13.05.20 12:57:03 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 12:57:03 (+0900) <fleet-supervisor>       ^
13.05.20 12:57:03 (+0900) <fleet-supervisor> 
13.05.20 12:57:03 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 12:57:03 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 12:57:03 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 12:57:03 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 12:57:03 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 12:57:03 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 12:57:03 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 12:57:03 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 12:57:03 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 12:57:03 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 12:57:03 (+0900) <fleet-supervisor>   port: 1705
13.05.20 12:57:03 (+0900) <fleet-supervisor> }
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 12:57:03 (+0900) <fleet-supervisor> 
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 12:57:03 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T03_57_03_288Z-debug.log
13.05.20 12:57:03 (+0900) <fleet-supervisor> 2020-05-13T03:58:05.331191000Z OK
13.05.20 12:58:05 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 12:58:05 (+0900) <fleet-supervisor> > node server.js
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#dc7a6367-de67-42d6-8d84-205ca7c06e92 
13.05.20 12:58:05 (+0900) <fleet-supervisor> ========================
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#5cecc93d-50ed-43fc-bd6f-df7477ad9e64 on 8000 
13.05.20 12:58:05 (+0900) <fleet-supervisor> ========================
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#5cecc93d-50ed-43fc-bd6f-df7477ad9e64 on 8000
13.05.20 12:58:05 (+0900) <fleet-supervisor> events.js:292
13.05.20 12:58:05 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 12:58:05 (+0900) <fleet-supervisor>       ^
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 12:58:05 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 12:58:05 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 12:58:05 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 12:58:05 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 12:58:05 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 12:58:05 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 12:58:05 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 12:58:05 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 12:58:05 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 12:58:05 (+0900) <fleet-supervisor>   port: 1705
13.05.20 12:58:05 (+0900) <fleet-supervisor> }
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 12:58:05 (+0900) <fleet-supervisor> 
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 12:58:05 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T03_58_05_967Z-debug.log
13.05.20 12:58:06 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 12:58:06 (+0900) <fleet-supervisor> 
13.05.20 12:59:07 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 12:58:06 (+0900) <fleet-supervisor> 2020-05-13T03:59:08.017819000Z OK
13.05.20 12:59:08 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 12:59:08 (+0900) <fleet-supervisor> > node server.js
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#44d417eb-8d34-403c-813b-42cfd9fdca32 
13.05.20 12:59:08 (+0900) <fleet-supervisor> ========================
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#e3464f3e-db44-4727-823f-8862f57cbfca on 8000 
13.05.20 12:59:08 (+0900) <fleet-supervisor> ========================
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#e3464f3e-db44-4727-823f-8862f57cbfca on 8000
13.05.20 12:59:08 (+0900) <fleet-supervisor> events.js:292
13.05.20 12:59:08 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 12:59:08 (+0900) <fleet-supervisor>       ^
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 12:59:08 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 12:59:08 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 12:59:08 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 12:59:08 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 12:59:08 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 12:59:08 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 12:59:08 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 12:59:08 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 12:59:08 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 12:59:08 (+0900) <fleet-supervisor>   port: 1705
13.05.20 12:59:08 (+0900) <fleet-supervisor> }
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 12:59:08 (+0900) <fleet-supervisor> 
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 12:59:08 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T03_59_08_674Z-debug.log
13.05.20 12:59:09 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 12:59:09 (+0900) <fleet-supervisor> 
13.05.20 13:00:09 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 12:59:09 (+0900) <fleet-supervisor> 2020-05-13T04:00:10.708035000Z OK
13.05.20 13:00:10 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:00:10 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:00:10 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#a823da90-698b-45cd-9a5d-18bf093f5bfd 
13.05.20 13:00:11 (+0900) <fleet-supervisor> ========================
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#c1633928-771d-421a-9039-f51269ac1e46 on 8000 
13.05.20 13:00:11 (+0900) <fleet-supervisor> ========================
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#c1633928-771d-421a-9039-f51269ac1e46 on 8000
13.05.20 13:00:11 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:00:11 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:00:11 (+0900) <fleet-supervisor>       ^
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:00:11 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:00:11 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:00:11 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:00:11 (+0900) <fleet-supervisor> }
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_00_11_342Z-debug.log
13.05.20 13:00:11 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:01:12 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#a823da90-698b-45cd-9a5d-18bf093f5bfd 
13.05.20 13:00:11 (+0900) <fleet-supervisor> ========================
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#c1633928-771d-421a-9039-f51269ac1e46 on 8000 
13.05.20 13:00:11 (+0900) <fleet-supervisor> ========================
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#c1633928-771d-421a-9039-f51269ac1e46 on 8000
13.05.20 13:00:11 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:00:11 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:00:11 (+0900) <fleet-supervisor>       ^
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:00:11 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:00:11 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:00:11 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:00:11 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:00:11 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:00:11 (+0900) <fleet-supervisor> }
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:00:11 (+0900) <fleet-supervisor> 
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:00:11 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_00_11_342Z-debug.log
13.05.20 13:00:11 (+0900) <fleet-supervisor> 2020-05-13T04:01:13.593605000Z OK
13.05.20 13:01:13 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:01:13 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:01:13 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#266b0a22-0005-4b59-af3b-6e4a641d474e 
13.05.20 13:01:14 (+0900) <fleet-supervisor> ========================
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#10177436-1bca-4203-a86a-5f4277dfa7eb on 8000 
13.05.20 13:01:14 (+0900) <fleet-supervisor> ========================
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#10177436-1bca-4203-a86a-5f4277dfa7eb on 8000
13.05.20 13:01:14 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:01:14 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:01:14 (+0900) <fleet-supervisor>       ^
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:01:14 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:01:14 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:01:14 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:01:14 (+0900) <fleet-supervisor> }
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_01_14_291Z-debug.log
13.05.20 13:01:14 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:02:15 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#266b0a22-0005-4b59-af3b-6e4a641d474e 
13.05.20 13:01:14 (+0900) <fleet-supervisor> ========================
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#10177436-1bca-4203-a86a-5f4277dfa7eb on 8000 
13.05.20 13:01:14 (+0900) <fleet-supervisor> ========================
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#10177436-1bca-4203-a86a-5f4277dfa7eb on 8000
13.05.20 13:01:14 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:01:14 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:01:14 (+0900) <fleet-supervisor>       ^
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:01:14 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:01:14 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:01:14 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:01:14 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:01:14 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:01:14 (+0900) <fleet-supervisor> }
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:01:14 (+0900) <fleet-supervisor> 
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:01:14 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_01_14_291Z-debug.log
13.05.20 13:01:14 (+0900) <fleet-supervisor> 2020-05-13T04:02:16.316433000Z OK
13.05.20 13:02:16 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:02:16 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#834f6523-8299-4b10-beeb-ca9579f985ed 
13.05.20 13:02:16 (+0900) <fleet-supervisor> ========================
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#6099b9d1-2603-46c3-bb83-fa4dbc945300 on 8000 
13.05.20 13:02:16 (+0900) <fleet-supervisor> ========================
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#6099b9d1-2603-46c3-bb83-fa4dbc945300 on 8000
13.05.20 13:02:16 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:02:16 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:02:16 (+0900) <fleet-supervisor>       ^
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:02:16 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:02:16 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:02:16 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:02:16 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:02:16 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:02:16 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:02:16 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:02:16 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:02:16 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:02:16 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:02:16 (+0900) <fleet-supervisor> }
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:02:16 (+0900) <fleet-supervisor> 
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:02:16 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_02_16_958Z-debug.log
13.05.20 13:02:17 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:02:17 (+0900) <fleet-supervisor> 
13.05.20 13:03:18 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:02:17 (+0900) <fleet-supervisor> 2020-05-13T04:03:19.009820000Z OK
13.05.20 13:03:19 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:03:19 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#b82fd246-1899-4976-89e4-f55b95d50c77 
13.05.20 13:03:19 (+0900) <fleet-supervisor> ========================
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#25ef73c1-5dc0-4af5-b7fc-0143d261e3d5 on 8000 
13.05.20 13:03:19 (+0900) <fleet-supervisor> ========================
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#25ef73c1-5dc0-4af5-b7fc-0143d261e3d5 on 8000
13.05.20 13:03:19 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:03:19 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:03:19 (+0900) <fleet-supervisor>       ^
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:03:19 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:03:19 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:03:19 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:03:19 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:03:19 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:03:19 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:03:19 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:03:19 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:03:19 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:03:19 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:03:19 (+0900) <fleet-supervisor> }
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:03:19 (+0900) <fleet-supervisor> 
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:03:19 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_03_19_642Z-debug.log
13.05.20 13:03:20 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:03:20 (+0900) <fleet-supervisor> 
13.05.20 13:04:20 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:03:20 (+0900) <fleet-supervisor> 2020-05-13T04:04:21.688494000Z OK
13.05.20 13:04:21 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:04:21 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:04:21 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#1fa60da8-c557-4aa1-8e8f-64054e4b509f 
13.05.20 13:04:22 (+0900) <fleet-supervisor> ========================
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#610390f5-8235-41c2-9d99-605152a654cd on 8000 
13.05.20 13:04:22 (+0900) <fleet-supervisor> ========================
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#610390f5-8235-41c2-9d99-605152a654cd on 8000
13.05.20 13:04:22 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:04:22 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:04:22 (+0900) <fleet-supervisor>       ^
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:04:22 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:04:22 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:04:22 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:04:22 (+0900) <fleet-supervisor> }
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_04_22_323Z-debug.log
13.05.20 13:04:22 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:05:23 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#1fa60da8-c557-4aa1-8e8f-64054e4b509f 
13.05.20 13:04:22 (+0900) <fleet-supervisor> ========================
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#610390f5-8235-41c2-9d99-605152a654cd on 8000 
13.05.20 13:04:22 (+0900) <fleet-supervisor> ========================
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#610390f5-8235-41c2-9d99-605152a654cd on 8000
13.05.20 13:04:22 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:04:22 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:04:22 (+0900) <fleet-supervisor>       ^
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:04:22 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:04:22 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:04:22 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:04:22 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:04:22 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:04:22 (+0900) <fleet-supervisor> }
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:04:22 (+0900) <fleet-supervisor> 
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:04:22 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_04_22_323Z-debug.log
13.05.20 13:04:22 (+0900) <fleet-supervisor> 2020-05-13T04:05:24.336795000Z OK
13.05.20 13:05:24 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:05:24 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#0f0bc778-b902-419b-a28f-afa5c4c6e39f 
13.05.20 13:05:24 (+0900) <fleet-supervisor> ========================
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#0833eca1-e071-4d07-beed-88be0752f702 on 8000 
13.05.20 13:05:24 (+0900) <fleet-supervisor> ========================
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#0833eca1-e071-4d07-beed-88be0752f702 on 8000
13.05.20 13:05:24 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:05:24 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:05:24 (+0900) <fleet-supervisor>       ^
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:05:24 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:05:24 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:05:24 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:05:24 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:05:24 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:05:24 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:05:24 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:05:24 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:05:24 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:05:24 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:05:24 (+0900) <fleet-supervisor> }
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:05:24 (+0900) <fleet-supervisor> 
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:05:24 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_05_24_979Z-debug.log
13.05.20 13:05:25 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:05:25 (+0900) <fleet-supervisor> 
13.05.20 13:06:26 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:05:25 (+0900) <fleet-supervisor> 2020-05-13T04:06:27.009422000Z OK
13.05.20 13:06:27 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:06:27 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#4366c4df-3846-451b-afcb-ab0ed6d367a9 
13.05.20 13:06:27 (+0900) <fleet-supervisor> ========================
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#6b021eca-6e58-4c25-9696-d9402283f4c4 on 8000 
13.05.20 13:06:27 (+0900) <fleet-supervisor> ========================
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#6b021eca-6e58-4c25-9696-d9402283f4c4 on 8000
13.05.20 13:06:27 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:06:27 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:06:27 (+0900) <fleet-supervisor>       ^
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:06:27 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:06:27 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:06:27 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:06:27 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:06:27 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:06:27 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:06:27 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:06:27 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:06:27 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:06:27 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:06:27 (+0900) <fleet-supervisor> }
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:06:27 (+0900) <fleet-supervisor> 
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:06:27 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_06_27_646Z-debug.log
13.05.20 13:06:28 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:06:28 (+0900) <fleet-supervisor> 
13.05.20 13:07:28 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:06:28 (+0900) <fleet-supervisor> 2020-05-13T04:07:29.658844000Z OK
13.05.20 13:07:29 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:07:29 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:07:29 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#d58b5d8e-4876-4edf-aa4b-6a83e278d12f 
13.05.20 13:07:30 (+0900) <fleet-supervisor> ========================
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#e12c5aa5-c736-4e0f-b81e-3990130b3c24 on 8000 
13.05.20 13:07:30 (+0900) <fleet-supervisor> ========================
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#e12c5aa5-c736-4e0f-b81e-3990130b3c24 on 8000
13.05.20 13:07:30 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:07:30 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:07:30 (+0900) <fleet-supervisor>       ^
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:07:30 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:07:30 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:07:30 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:07:30 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:07:30 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:07:30 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:07:30 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:07:30 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:07:30 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:07:30 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:07:30 (+0900) <fleet-supervisor> }
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:07:30 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_07_30_306Z-debug.log
13.05.20 13:07:30 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:07:30 (+0900) <fleet-supervisor> 
13.05.20 13:08:03 (+0900) Killing service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:08:03 (+0900) Killed service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:08:03 (+0900) Killing service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:08:03 (+0900) Service is already stopped, removing container 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:08:03 (+0900) Killed service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:08:03 (+0900) Killing service 'snapcast-client sha256:4f41cb475c12960309a03a206081927edd06ff3337c1c584a354de5c845ba46a'
13.05.20 13:08:14 (+0900) Service exited 'snapcast-client sha256:4f41cb475c12960309a03a206081927edd06ff3337c1c584a354de5c845ba46a'
13.05.20 13:08:14 (+0900) Killed service 'snapcast-client sha256:4f41cb475c12960309a03a206081927edd06ff3337c1c584a354de5c845ba46a'
13.05.20 13:08:14 (+0900) Killing service 'airplay sha256:1a5011d9ea3deff9d91d89c7f81fafe038f5780caed88cb44d6bfe9b6503062a'
13.05.20 13:08:25 (+0900) Killed service 'airplay sha256:1a5011d9ea3deff9d91d89c7f81fafe038f5780caed88cb44d6bfe9b6503062a'
13.05.20 13:08:25 (+0900) Service exited 'airplay sha256:1a5011d9ea3deff9d91d89c7f81fafe038f5780caed88cb44d6bfe9b6503062a'
13.05.20 13:08:25 (+0900) Killing service 'spotify sha256:615d584535efbe1373c26bf8d6107f9dee2b7239657923352ffeb0e9fa7851db'
13.05.20 13:08:36 (+0900) Killed service 'spotify sha256:615d584535efbe1373c26bf8d6107f9dee2b7239657923352ffeb0e9fa7851db'
13.05.20 13:08:36 (+0900) Service exited 'spotify sha256:615d584535efbe1373c26bf8d6107f9dee2b7239657923352ffeb0e9fa7851db'
13.05.20 13:08:36 (+0900) Killing service 'bluetooth-audio sha256:48a8401a367d4bf0eadbcd1e97a86b1944af5250242d063da00d9f82a349c1a3'
13.05.20 13:08:37 (+0900) Killed service 'bluetooth-audio sha256:48a8401a367d4bf0eadbcd1e97a86b1944af5250242d063da00d9f82a349c1a3'
13.05.20 13:08:37 (+0900) Rebooting
13.05.20 13:08:37 (+0900) Service exited 'bluetooth-audio sha256:48a8401a367d4bf0eadbcd1e97a86b1944af5250242d063da00d9f82a349c1a3'
13.05.20 13:09:34 (+0900) Supervisor starting
13.05.20 13:09:27 (+0900) <fleet-supervisor> OK
13.05.20 13:09:27 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:27 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:27 (+0900) <fleet-supervisor> 
13.05.20 13:09:28 (+0900) <fleet-supervisor> Error: Command failed: curl -s -X GET --header "Content-Type:application/json" "$BALENA_SUPERVISOR_ADDRESS/v1/device?apikey=$BALENA_SUPERVISOR_API_KEY"
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at checkExecSyncError (child_process.js:611:11)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at execSync (child_process.js:647:15)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at module.exports.getIPAddress (/usr/src/src/utils.js:8:16)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Object.<anonymous> (/usr/src/server.js:7:57)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Module._compile (internal/modules/cjs/loader.js:1185:30)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1205:10)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Module.load (internal/modules/cjs/loader.js:1034:32)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Function.Module._load (internal/modules/cjs/loader.js:923:14)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
13.05.20 13:09:28 (+0900) <fleet-supervisor>     at internal/main/run_main_module.js:17:47 {
13.05.20 13:09:28 (+0900) <fleet-supervisor>   status: 7,
13.05.20 13:09:28 (+0900) <fleet-supervisor>   signal: null,
13.05.20 13:09:28 (+0900) <fleet-supervisor>   output: [ null, <Buffer >, <Buffer > ],
13.05.20 13:09:28 (+0900) <fleet-supervisor>   pid: 48,
13.05.20 13:09:28 (+0900) <fleet-supervisor>   stdout: <Buffer >,
13.05.20 13:09:28 (+0900) <fleet-supervisor>   stderr: <Buffer >
13.05.20 13:09:28 (+0900) <fleet-supervisor> }
13.05.20 13:09:28 (+0900) <fleet-supervisor> 
13.05.20 13:09:28 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#90d59533-c841-4347-8f35-a4c345ab368b 
13.05.20 13:09:28 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:28 (+0900) <fleet-supervisor> 
13.05.20 13:09:29 (+0900) <fleet-supervisor> 
13.05.20 13:09:29 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#3114caf2-786f-4ebe-8476-064d9d980560 on 8000 
13.05.20 13:09:29 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:29 (+0900) <fleet-supervisor> 
13.05.20 13:09:29 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#3114caf2-786f-4ebe-8476-064d9d980560 on 8000
13.05.20 13:09:29 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:29 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:29 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:29 (+0900) <fleet-supervisor> 
13.05.20 13:09:29 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:29 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:29 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:29 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:29 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:29 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:29 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:29 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:29 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:29 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:29 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:29 (+0900) <fleet-supervisor> }
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:29 (+0900) <fleet-supervisor> 
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:29 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_29_115Z-debug.log
13.05.20 13:09:26 (+0900) <bluetooth-audio> Setting output volume to 75%
13.05.20 13:09:26 (+0900) <bluetooth-audio> Connection notify volume is 75%
13.05.20 13:09:27 (+0900) <bluetooth-audio> amixer: Unable to find simple control 'Digital',0
13.05.20 13:09:27 (+0900) <bluetooth-audio> 
13.05.20 13:09:27 (+0900) <bluetooth-audio> Restarting bluetooth service
13.05.20 13:09:30 (+0900) <bluetooth-audio> Bluetooth agent registered
13.05.20 13:09:32 (+0900) <bluetooth-audio> Starting bluetooth agent in Secure Simple Pairing Mode (SSPM) - No PIN code provided or invalid
13.05.20 13:09:34 (+0900) <bluetooth-audio> Attempting to reconnect to previous bluetooth device: 28:F0:76:E0:65:F4
13.05.20 13:09:35 (+0900) Starting service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:09:36 (+0900) <bluetooth-audio> Device is discoverable as "test2"
13.05.20 13:09:37 (+0900) Started service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:09:29 (+0900) <fleet-supervisor> 2020-05-13T04:09:37.720534000Z OK
13.05.20 13:09:37 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:37 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:37 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) Service exited 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#5942570c-343a-46d9-82a2-2a6c26e5d6b9 
13.05.20 13:09:38 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#fc4a1612-ec72-47d9-b276-59fafb18c575 on 8000 
13.05.20 13:09:38 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#fc4a1612-ec72-47d9-b276-59fafb18c575 on 8000
13.05.20 13:09:38 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:38 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:38 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:38 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:38 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:38 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:38 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:38 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:38 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:38 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:38 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:38 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:38 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:38 (+0900) <fleet-supervisor> }
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:38 (+0900) <fleet-supervisor> 
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:38 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_38_744Z-debug.log
13.05.20 13:09:39 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:39 (+0900) <fleet-supervisor> 
13.05.20 13:09:40 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:39 (+0900) <fleet-supervisor> 2020-05-13T04:09:40.947745000Z OK
13.05.20 13:09:40 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:40 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:40 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#c93eb4f6-ec55-40ed-82e3-46ad0749599c 
13.05.20 13:09:41 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#ae648a06-7657-4668-9112-19250f2bc035 on 8000 
13.05.20 13:09:41 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#ae648a06-7657-4668-9112-19250f2bc035 on 8000
13.05.20 13:09:41 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:41 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:41 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:41 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:41 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:41 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:41 (+0900) <fleet-supervisor> }
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_41_596Z-debug.log
13.05.20 13:09:42 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:43 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#c93eb4f6-ec55-40ed-82e3-46ad0749599c 
13.05.20 13:09:41 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#ae648a06-7657-4668-9112-19250f2bc035 on 8000 
13.05.20 13:09:41 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#ae648a06-7657-4668-9112-19250f2bc035 on 8000
13.05.20 13:09:41 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:41 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:41 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:41 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:41 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:41 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:41 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:41 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:41 (+0900) <fleet-supervisor> }
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:41 (+0900) <fleet-supervisor> 
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:41 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_41_596Z-debug.log
13.05.20 13:09:41 (+0900) <fleet-supervisor> 2020-05-13T04:09:44.020518000Z OK
13.05.20 13:09:44 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:44 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#7db77f68-fdc4-4649-aaa3-14256daa92ee 
13.05.20 13:09:44 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#80f074d0-f20b-46da-adce-bc0cd8562b74 on 8000 
13.05.20 13:09:44 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#80f074d0-f20b-46da-adce-bc0cd8562b74 on 8000
13.05.20 13:09:44 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:44 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:44 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:44 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:44 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:44 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:44 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:44 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:44 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:44 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:44 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:44 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:44 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:44 (+0900) <fleet-supervisor> }
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:44 (+0900) <fleet-supervisor> 
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:44 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_44_670Z-debug.log
13.05.20 13:09:45 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:45 (+0900) <fleet-supervisor> 
13.05.20 13:09:46 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:45 (+0900) <fleet-supervisor> 2020-05-13T04:09:47.510288000Z OK
13.05.20 13:09:47 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:47 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:47 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#23d63173-59f4-4573-88cc-78693f5b9e11 
13.05.20 13:09:48 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#351e50cd-57c6-4812-aeea-18eb0f9b2404 on 8000 
13.05.20 13:09:48 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#351e50cd-57c6-4812-aeea-18eb0f9b2404 on 8000
13.05.20 13:09:48 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:48 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:48 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:48 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:48 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:48 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:48 (+0900) <fleet-supervisor> }
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_48_164Z-debug.log
13.05.20 13:09:48 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:51 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#23d63173-59f4-4573-88cc-78693f5b9e11 
13.05.20 13:09:48 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#351e50cd-57c6-4812-aeea-18eb0f9b2404 on 8000 
13.05.20 13:09:48 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#351e50cd-57c6-4812-aeea-18eb0f9b2404 on 8000
13.05.20 13:09:48 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:48 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:48 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:48 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:48 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:48 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:48 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:48 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:48 (+0900) <fleet-supervisor> }
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:48 (+0900) <fleet-supervisor> 
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:48 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_48_164Z-debug.log
13.05.20 13:09:48 (+0900) <fleet-supervisor> 2020-05-13T04:09:51.904160000Z OK
13.05.20 13:09:51 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:51 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:51 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#199ee047-dcc6-4cff-b5b6-5acf5ca8a334 
13.05.20 13:09:52 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#2ec413e2-12fe-4f30-aa59-2cf77328a4cd on 8000 
13.05.20 13:09:52 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#2ec413e2-12fe-4f30-aa59-2cf77328a4cd on 8000
13.05.20 13:09:52 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:52 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:52 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:52 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:52 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:52 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:52 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:52 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:52 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:52 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:52 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:52 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:52 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:52 (+0900) <fleet-supervisor> }
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:52 (+0900) <fleet-supervisor> 
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:52 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_52_686Z-debug.log
13.05.20 13:09:53 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:53 (+0900) <fleet-supervisor> 
13.05.20 13:09:57 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:53 (+0900) <fleet-supervisor> 2020-05-13T04:09:58.139223000Z OK
13.05.20 13:09:58 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:09:58 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#2e11fac7-787e-4977-95d4-23bc2a87177d 
13.05.20 13:09:58 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#b38b8065-f20e-4c22-9719-0f4c9b360446 on 8000 
13.05.20 13:09:58 (+0900) <fleet-supervisor> ========================
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#b38b8065-f20e-4c22-9719-0f4c9b360446 on 8000
13.05.20 13:09:58 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:09:58 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:09:58 (+0900) <fleet-supervisor>       ^
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:09:58 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:09:58 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:09:58 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:09:58 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:09:58 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:09:58 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:09:58 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:09:58 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:09:58 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:09:58 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:09:58 (+0900) <fleet-supervisor> }
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:09:58 (+0900) <fleet-supervisor> 
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:09:58 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_09_58_785Z-debug.log
13.05.20 13:09:59 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:59 (+0900) <fleet-supervisor> 
13.05.20 13:10:06 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:09:59 (+0900) <fleet-supervisor> 2020-05-13T04:10:07.197734000Z OK
13.05.20 13:10:07 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
13.05.20 13:10:07 (+0900) <fleet-supervisor> > node server.js
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#b71d6f8b-bc73-4200-9b2d-49fa996d39c5 
13.05.20 13:10:07 (+0900) <fleet-supervisor> ========================
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#24e6004a-de4c-4c5d-8025-36bdec1d27b5 on 8000 
13.05.20 13:10:07 (+0900) <fleet-supervisor> ========================
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#24e6004a-de4c-4c5d-8025-36bdec1d27b5 on 8000
13.05.20 13:10:07 (+0900) <fleet-supervisor> events.js:292
13.05.20 13:10:07 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
13.05.20 13:10:07 (+0900) <fleet-supervisor>       ^
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
13.05.20 13:10:07 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
13.05.20 13:10:07 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
13.05.20 13:10:07 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
13.05.20 13:10:07 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
13.05.20 13:10:07 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
13.05.20 13:10:07 (+0900) <fleet-supervisor>   errno: -111,
13.05.20 13:10:07 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
13.05.20 13:10:07 (+0900) <fleet-supervisor>   syscall: 'connect',
13.05.20 13:10:07 (+0900) <fleet-supervisor>   address: '127.0.0.1',
13.05.20 13:10:07 (+0900) <fleet-supervisor>   port: 1705
13.05.20 13:10:07 (+0900) <fleet-supervisor> }
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! errno 1
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! Exit status 1
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! 
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
13.05.20 13:10:07 (+0900) <fleet-supervisor> 
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
13.05.20 13:10:07 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-13T04_10_07_840Z-debug.log
13.05.20 13:10:08 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
13.05.20 13:10:08 (+0900) <fleet-supervisor>