jishi
commented
4 years ago You are running an old version of the api, there might be some changes in
sonos that makes it crash. To get a clean stack trace without the npm
noise, try running it with just node server.js
On Sat, 28 Sep 2019, 20:10 autofrank, notifications@github.com wrote:
Hi I'm running the http api on pi and it has been working for a few years now Earlier today the api started to go offline and restart itself approx every minute. I updated sonos to latest a few days ago and no other related changes
Is there somewhere I can try and debug to see why this is suddenly happening dump of npm-debug.log is below 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using npm@2.15.9 3 info using node@v4.5.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info prestart sonos-http-api@1.5.0 6 info start sonos-http-api@1.5.0 7 verbose unsafe-perm in lifecycle true 8 info sonos-http-api@1.5.0 Failed to exec start script 9 verbose stack Error: sonos-http-api@1.5.0 start: node server.js9 verbose stack Exit status 1 9 verbose stack at EventEmitter.
(/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:217:16) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at EventEmitter.emit (events.js:172:7) 9 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at ChildProcess.emit (events.js:172:7) 9 verbose stack at maybeClose (internal/child_process.js:829:16) 9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10 verbose pkgid sonos-http-api@1.5.0 11 verbose cwd /home/pi/node-sonos-http-api 12 error Linux 4.4.50-v7+ 13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 14 error node v4.5.0 15 error npm v2.15.9 16 error code ELIFECYCLE 17 error sonos-http-api@1.5.0 start:node server.js17 error Exit status 1 18 error Failed at the sonos-http-api@1.5.0 start script 'node server.js'. 18 error This is most likely a problem with the sonos-http-api package, 18 error not with npm itself. 18 error Tell the author that this fails on your system: 18 error node server.js 18 error You can get information on how to open an issue for this project with: 18 error npm bugs sonos-http-api 18 error Or if that isn't available, you can get their info via: 18 error 18 error npm owner ls sonos-http-api 18 error There is likely additional logging output above. 19 verbose exit [ 1, true ] — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jishi/node-sonos-http-api/issues/719?email_source=notifications&email_token=AAYE2I3QOYNCEMLFHKH2VF3QL6M2NA5CNFSM4I3PDV3KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HOKMKRA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYE2I7Y5L2CMB6XBG2MBWLQL6M2NANCNFSM4I3PDV3A .
autofrank
Hi I'm running the http api on pi and it has been working for a few years now Earlier today the api started to go offline and restart itself approx every minute. I updated sonos to latest a few days ago and no other related changes
Is there somewhere I can try and debug to see why this is suddenly happening dump of npm-debug.log is below
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using npm@2.15.9 3 info using node@v4.5.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info prestart sonos-http-api@1.5.0 6 info start sonos-http-api@1.5.0 7 verbose unsafe-perm in lifecycle true 8 info sonos-http-api@1.5.0 Failed to exec start script 9 verbose stack Error: sonos-http-api@1.5.0 start:node server.js9 verbose stack Exit status 1 9 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:217:16) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at EventEmitter.emit (events.js:172:7) 9 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14) 9 verbose stack at emitTwo (events.js:87:13) 9 verbose stack at ChildProcess.emit (events.js:172:7) 9 verbose stack at maybeClose (internal/child_process.js:829:16) 9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10 verbose pkgid sonos-http-api@1.5.0 11 verbose cwd /home/pi/node-sonos-http-api 12 error Linux 4.4.50-v7+ 13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 14 error node v4.5.0 15 error npm v2.15.9 16 error code ELIFECYCLE 17 error sonos-http-api@1.5.0 start:node server.js17 error Exit status 1 18 error Failed at the sonos-http-api@1.5.0 start script 'node server.js'. 18 error This is most likely a problem with the sonos-http-api package, 18 error not with npm itself. 18 error Tell the author that this fails on your system: 18 error node server.js 18 error You can get information on how to open an issue for this project with: 18 error npm bugs sonos-http-api 18 error Or if that isn't available, you can get their info via: 18 error 18 error npm owner ls sonos-http-api 18 error There is likely additional logging output above. 19 verbose exit [ 1, true ]Space on the PI good and I have a HA bridge service running on the same pi and that is not being impacted...
Any suggestions appreciated.... Thanks