Failed to Execute Start Script

[erodenberg-esri]

I'm running into an issue getting the API started. The log file is saying that it failed to execute the start script. Here is a dump of my log:

0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.24.0
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
7 info using npm@5.8.0
8 info using node@v10.24.0
9 verbose run-script [ 'prestart', 'start', 'poststart' ]
10 info lifecycle sonos-http-api@1.6.9~prestart: sonos-http-api@1.6.9
11 info lifecycle sonos-http-api@1.6.9~start: sonos-http-api@1.6.9
12 verbose lifecycle sonos-http-api@1.6.9~start: unsafe-perm in lifecycle true
13 verbose lifecycle sonos-http-api@1.6.9~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-sonos-http-api/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/$
14 verbose lifecycle sonos-http-api@1.6.9~start: CWD: /home/pi/node-sonos-http-api
15 silly lifecycle sonos-http-api@1.6.9~start: Args: [ '-c', 'node server.js' ]
16 silly lifecycle sonos-http-api@1.6.9~start: Returned: code: 1  signal: null
17 info lifecycle sonos-http-api@1.6.9~start: Failed to exec start script
18 verbose stack Error: sonos-http-api@1.6.9 start: `node server.js`
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)
18 verbose stack     at EventEmitter.emit (events.js:198:13)
18 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:198:13)
18 verbose stack     at maybeClose (internal/child_process.js:982:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
19 verbose pkgid sonos-http-api@1.6.9
20 verbose cwd /home/pi/node-sonos-http-api
21 verbose Linux 4.19.97-v7+
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
23 verbose node v10.24.0
24 verbose npm  v5.8.0
25 error code ELIFECYCLE
26 error errno 1
27 error sonos-http-api@1.6.9 start: `node server.js`
27 error Exit status 1
28 error Failed at the sonos-http-api@1.6.9 start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]

[jishi]

Try running it with node directly (node server.js) and see what it says.

…

On Fri, 10 May 2024, 20:34 Eric Rodenberg, ***@***.***> wrote: I'm running into an issue getting the API started. The log file is saying that it failed to execute the start script. Here is a dump of my log: 0 info it worked if it ends with ok 1 warn npm npm does not support Node.js v10.24.0 2 warn npm You should probably upgrade to a newer version of node as we 3 warn npm can't make any promises that npm will work with this version. 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. 5 warn npm You can find the latest version at https://nodejs.org/ 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 7 info using ***@***.*** 8 info using ***@***.*** 9 verbose run-script [ 'prestart', 'start', 'poststart' ] 10 info lifecycle ***@***.***~prestart: ***@***.*** 11 info lifecycle ***@***.***~start: ***@***.*** 12 verbose lifecycle ***@***.***~start: unsafe-perm in lifecycle true 13 verbose lifecycle ***@***.***~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-sonos-http-api/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/$ 14 verbose lifecycle ***@***.***~start: CWD: /home/pi/node-sonos-http-api 15 silly lifecycle ***@***.***~start: Args: [ '-c', 'node server.js' ] 16 silly lifecycle ***@***.***~start: Returned: code: 1 signal: null 17 info lifecycle ***@***.***~start: Failed to exec start script 18 verbose stack Error: ***@***.*** start: `node server.js` 18 verbose stack Exit status 1 18 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16) 18 verbose stack at EventEmitter.emit (events.js:198:13) 18 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 18 verbose stack at ChildProcess.emit (events.js:198:13) 18 verbose stack at maybeClose (internal/child_process.js:982:16) 18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 19 verbose pkgid ***@***.*** 20 verbose cwd /home/pi/node-sonos-http-api 21 verbose Linux 4.19.97-v7+ 22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 23 verbose node v10.24.0 24 verbose npm v5.8.0 25 error code ELIFECYCLE 26 error errno 1 27 error ***@***.*** start: `node server.js` 27 error Exit status 1 28 error Failed at the ***@***.*** start script. 28 error This is probably not a problem with npm. There is likely additional logging output above. 29 verbose exit [ 1, true ] — Reply to this email directly, view it on GitHub <#890>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2I4Z6KHKQXM7JW3Q5DDZBUHJ3AVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TAMRRGY3TAMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[erodenberg-esri]

Jimmy, Here you go… I think it is saying that it can find the Axios library. Do I have that right? ***@***.***:~/node-sonos-http-api $ node server.js 2024-05-10T20:13:58.783Z INFO Presets loaded: { example: { players: [ { roomName: 'Bathroom', volume: 10 }, { roomName: 'Kitchen', volume: 10 }, { roomName: 'Office', volume: 10 }, { roomName: 'Bedroom', volume: 10 }, { roomName: 'TV Room', volume: 15 } ], playMode: { shuffle: true, repeat: 'all', crossfade: false }, pauseOthers: false } } /home/pi/node-sonos-http-api/node_modules/axios/index.js:1 import axios from './lib/axios.js'; ^^^^^ SyntaxError: Unexpected identifier at Module._compile (internal/modules/cjs/loader.js:723:23) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/node_modules/elevenlabs-node/index.js:1:15) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/lib/tts-providers/elevenlabs.js:6:20) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) From: Jimmy Shimizu ***@***.***> Sent: Friday, May 10, 2024 2:43 PM To: jishi/node-sonos-http-api ***@***.***> Cc: Eric Rodenberg ***@***.***>; Author ***@***.***> Subject: Re: [jishi/node-sonos-http-api] Failed to Execute Start Script (Issue #890) Try running it with node directly (node server.js) and see what it says.

On Fri, 10 May 2024, 20:34 Eric Rodenberg, ***@***.***<mailto:***@***.***>> wrote: I'm running into an issue getting the API started. The log file is saying that it failed to execute the start script. Here is a dump of my log: 0 info it worked if it ends with ok 1 warn npm npm does not support Node.js v10.24.0 2 warn npm You should probably upgrade to a newer version of node as we 3 warn npm can't make any promises that npm will work with this version. 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. 5 warn npm You can find the latest version at https://nodejs.org/ 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 7 info using ***@***.***<mailto:***@***.***> 8 info using ***@***.***<mailto:***@***.***> 9 verbose run-script [ 'prestart', 'start', 'poststart' ] 10 info lifecycle ***@***.***~prestart<mailto:***@***.***~prestart>: ***@***.***<mailto:***@***.***> 11 info lifecycle ***@***.***~start<mailto:***@***.***~start>: ***@***.***<mailto:***@***.***> 12 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: unsafe-perm in lifecycle true 13 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-sonos-http-api/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/$ 14 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: CWD: /home/pi/node-sonos-http-api 15 silly lifecycle ***@***.***~start<mailto:***@***.***~start>: Args: [ '-c', 'node server.js' ] 16 silly lifecycle ***@***.***~start<mailto:***@***.***~start>: Returned: code: 1 signal: null 17 info lifecycle ***@***.***~start<mailto:***@***.***~start>: Failed to exec start script 18 verbose stack Error: ***@***.***<mailto:***@***.***> start: `node server.js` 18 verbose stack Exit status 1 18 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16) 18 verbose stack at EventEmitter.emit (events.js:198:13) 18 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 18 verbose stack at ChildProcess.emit (events.js:198:13) 18 verbose stack at maybeClose (internal/child_process.js:982:16) 18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 19 verbose pkgid ***@***.***<mailto:***@***.***> 20 verbose cwd /home/pi/node-sonos-http-api 21 verbose Linux 4.19.97-v7+ 22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 23 verbose node v10.24.0 24 verbose npm v5.8.0 25 error code ELIFECYCLE 26 error errno 1 27 error ***@***.***<mailto:***@***.***> start: `node server.js` 27 error Exit status 1 28 error Failed at the ***@***.***<mailto:***@***.***> start script. 28 error This is probably not a problem with npm. There is likely additional logging output above. 29 verbose exit [ 1, true ] — Reply to this email directly, view it on GitHub <#890>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2I4Z6KHKQXM7JW3Q5DDZBUHJ3AVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TAMRRGY3TAMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https:/github.com/jishi/node-sonos-http-api/issues/890*issuecomment-2105099382__;Iw!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJgxeLly9c$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AL6ST3SEOZVHTORKKLYP72LZBUINBAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGA4TSMZYGI__;!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJg65FGqLE$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[jishi]

Looks like the axios lib that is installed is an esm module. I wouldn't expect the package-lock.json to include an esm-version, but maybe some references there are incompatible with node 10. Either update to node 18 which should support esm modules, or find a version of axios that doesn't compile as esm (basically, <1.0.0, 0.27.2 seems to be the last one). Not sure it would work though.

…

On Fri, 10 May 2024, 22:17 Eric Rodenberg, ***@***.***> wrote: Jimmy, Here you go… I think it is saying that it can find the Axios library. Do I have that right? ***@***.***:~/node-sonos-http-api $ node server.js 2024-05-10T20:13:58.783Z INFO Presets loaded: { example: { players: [ { roomName: 'Bathroom', volume: 10 }, { roomName: 'Kitchen', volume: 10 }, { roomName: 'Office', volume: 10 }, { roomName: 'Bedroom', volume: 10 }, { roomName: 'TV Room', volume: 15 } ], playMode: { shuffle: true, repeat: 'all', crossfade: false }, pauseOthers: false } } /home/pi/node-sonos-http-api/node_modules/axios/index.js:1 import axios from './lib/axios.js'; ^^^^^ SyntaxError: Unexpected identifier at Module._compile (internal/modules/cjs/loader.js:723:23) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/node_modules/elevenlabs-node/index.js:1:15) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/lib/tts-providers/elevenlabs.js:6:20) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) From: Jimmy Shimizu ***@***.***> Sent: Friday, May 10, 2024 2:43 PM To: jishi/node-sonos-http-api ***@***.***> Cc: Eric Rodenberg ***@***.***>; Author ***@***.***> Subject: Re: [jishi/node-sonos-http-api] Failed to Execute Start Script (Issue #890) Try running it with node directly (node server.js) and see what it says. On Fri, 10 May 2024, 20:34 Eric Rodenberg, ***@***.***<mailto:***@***.***>> wrote: > I'm running into an issue getting the API started. The log file is saying > that it failed to execute the start script. Here is a dump of my log: > > 0 info it worked if it ends with ok > 1 warn npm npm does not support Node.js v10.24.0 > 2 warn npm You should probably upgrade to a newer version of node as we > 3 warn npm can't make any promises that npm will work with this version. > 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. > 5 warn npm You can find the latest version at https://nodejs.org/ > 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] > 7 info using ***@***.***<mailto:***@***.***> > 8 info using ***@***.***<mailto:***@***.***> > 9 verbose run-script [ 'prestart', 'start', 'poststart' ] > 10 info lifecycle ***@***.***~prestart<mailto:***@***.***~prestart>: ***@***.***<mailto:***@***.***> > 11 info lifecycle ***@***.***~start<mailto:***@***.***~start>: ***@***.***<mailto:***@***.***> > 12 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: unsafe-perm in lifecycle true > 13 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-sonos-http-api/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/$ > 14 verbose lifecycle ***@***.***~start<mailto:***@***.***~start>: CWD: /home/pi/node-sonos-http-api > 15 silly lifecycle ***@***.***~start<mailto:***@***.***~start>: Args: [ '-c', 'node server.js' ] > 16 silly lifecycle ***@***.***~start<mailto:***@***.***~start>: Returned: code: 1 signal: null > 17 info lifecycle ***@***.***~start<mailto:***@***.***~start>: Failed to exec start script > 18 verbose stack Error: ***@***.***<mailto:***@***.***> start: `node server.js` > 18 verbose stack Exit status 1 > 18 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16) > 18 verbose stack at EventEmitter.emit (events.js:198:13) > 18 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) > 18 verbose stack at ChildProcess.emit (events.js:198:13) > 18 verbose stack at maybeClose (internal/child_process.js:982:16) > 18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) > 19 verbose pkgid ***@***.***<mailto:***@***.***> > 20 verbose cwd /home/pi/node-sonos-http-api > 21 verbose Linux 4.19.97-v7+ > 22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" > 23 verbose node v10.24.0 > 24 verbose npm v5.8.0 > 25 error code ELIFECYCLE > 26 error errno 1 > 27 error ***@***.***<mailto:***@***.***> start: `node server.js` > 27 error Exit status 1 > 28 error Failed at the ***@***.***<mailto:***@***.***> start script. > 28 error This is probably not a problem with npm. There is likely additional logging output above. > 29 verbose exit [ 1, true ] > > — > Reply to this email directly, view it on GitHub > <#890>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAYE2I4Z6KHKQXM7JW3Q5DDZBUHJ3AVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TAMRRGY3TAMY> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***<mailto:***@***.***>> > — Reply to this email directly, view it on GitHub [github.com]< https://urldefense.com/v3/__https:/github.com/jishi/node-sonos-http-api/issues/890*issuecomment-2105099382__;Iw!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJgxeLly9c$>, or unsubscribe [github.com]< https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AL6ST3SEOZVHTORKKLYP72LZBUINBAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGA4TSMZYGI__;!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJg65FGqLE$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> — Reply to this email directly, view it on GitHub <#890 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2IYS3E34LDJZICPDY5TZBUTOFAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGIYTQMBYGY> . You are receiving this because you commented.Message ID: ***@***.***>

[erodenberg-esri]

Updated to Node 18.20.2… all is working, Thanks. From: Jimmy Shimizu ***@***.***> Sent: Friday, May 10, 2024 4:27 PM To: jishi/node-sonos-http-api ***@***.***> Cc: Eric Rodenberg ***@***.***>; Author ***@***.***> Subject: Re: [jishi/node-sonos-http-api] Failed to Execute Start Script (Issue #890) Looks like the axios lib that is installed is an esm module. I wouldn't expect the package-lock.json to include an esm-version, but maybe some references there are incompatible with node 10. Either update to node 18 which should support esm modules, or find a version of axios that doesn't compile as esm (basically, <1.0.0, 0.27.2 seems to be the last one). Not sure it would work though.

On Fri, 10 May 2024, 22:17 Eric Rodenberg, ***@***.***<mailto:***@***.***>> wrote: Jimmy, Here you go… I think it is saying that it can find the Axios library. Do I have that right? ***@***.***:~/node-sonos-http-api<mailto:***@***.***:~/node-sonos-http-api> $ node server.js 2024-05-10T20:13:58.783Z INFO Presets loaded: { example: { players: [ { roomName: 'Bathroom', volume: 10 }, { roomName: 'Kitchen', volume: 10 }, { roomName: 'Office', volume: 10 }, { roomName: 'Bedroom', volume: 10 }, { roomName: 'TV Room', volume: 15 } ], playMode: { shuffle: true, repeat: 'all', crossfade: false }, pauseOthers: false } } /home/pi/node-sonos-http-api/node_modules/axios/index.js:1 import axios from './lib/axios.js'; ^^^^^ SyntaxError: Unexpected identifier at Module._compile (internal/modules/cjs/loader.js:723:23) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/node_modules/elevenlabs-node/index.js:1:15) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object.<anonymous> (/home/pi/node-sonos-http-api/lib/tts-providers/elevenlabs.js:6:20) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) From: Jimmy Shimizu ***@***.***<mailto:***@***.***>> Sent: Friday, May 10, 2024 2:43 PM To: jishi/node-sonos-http-api ***@***.***<mailto:***@***.***>> Cc: Eric Rodenberg ***@***.***<mailto:***@***.***>>; Author ***@***.***<mailto:***@***.***>> Subject: Re: [jishi/node-sonos-http-api] Failed to Execute Start Script (Issue #890) Try running it with node directly (node server.js) and see what it says. On Fri, 10 May 2024, 20:34 Eric Rodenberg, ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>> wrote: > I'm running into an issue getting the API started. The log file is saying > that it failed to execute the start script. Here is a dump of my log: > > 0 info it worked if it ends with ok > 1 warn npm npm does not support Node.js v10.24.0 > 2 warn npm You should probably upgrade to a newer version of node as we > 3 warn npm can't make any promises that npm will work with this version. > 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. > 5 warn npm You can find the latest version at https://nodejs.org/ > 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] > 7 info using ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> > 8 info using ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> > 9 verbose run-script [ 'prestart', 'start', 'poststart' ] > 10 info lifecycle ***@***.***~prestart<mailto:***@***.***~prestart<mailto:***@***.***~prestart%3cmailto:***@***.***~prestart>>: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> > 11 info lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> > 12 verbose lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: unsafe-perm in lifecycle true > 13 verbose lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/node-sonos-http-api/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/$ > 14 verbose lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: CWD: /home/pi/node-sonos-http-api > 15 silly lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: Args: [ '-c', 'node server.js' ] > 16 silly lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: Returned: code: 1 signal: null > 17 info lifecycle ***@***.***~start<mailto:***@***.***~start<mailto:***@***.***~start%3cmailto:***@***.***~start>>: Failed to exec start script > 18 verbose stack Error: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> start: `node server.js` > 18 verbose stack Exit status 1 > 18 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16) > 18 verbose stack at EventEmitter.emit (events.js:198:13) > 18 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) > 18 verbose stack at ChildProcess.emit (events.js:198:13) > 18 verbose stack at maybeClose (internal/child_process.js:982:16) > 18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) > 19 verbose pkgid ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> > 20 verbose cwd /home/pi/node-sonos-http-api > 21 verbose Linux 4.19.97-v7+ > 22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" > 23 verbose node v10.24.0 > 24 verbose npm v5.8.0 > 25 error code ELIFECYCLE > 26 error errno 1 > 27 error ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> start: `node server.js` > 27 error Exit status 1 > 28 error Failed at the ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>> start script. > 28 error This is probably not a problem with npm. There is likely additional logging output above. > 29 verbose exit [ 1, true ] > > — > Reply to this email directly, view it on GitHub > <#890>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAYE2I4Z6KHKQXM7JW3Q5DDZBUHJ3AVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TAMRRGY3TAMY> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>> > — Reply to this email directly, view it on GitHub [github.com]< https://urldefense.com/v3/__https:/github.com/jishi/node-sonos-http-api/issues/890*issuecomment-2105099382__;Iw!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJgxeLly9c$>, or unsubscribe [github.com]< https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AL6ST3SEOZVHTORKKLYP72LZBUINBAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGA4TSMZYGI__;!!CKZwjTOV!zUXrXwE161RWi274eHZTBsOEIPqbYHGxWBEbkEDR2XBnt5DOVgVsp9iWv7Y91KHXrPbafQwOrmPtBPJg65FGqLE$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***<mailto:***@***.******@***.***>>> — Reply to this email directly, view it on GitHub <#890 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYE2IYS3E34LDJZICPDY5TZBUTOFAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGIYTQMBYGY> . You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https:/github.com/jishi/node-sonos-http-api/issues/890*issuecomment-2105230683__;Iw!!CKZwjTOV!z6-4gKVGZhllFhuNnszWK5gpoF0Bv8A1wf_SRjLjqUstfdhy2xaOfrP8Sz0t6uavnFAqUvgWLEGPLL4mOSg1BoM$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AL6ST3UF46DZF5A5WRF6WMDZBUUSXAVCNFSM6AAAAABHRCHRVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVGIZTANRYGM__;!!CKZwjTOV!z6-4gKVGZhllFhuNnszWK5gpoF0Bv8A1wf_SRjLjqUstfdhy2xaOfrP8Sz0t6uavnFAqUvgWLEGPLL4micURvbA$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>