ray_sabado - This is a Raspberry Pi install. ...
This is a Raspberry Pi install.
I'm unable to update SignalK from the GUI. I'm currently running 2.3.0 and node is 18.17.1 and npm is 9.8.1.
The install shows that it starts but then just ends with failed.
I think this is the relevant log information
Jul 18 10:01:18 stderr: npm Jul 18 10:01:18 stderr: ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/signalk-server npm ERR! dest /usr/local/lib/node_modules/.signalk-server-eaGa4pj4 Jul 18 10:01:18 stderr: npm ERR! errno -39 Jul 18 10:01:18 stderr: npm ERR! Jul 18 10:01:18 stderr: ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/signalk-server' -> '/usr/local/lib/node_modules/.signalk-server-eaGa4pj4' Jul 18 10:01:18 stderr: Jul 18 10:01:18 stderr: npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-07-18T14_00_08_493Z-debug-0.log FetchError: request to https://registry.npmjs.org/-/package/signalk-server/dist-tags failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org at ClientRequest.<anonymous> (/usr/local/lib/node_modules/signalk-server/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:514:28) at ClientRequest.emit (node:domain:489:12) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:514:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'EAI_AGAIN', code: 'EAI_AGAIN' }
Jul 18 10:01:18 stderr: npm Jul 18 10:01:18 stderr: ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /usr/local/lib/node_modules/signalk-server npm ERR! dest /usr/local/lib/node_modules/.signalk-server-eaGa4pj4 Jul 18 10:01:18 stderr: npm ERR! errno -39 Jul 18 10:01:18 stderr: npm ERR! Jul 18 10:01:18 stderr: ENOTEMPTY: directory not empty, rename '/usr/local/lib/node_modules/signalk-server' -> '/usr/local/lib/node_modules/.signalk-server-eaGa4pj4' Jul 18 10:01:18 stderr: Jul 18 10:01:18 stderr: npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-07-18T14_00_08_493Z-debug-0.log FetchError: request to https://registry.npmjs.org/-/package/signalk-server/dist-tags failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org at ClientRequest.<anonymous> (/usr/local/lib/node_modules/signalk-server/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:514:28) at ClientRequest.emit (node:domain:489:12) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:514:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'EAI_AGAIN', code: 'EAI_AGAIN' }
2 Replies
It looks like there is a problem with npm temporary directories that may be recoverable with the rename instruction
But there is a second error - EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error
Weird. It's a standard follow the steps install and the network is working fine. 🤷🏻♂️. The system is working without any issues so I may just leave it alone and not update it.
It worked after a reboot. It's been over six months of uptime so it was probably due.