08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:65
08.05.20 13:21:52 (+0900) <spotify>    7:   0x9e9954 - std::sys_common::backtrace::print::hec570bc9fdd6a536
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:50
08.05.20 13:21:52 (+0900) <spotify>    8:   0x9e9954 - std::panicking::default_hook::{{closure}}::hf187be78db8e291b
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:193
08.05.20 13:21:52 (+0900) <spotify>    9:   0x9e95b4 - std::panicking::default_hook::h9634e45fc0d61ba6
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:210
08.05.20 13:21:52 (+0900) <spotify>   10:   0x9ea030 - std::panicking::rust_panic_with_hook::h35923fdea5783220
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:471
08.05.20 13:21:52 (+0900) <spotify>   11:   0x9e9c48 - rust_begin_unwind
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:375
08.05.20 13:21:52 (+0900) <spotify>   12:   0xa05ac0 - core::panicking::panic_fmt::hd74e307162bc16e5
08.05.20 13:21:52 (+0900) <spotify>                        at src/libcore/panicking.rs:84
08.05.20 13:21:52 (+0900) <spotify>   13:   0xa05bac - core::result::unwrap_failed::h36f73057b442c0eb
08.05.20 13:21:52 (+0900) <spotify>                        at src/libcore/result.rs:1188
08.05.20 13:21:52 (+0900) <spotify>   14:   0x5215e0 - librespot::main::h0ed06a728ac2479f
08.05.20 13:21:52 (+0900) <spotify>   15:   0x522980 - std::rt::lang_start::{{closure}}::h3ecc962e3fb4564b
08.05.20 13:21:52 (+0900) <spotify>   16:   0x9e9ac4 - std::rt::lang_start_internal::{{closure}}::hc02935a73664ebd0
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/rt.rs:52
08.05.20 13:21:52 (+0900) <spotify>   17:   0x9e9ac4 - std::panicking::try::do_call::h9ca5184b6b3cc62d
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:292
08.05.20 13:21:52 (+0900) <spotify>   18:   0x9f1220 - __rust_maybe_catch_panic
08.05.20 13:21:52 (+0900) <spotify>                        at src/libpanic_unwind/lib.rs:78
08.05.20 13:21:52 (+0900) <spotify>   19:   0x9ea484 - std::panicking::try::hc53e4a11b02f3299
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panicking.rs:270
08.05.20 13:21:52 (+0900) <spotify>   20:   0x9ea484 - std::panic::catch_unwind::ha972c7f8a413a94c
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/panic.rs:394
08.05.20 13:21:52 (+0900) <spotify>   21:   0x9ea484 - std::rt::lang_start_internal::hdf6cc497202d2594
08.05.20 13:21:52 (+0900) <spotify>                        at src/libstd/rt.rs:51
08.05.20 13:21:52 (+0900) <spotify>   22:   0x521dc4 - main
08.05.20 13:21:52 (+0900) <spotify>   23: 0xf7c4f524 - __libc_start_main
08.05.20 13:21:55 (+0900) <spotify> [2020-05-08T04:21:55Z INFO  librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16. Build ID: 7pZDdYUK
08.05.20 13:21:55 (+0900) <spotify> thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 19, kind: Other, message: "No such device" }', src/libcore/result.rs:1188:5
08.05.20 13:21:55 (+0900) <spotify> stack backtrace:
08.05.20 13:21:55 (+0900) <spotify>    0:   0xd883a4 - backtrace::backtrace::libunwind::trace::hb1e9954dcc6e7c1f
08.05.20 13:21:55 (+0900) <spotify>                        at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
08.05.20 13:21:55 (+0900) <spotify>    1:   0xd883a4 - backtrace::backtrace::trace_unsynchronized::h1b198a73034a9734
08.05.20 13:21:55 (+0900) <spotify>                        at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
08.05.20 13:21:55 (+0900) <spotify>    2:   0xd883a4 - std::sys_common::backtrace::_print_fmt::hf691518b63d0b79d
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:84
08.05.20 13:21:55 (+0900) <spotify>    3:   0xd883a4 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::he6a16924c7e1913e
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:61
08.05.20 13:21:55 (+0900) <spotify>    4:   0xdaaca4 - core::fmt::write::hc426988e4c4119a8
08.05.20 13:21:55 (+0900) <spotify>                        at src/libcore/fmt/mod.rs:1025
08.05.20 13:21:55 (+0900) <spotify>    5:   0xd82ff0 - std::io::Write::write_fmt::h34e90dde595ba7cd
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/io/mod.rs:1426
08.05.20 13:21:55 (+0900) <spotify>    6:   0xd8a954 - std::sys_common::backtrace::_print::h406863a8800396cd
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:65
08.05.20 13:21:55 (+0900) <spotify>    7:   0xd8a954 - std::sys_common::backtrace::print::hec570bc9fdd6a536
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/sys_common/backtrace.rs:50
08.05.20 13:21:55 (+0900) <spotify>    8:   0xd8a954 - std::panicking::default_hook::{{closure}}::hf187be78db8e291b
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:193
08.05.20 13:21:55 (+0900) <spotify>    9:   0xd8a5b4 - std::panicking::default_hook::h9634e45fc0d61ba6
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:210
08.05.20 13:21:55 (+0900) <spotify>   10:   0xd8b030 - std::panicking::rust_panic_with_hook::h35923fdea5783220
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:471
08.05.20 13:21:55 (+0900) <spotify>   11:   0xd8ac48 - rust_begin_unwind
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:375
08.05.20 13:21:55 (+0900) <spotify>   12:   0xda6ac0 - core::panicking::panic_fmt::hd74e307162bc16e5
08.05.20 13:21:55 (+0900) <spotify>                        at src/libcore/panicking.rs:84
08.05.20 13:21:55 (+0900) <spotify>   13:   0xda6bac - core::result::unwrap_failed::h36f73057b442c0eb
08.05.20 13:21:55 (+0900) <spotify>                        at src/libcore/result.rs:1188
08.05.20 13:21:55 (+0900) <spotify>   14:   0x8c25e0 - librespot::main::h0ed06a728ac2479f
08.05.20 13:21:55 (+0900) <spotify>   15:   0x8c3980 - std::rt::lang_start::{{closure}}::h3ecc962e3fb4564b
08.05.20 13:21:55 (+0900) <spotify>   16:   0xd8aac4 - std::rt::lang_start_internal::{{closure}}::hc02935a73664ebd0
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/rt.rs:52
08.05.20 13:21:55 (+0900) <spotify>   17:   0xd8aac4 - std::panicking::try::do_call::h9ca5184b6b3cc62d
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:292
08.05.20 13:21:55 (+0900) <spotify>   18:   0xd92220 - __rust_maybe_catch_panic
08.05.20 13:21:55 (+0900) <spotify>                        at src/libpanic_unwind/lib.rs:78
08.05.20 13:21:55 (+0900) <spotify>   19:   0xd8b484 - std::panicking::try::hc53e4a11b02f3299
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panicking.rs:270
08.05.20 13:21:55 (+0900) <spotify>   20:   0xd8b484 - std::panic::catch_unwind::ha972c7f8a413a94c
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/panic.rs:394
08.05.20 13:21:55 (+0900) <spotify>   21:   0xd8b484 - std::rt::lang_start_internal::hdf6cc497202d2594
08.05.20 13:21:55 (+0900) <spotify>                        at src/libstd/rt.rs:51
08.05.20 13:21:55 (+0900) <spotify>   22:   0x8c2dc4 - main
08.05.20 13:21:55 (+0900) <spotify>   23: 0xf7bba524 - __libc_start_main
08.05.20 13:21:57 (+0900) <spotify> [2020-05-08T04:21:57Z INFO  librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16. Build ID: 7pZDdYUK
11.05.20 10:14:30 (+0900) <bluetooth-audio> Setting output volume to 75%
11.05.20 10:14:30 (+0900) <bluetooth-audio> Connection notify volume is 75%
11.05.20 10:14:30 (+0900) <bluetooth-audio> amixer: Unable to find simple control 'Digital',0
11.05.20 10:14:30 (+0900) <bluetooth-audio> 
11.05.20 10:14:30 (+0900) <bluetooth-audio> Restarting bluetooth service
11.05.20 10:14:34 (+0900) <bluetooth-audio> Bluetooth agent registered
11.05.20 10:14:35 (+0900) <bluetooth-audio> Starting bluetooth agent in Secure Simple Pairing Mode (SSPM) - No PIN code provided or invalid
11.05.20 10:14:37 (+0900) <bluetooth-audio> Attempting to reconnect to previous bluetooth device: 28:F0:76:E0:65:F4
11.05.20 10:14:38 (+0900) Starting service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
11.05.20 10:14:39 (+0900) <bluetooth-audio> Device is discoverable as "test1"
11.05.20 10:14:40 (+0900) Started service 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
11.05.20 10:14:32 (+0900) <fleet-supervisor> 2020-05-11T01:14:40.770396000Z OK
11.05.20 10:14:40 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:14:40 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:14:40 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) Service exited 'snapcast-server sha256:3d59dbfa4b646f2b683421babb0ce1a7c584ac4e8bd0025696334590ed0425a7'
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#f200a3c2-d534-4768-8557-ebae67623142 
11.05.20 10:14:41 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#f1d9cfae-26f8-43b9-a3eb-7ee1062d9782 on 8000 
11.05.20 10:14:41 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#f1d9cfae-26f8-43b9-a3eb-7ee1062d9782 on 8000
11.05.20 10:14:41 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:41 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:41 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:41 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:41 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:41 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:41 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:41 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:41 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:41 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:41 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:41 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:41 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:41 (+0900) <fleet-supervisor> }
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:41 (+0900) <fleet-supervisor> 
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:41 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_41_897Z-debug.log
11.05.20 10:14:42 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:42 (+0900) <fleet-supervisor> 
11.05.20 10:14:43 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:42 (+0900) <fleet-supervisor> 2020-05-11T01:14:44.179481000Z OK
11.05.20 10:14:44 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:14:44 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#8779734b-feec-435f-8726-943b20b8ded8 
11.05.20 10:14:44 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#98cbe049-540d-43e5-a2a3-006d5a2f8264 on 8000 
11.05.20 10:14:44 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#98cbe049-540d-43e5-a2a3-006d5a2f8264 on 8000
11.05.20 10:14:44 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:44 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:44 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:44 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:44 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:44 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:44 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:44 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:44 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:44 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:44 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:44 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:44 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:44 (+0900) <fleet-supervisor> }
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:44 (+0900) <fleet-supervisor> 
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:44 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_44_842Z-debug.log
11.05.20 10:14:45 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:45 (+0900) <fleet-supervisor> 
11.05.20 10:14:46 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:45 (+0900) <fleet-supervisor> 2020-05-11T01:14:47.595300000Z OK
11.05.20 10:14:47 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:14:47 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:14:47 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#1424190d-2ec6-4765-830a-f406823ddc88 
11.05.20 10:14:48 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#11da1f76-98e2-4496-82e9-09e56d3a8fc8 on 8000 
11.05.20 10:14:48 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#11da1f76-98e2-4496-82e9-09e56d3a8fc8 on 8000
11.05.20 10:14:48 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:48 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:48 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:48 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:48 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:48 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:48 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:48 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:48 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:48 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:48 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:48 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:48 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:48 (+0900) <fleet-supervisor> }
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:48 (+0900) <fleet-supervisor> 
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:48 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_48_601Z-debug.log
11.05.20 10:14:49 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:49 (+0900) <fleet-supervisor> 
11.05.20 10:14:50 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:49 (+0900) <fleet-supervisor> 2020-05-11T01:14:51.452266000Z OK
11.05.20 10:14:51 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:14:51 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:14:51 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#8baa4392-ebd7-4d2b-add3-5849e2bb97b1 
11.05.20 10:14:52 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#97373d14-39ac-4a4d-9651-8b9670592215 on 8000 
11.05.20 10:14:52 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#97373d14-39ac-4a4d-9651-8b9670592215 on 8000
11.05.20 10:14:52 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:52 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:52 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:52 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:52 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:52 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:52 (+0900) <fleet-supervisor> }
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_52_144Z-debug.log
11.05.20 10:14:52 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:55 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#8baa4392-ebd7-4d2b-add3-5849e2bb97b1 
11.05.20 10:14:52 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#97373d14-39ac-4a4d-9651-8b9670592215 on 8000 
11.05.20 10:14:52 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#97373d14-39ac-4a4d-9651-8b9670592215 on 8000
11.05.20 10:14:52 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:52 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:52 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:52 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:52 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:52 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:52 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:52 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:52 (+0900) <fleet-supervisor> }
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:52 (+0900) <fleet-supervisor> 
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:52 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_52_144Z-debug.log
11.05.20 10:14:52 (+0900) <fleet-supervisor> 2020-05-11T01:14:55.835620000Z OK
11.05.20 10:14:55 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:14:55 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:14:55 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#08cc5392-a8c1-4981-abd2-1b7f67491552 
11.05.20 10:14:56 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#f0b4b55e-7c1d-4b9e-866f-16f16352629f on 8000 
11.05.20 10:14:56 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#f0b4b55e-7c1d-4b9e-866f-16f16352629f on 8000
11.05.20 10:14:56 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:56 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:56 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:56 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:56 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:56 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:56 (+0900) <fleet-supervisor> }
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_56_485Z-debug.log
11.05.20 10:14:57 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:15:00 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#08cc5392-a8c1-4981-abd2-1b7f67491552 
11.05.20 10:14:56 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#f0b4b55e-7c1d-4b9e-866f-16f16352629f on 8000 
11.05.20 10:14:56 (+0900) <fleet-supervisor> ========================
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#f0b4b55e-7c1d-4b9e-866f-16f16352629f on 8000
11.05.20 10:14:56 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:14:56 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:14:56 (+0900) <fleet-supervisor>       ^
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:14:56 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:14:56 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:14:56 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:14:56 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:14:56 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:14:56 (+0900) <fleet-supervisor> }
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:14:56 (+0900) <fleet-supervisor> 
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:14:56 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_14_56_485Z-debug.log
11.05.20 10:14:56 (+0900) <fleet-supervisor> 2020-05-11T01:15:01.713648000Z OK
11.05.20 10:15:01 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:15:01 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:15:01 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#677f85c3-d60e-482b-a33c-1c91bcc2ace8 
11.05.20 10:15:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#92df3dda-def7-4c4a-bdf2-42dadf58b784 on 8000 
11.05.20 10:15:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#92df3dda-def7-4c4a-bdf2-42dadf58b784 on 8000
11.05.20 10:15:02 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:02 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:02 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:02 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:02 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:02 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:02 (+0900) <fleet-supervisor> }
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_02_347Z-debug.log
11.05.20 10:15:02 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:10 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#677f85c3-d60e-482b-a33c-1c91bcc2ace8 
11.05.20 10:15:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#92df3dda-def7-4c4a-bdf2-42dadf58b784 on 8000 
11.05.20 10:15:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#92df3dda-def7-4c4a-bdf2-42dadf58b784 on 8000
11.05.20 10:15:02 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:02 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:02 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:02 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:02 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:02 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:02 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:02 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:02 (+0900) <fleet-supervisor> }
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:02 (+0900) <fleet-supervisor> 
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:02 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_02_347Z-debug.log
11.05.20 10:15:02 (+0900) <fleet-supervisor> 2020-05-11T01:15:10.755127000Z OK
11.05.20 10:15:10 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:15:10 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:15:10 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#4dad26b6-a559-442f-9457-800c6fdcde4b 
11.05.20 10:15:11 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#2002b1c4-24a9-4567-b69d-c28a094fe169 on 8000 
11.05.20 10:15:11 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#2002b1c4-24a9-4567-b69d-c28a094fe169 on 8000
11.05.20 10:15:11 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:11 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:11 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:11 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:11 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:11 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:11 (+0900) <fleet-supervisor> }
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_11_394Z-debug.log
11.05.20 10:15:11 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:25 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#4dad26b6-a559-442f-9457-800c6fdcde4b 
11.05.20 10:15:11 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#2002b1c4-24a9-4567-b69d-c28a094fe169 on 8000 
11.05.20 10:15:11 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#2002b1c4-24a9-4567-b69d-c28a094fe169 on 8000
11.05.20 10:15:11 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:11 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:11 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:11 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:11 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:11 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:11 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:11 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:11 (+0900) <fleet-supervisor> }
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:11 (+0900) <fleet-supervisor> 
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:11 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_11_394Z-debug.log
11.05.20 10:15:11 (+0900) <fleet-supervisor> 2020-05-11T01:15:26.209423000Z OK
11.05.20 10:15:26 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:15:26 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#e818f2f3-4590-4db8-a673-17119f626493 
11.05.20 10:15:26 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#3eb85936-c530-4af2-914d-0d71d562c9a3 on 8000 
11.05.20 10:15:26 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#3eb85936-c530-4af2-914d-0d71d562c9a3 on 8000
11.05.20 10:15:26 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:26 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:26 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:26 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:26 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:26 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:26 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:26 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:26 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:26 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:26 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:26 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:26 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:26 (+0900) <fleet-supervisor> }
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:26 (+0900) <fleet-supervisor> 
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:26 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_26_847Z-debug.log
11.05.20 10:15:27 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:27 (+0900) <fleet-supervisor> 
11.05.20 10:15:53 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:27 (+0900) <fleet-supervisor> 2020-05-11T01:15:54.535404000Z OK
11.05.20 10:15:54 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:15:54 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:15:54 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#356595f3-86e8-4210-a51c-84b17ddb4864 
11.05.20 10:15:55 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#0816427a-75fc-418a-81dc-9fabe054b284 on 8000 
11.05.20 10:15:55 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#0816427a-75fc-418a-81dc-9fabe054b284 on 8000
11.05.20 10:15:55 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:55 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:55 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:55 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:55 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:55 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:55 (+0900) <fleet-supervisor> }
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_55_179Z-debug.log
11.05.20 10:15:55 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:16:47 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#356595f3-86e8-4210-a51c-84b17ddb4864 
11.05.20 10:15:55 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#0816427a-75fc-418a-81dc-9fabe054b284 on 8000 
11.05.20 10:15:55 (+0900) <fleet-supervisor> ========================
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#0816427a-75fc-418a-81dc-9fabe054b284 on 8000
11.05.20 10:15:55 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:15:55 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:15:55 (+0900) <fleet-supervisor>       ^
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:15:55 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:15:55 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:15:55 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:15:55 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:15:55 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:15:55 (+0900) <fleet-supervisor> }
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:15:55 (+0900) <fleet-supervisor> 
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:15:55 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_15_55_179Z-debug.log
11.05.20 10:15:55 (+0900) <fleet-supervisor> 2020-05-11T01:16:48.507026000Z OK
11.05.20 10:16:48 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:16:48 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:16:48 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#ff4be11f-4a67-4425-afa4-e44da2a9bc02 
11.05.20 10:16:49 (+0900) <fleet-supervisor> ========================
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#632764cd-76a9-427f-9a94-5a21d655b716 on 8000 
11.05.20 10:16:49 (+0900) <fleet-supervisor> ========================
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#632764cd-76a9-427f-9a94-5a21d655b716 on 8000
11.05.20 10:16:49 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:16:49 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:16:49 (+0900) <fleet-supervisor>       ^
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:16:49 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:16:49 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:16:49 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:16:49 (+0900) <fleet-supervisor> }
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_16_49_149Z-debug.log
11.05.20 10:16:49 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:17:50 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#ff4be11f-4a67-4425-afa4-e44da2a9bc02 
11.05.20 10:16:49 (+0900) <fleet-supervisor> ========================
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#632764cd-76a9-427f-9a94-5a21d655b716 on 8000 
11.05.20 10:16:49 (+0900) <fleet-supervisor> ========================
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#632764cd-76a9-427f-9a94-5a21d655b716 on 8000
11.05.20 10:16:49 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:16:49 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:16:49 (+0900) <fleet-supervisor>       ^
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:16:49 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:16:49 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:16:49 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:16:49 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:16:49 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:16:49 (+0900) <fleet-supervisor> }
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:16:49 (+0900) <fleet-supervisor> 
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:16:49 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_16_49_149Z-debug.log
11.05.20 10:16:49 (+0900) <fleet-supervisor> 2020-05-11T01:17:51.190111000Z OK
11.05.20 10:17:51 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:17:51 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#b5cfe9d9-3c5e-46b5-b0ef-aa904ac6f0f5 
11.05.20 10:17:51 (+0900) <fleet-supervisor> ========================
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#b66ce865-9fa8-4eb9-835e-6f1b4226f98c on 8000 
11.05.20 10:17:51 (+0900) <fleet-supervisor> ========================
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#b66ce865-9fa8-4eb9-835e-6f1b4226f98c on 8000
11.05.20 10:17:51 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:17:51 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:17:51 (+0900) <fleet-supervisor>       ^
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:17:51 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:17:51 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:17:51 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:17:51 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:17:51 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:17:51 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:17:51 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:17:51 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:17:51 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:17:51 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:17:51 (+0900) <fleet-supervisor> }
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:17:51 (+0900) <fleet-supervisor> 
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:17:51 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_17_51_836Z-debug.log
11.05.20 10:17:52 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:17:52 (+0900) <fleet-supervisor> 
11.05.20 10:18:53 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:17:52 (+0900) <fleet-supervisor> 2020-05-11T01:18:53.890125000Z OK
11.05.20 10:18:53 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:18:53 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:18:53 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#b21437b1-cde3-4b31-80e9-ab269b6ec880 
11.05.20 10:18:54 (+0900) <fleet-supervisor> ========================
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#a9e25541-80de-4fa3-bded-b596a291405f on 8000 
11.05.20 10:18:54 (+0900) <fleet-supervisor> ========================
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#a9e25541-80de-4fa3-bded-b596a291405f on 8000
11.05.20 10:18:54 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:18:54 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:18:54 (+0900) <fleet-supervisor>       ^
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:18:54 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:18:54 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:18:54 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:18:54 (+0900) <fleet-supervisor> }
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_18_54_536Z-debug.log
11.05.20 10:18:55 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:19:55 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#b21437b1-cde3-4b31-80e9-ab269b6ec880 
11.05.20 10:18:54 (+0900) <fleet-supervisor> ========================
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#a9e25541-80de-4fa3-bded-b596a291405f on 8000 
11.05.20 10:18:54 (+0900) <fleet-supervisor> ========================
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#a9e25541-80de-4fa3-bded-b596a291405f on 8000
11.05.20 10:18:54 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:18:54 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:18:54 (+0900) <fleet-supervisor>       ^
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:18:54 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:18:54 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:18:54 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:18:54 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:18:54 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:18:54 (+0900) <fleet-supervisor> }
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:18:54 (+0900) <fleet-supervisor> 
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:18:54 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_18_54_536Z-debug.log
11.05.20 10:18:54 (+0900) <fleet-supervisor> 2020-05-11T01:19:56.612903000Z OK
11.05.20 10:19:56 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:19:56 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:19:56 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#946ccdc8-6212-476b-b9b6-fe1713cf6db2 
11.05.20 10:19:57 (+0900) <fleet-supervisor> ========================
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#b3b74de4-880b-4ffa-ac2f-07bf6c207322 on 8000 
11.05.20 10:19:57 (+0900) <fleet-supervisor> ========================
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#b3b74de4-880b-4ffa-ac2f-07bf6c207322 on 8000
11.05.20 10:19:57 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:19:57 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:19:57 (+0900) <fleet-supervisor>       ^
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:19:57 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:19:57 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:19:57 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:19:57 (+0900) <fleet-supervisor> }
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_19_57_253Z-debug.log
11.05.20 10:19:57 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:20:58 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#946ccdc8-6212-476b-b9b6-fe1713cf6db2 
11.05.20 10:19:57 (+0900) <fleet-supervisor> ========================
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#b3b74de4-880b-4ffa-ac2f-07bf6c207322 on 8000 
11.05.20 10:19:57 (+0900) <fleet-supervisor> ========================
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#b3b74de4-880b-4ffa-ac2f-07bf6c207322 on 8000
11.05.20 10:19:57 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:19:57 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:19:57 (+0900) <fleet-supervisor>       ^
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:19:57 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:19:57 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:19:57 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:19:57 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:19:57 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:19:57 (+0900) <fleet-supervisor> }
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:19:57 (+0900) <fleet-supervisor> 
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:19:57 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_19_57_253Z-debug.log
11.05.20 10:19:57 (+0900) <fleet-supervisor> 2020-05-11T01:20:59.288308000Z OK
11.05.20 10:20:59 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:20:59 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#4c8cf1e9-2dca-4ec1-ba68-b1209f57dd4a 
11.05.20 10:20:59 (+0900) <fleet-supervisor> ========================
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#81846919-b8a7-4cd1-8f2c-a7f29c5ffa93 on 8000 
11.05.20 10:20:59 (+0900) <fleet-supervisor> ========================
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#81846919-b8a7-4cd1-8f2c-a7f29c5ffa93 on 8000
11.05.20 10:20:59 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:20:59 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:20:59 (+0900) <fleet-supervisor>       ^
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:20:59 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:20:59 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:20:59 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:20:59 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:20:59 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:20:59 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:20:59 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:20:59 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:20:59 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:20:59 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:20:59 (+0900) <fleet-supervisor> }
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:20:59 (+0900) <fleet-supervisor> 
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:20:59 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_20_59_962Z-debug.log
11.05.20 10:21:00 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:21:00 (+0900) <fleet-supervisor> 
11.05.20 10:22:01 (+0900) Restarting service 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:21:00 (+0900) <fleet-supervisor> 2020-05-11T01:22:02.060711000Z OK
11.05.20 10:22:02 (+0900) <fleet-supervisor> > fleet-supervisor@1.0.0 start /usr/src
11.05.20 10:22:02 (+0900) <fleet-supervisor> > node server.js
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> Hello! I'm Fleet subscriber#70cfa1aa-08ed-46f5-b27f-d026d3810cb9 
11.05.20 10:22:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> Hello! I'm Fleet publisher#a230a374-4c93-4dd2-ad70-0434152e9b27 on 8000 
11.05.20 10:22:02 (+0900) <fleet-supervisor> ========================
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> Fleet subscriber > service.online Fleet publisher#a230a374-4c93-4dd2-ad70-0434152e9b27 on 8000
11.05.20 10:22:02 (+0900) <fleet-supervisor> events.js:292
11.05.20 10:22:02 (+0900) <fleet-supervisor>       throw er; // Unhandled 'error' event
11.05.20 10:22:02 (+0900) <fleet-supervisor>       ^
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> Error: connect ECONNREFUSED 127.0.0.1:1705
11.05.20 10:22:02 (+0900) <fleet-supervisor>     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
11.05.20 10:22:02 (+0900) <fleet-supervisor> Emitted 'error' event on Socket instance at:
11.05.20 10:22:02 (+0900) <fleet-supervisor>     at emitErrorNT (internal/streams/destroy.js:96:8)
11.05.20 10:22:02 (+0900) <fleet-supervisor>     at emitErrorCloseNT (internal/streams/destroy.js:68:3)
11.05.20 10:22:02 (+0900) <fleet-supervisor>     at processTicksAndRejections (internal/process/task_queues.js:84:21) {
11.05.20 10:22:02 (+0900) <fleet-supervisor>   errno: -111,
11.05.20 10:22:02 (+0900) <fleet-supervisor>   code: 'ECONNREFUSED',
11.05.20 10:22:02 (+0900) <fleet-supervisor>   syscall: 'connect',
11.05.20 10:22:02 (+0900) <fleet-supervisor>   address: '127.0.0.1',
11.05.20 10:22:02 (+0900) <fleet-supervisor>   port: 1705
11.05.20 10:22:02 (+0900) <fleet-supervisor> }
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! code ELIFECYCLE
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! errno 1
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! fleet-supervisor@1.0.0 start: `node server.js`
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! Exit status 1
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! 
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! Failed at the fleet-supervisor@1.0.0 start script.
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11.05.20 10:22:02 (+0900) <fleet-supervisor> 
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR! A complete log of this run can be found in:
11.05.20 10:22:02 (+0900) <fleet-supervisor> npm ERR!     /root/.npm/_logs/2020-05-11T01_22_02_726Z-debug.log
11.05.20 10:22:03 (+0900) Service exited 'fleet-supervisor sha256:39a23a5f30c9c0deb64b4022248bdc2398cae578a265a52e128886172061d44a'
11.05.20 10:22:03 (+0900) <fleet-supervisor>