Error in Signalk log

[mshulman]

xMay 18 15:28:32 Error: SQLITE_MISUSE: Database is closed at plugin.stop (/home/pi/.signalk/node_modules/signalk-saillogger/index.js:78:10) at stopPlugin (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:239:16) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:445:17 at savePluginOptions (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:135:13) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:437:13 at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:149:13) at Route.dispatch (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:119:3) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at /usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:284:15 at Function.process_params (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:346:12) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:280:10) at Function.handle (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:175:3) at router (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:328:13) { errno: 21, code: 'SQLITE_MISUSE' }

I want realtime monitoring of my boat at the slip, so I enabled the Fixed Position plugin at a lower priority. I don't know if it's related to this error.

[admin]

Hi Michael, few questions:

• When do you see this error?
• What are the steps that have taken you here?
• Did the plugin stop logging or working after seeing this?

Thanks,

[mshulman]

1. I'm running (right now) on a raspberry pi zero w. After this message, I got a node kernel panic and I had to restart the pi. I think that the poor thing just ran out of resources (threads or whatever).
2. I don't think I was doing anything in particular that caused this error
3. Yes, the plugin and server stopped working.

Now that I've recovered from this error, I'm not seeing it again.