Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Saillogger Community

  1. Home
  2. General Discussion
  3. No data reaching Saillogger after upgrade of Openplotter 3->4

No data reaching Saillogger after upgrade of Openplotter 3->4

Scheduled Pinned Locked Moved General Discussion
5 Posts 3 Posters 743 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    alastairbuchan
    wrote last edited by
    #1

    I recently moved my install from OP3 to OP4 on RPI 4
    This involved a totally new install on a new SD Card.
    Hardware is the same
    SK plugins and version were up-to-date before makeing a signalk backup. I did not include plugins in the backup.

    Restore went well and signalk came back online even though it took a long time to restart - I guess as NPM modules were restored.

    However, Saillogger does not appear to communicate with the cloud - no updates shown on web or app since around the time I took Op3 down.
    Saillogger config with boat ID was ok when restored. I even uninstalled the plugin and reinstallled.

    Dashboard plugin status shows (in green)
    "Saillogger Started please wait 60seconds for a Status update."

    SK log shows this when debug is enabled.

    Jun 08 07:27:13 2025-06-08T05:27:13.708Z signalk-saillogger Stopping the plugin
    Jun 08 07:27:13 POST /skServer/plugins/signalk-saillogger/config 200 15.291 ms - 51
    Jun 08 07:27:13 2025-06-08T05:27:13.723Z signalk-saillogger Running on Raspberry Pi 4 Model B Rev 1.4
    Jun 08 07:27:13 2025-06-08T05:27:13.724Z signalk-saillogger Starting the plugin with collector ID 62c49d8a-aab9-4cad
    Jun 08 07:27:13 [object Object]
    Jun 08 07:27:13 2025-06-08T05:27:13.752Z signalk-saillogger Retrieving monitoring configuration
    Jun 08 07:27:13 2025-06-08T05:27:13.756Z signalk-saillogger Sending metadata
    Jun 08 07:27:13 [Error: SQLITE_NOTADB: file is not a database] { errno: 26, code: 'SQLITE_NOTADB' }
    Jun 08 07:27:13 2025-06-08T05:27:13.798Z signalk-saillogger Error querying the local cache: [Error: SQLITE_NOTADB: file is not a database] { errno: 26, code: 'SQLITE_NOTADB' }
    Jun 08 07:27:13 [Error: SQLITE_NOTADB: file is not a database] { errno: 26, code: 'SQLITE_NOTADB' }
    Jun 08 07:27:14 2025-06-08T05:27:14.095Z signalk-saillogger Monitoring configuration: {"version":1718665020,"depthKey":"environment.depth.belowTransducer","waterTemperatureKey":"environment.water.temperature","insideTemperatureKey":"environment.inside.temperature","outsideTemperatureKey":"environment.outside.temperature","insideHumidityKey":"environment.inside.humidity","outsideHumidityKey":"environment.outside.humidity","windSpeedKey":"environment.wind.speedApparent","windDirectionKey":"environment.wind.directionTrue","pressureKey":"environment.outside.pressure","batteryVoltageKey":"electrical.batteries.House.voltage","batteryChargeKey":"electrical.batteries.House.capacity.stateOfCharge","sendAisTargets":true,"additionalDataKeys":[]}
    Jun 08 07:27:14 2025-06-08T05:27:14.097Z signalk-saillogger Failed to store configuration locally Error: SQLITE_NOTADB: file is not a database
    Jun 08 07:27:14 2025-06-08T05:27:14.097Z signalk-saillogger Inserted logging and monitoring data into the local cache
    Jun 08 07:27:14 2025-06-08T05:27:14.098Z signalk-saillogger Error querying the local cache: [Error: SQLITE_NOTADB: file is not a database] { errno: 26, code: 'SQLITE_NOTADB' }
    Jun 08 07:27:14 2025-06-08T05:27:14.154Z signalk-saillogger Successfully submitted metadata

    Seems to be an issue with SQLITE?

    Any help appreciated,

    1 Reply Last reply
    0
  • K Offline
    K Offline
    KevinN
    wrote last edited by
    #2

    Hello and thanks for contacting Saillogger, I’m going to refer this to Ilker as it is in his lane of expertise. Sorry for the delay in getting a response to you.

    Happy Cruising!
    Kevin N

    1 Reply Last reply
    0
  • adminA Offline
    adminA Offline
    admin
    wrote last edited by
    #3

    Hi Alastair, looks like your Signal K plugin installation got corrupted. Could you try uninstalling and re-installing the Saillogger Signal K plugin? Please do restart Signal K after uninstalling and after re-installing it.

    1 Reply Last reply
    0
  • A Offline
    A Offline
    alastairbuchan
    wrote last edited by
    #4

    Hi All, Just to close the loop on this topic in case anyone falls down the same rabbit hole. I have not managed to solve this via uninstall / re-install. Sk went to "failed" after any attempt to install/unistall any plugin. I have seen this problem before on Sk, and I tried to rebuild the node_modules dir after deletion, restoring from a backup with pluggins but nothing has helped, in fact my Sk environment just got worse to the point I don't wish to recover it. Currently I am back online but with original SD card of OP3. Only way forward I see is to start an new OP4 environment from scratch without backups. (fortunately I have another PI) to build it copying and pasting plugin config.

    1 Reply Last reply
    1
  • adminA Offline
    adminA Offline
    admin
    wrote last edited by
    #5

    Thank you for sharing this Alastair.

    1 Reply Last reply
    1

Powered by NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular