Stuck due to network problem

[yiran]

Hi Everone:
I just installed the voumio on my old x86 computer. But it always stucks. Then I checked the journalctl logs. The message report some network problem. Could anyone tell me how to avoid it.
The journalctl message is like this:
Jan 11 20:38:31 volumio sudo[3751]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -h

Jan 11 20:38:31 volumio sudo[3751]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)

Jan 11 20:38:31 volumio sudo[3751]: pam_unix(sudo:session): session closed for user root

Jan 11 20:38:34 volumio volumio[3485]: |||||||||||||||||||||||| WARNING: FATAL ERROR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Jan 11 20:38:34 volumio volumio[3485]: Error: connect ETIMEDOUT 173.244.209.150:443

Jan 11 20:38:34 volumio volumio[3485]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {

Jan 11 20:38:34 volumio volumio[3485]: errno: -110,

Jan 11 20:38:34 volumio volumio[3485]: code: ‘ETIMEDOUT’,

Jan 11 20:38:34 volumio volumio[3485]: syscall: ‘connect’,

Jan 11 20:38:34 volumio volumio[3485]: address: ‘173.244.209.150’,

Jan 11 20:38:34 volumio volumio[3485]: port: 443

Jan 11 20:38:34 volumio volumio[3485]: }

Jan 11 20:38:34 volumio volumio[3485]: ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Jan 11 20:38:34 volumio sudo[3763]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl --since=2024-01-11 20:37

Jan 11 20:38:34 volumio sudo[3763]: pam_unix(sudo:session): session opened for user root by (uid=0)

Jan 11 20:38:34 volumio sudo[3763]: pam_unix(sudo:session): session closed for user root

Jan 11 20:38:34 volumio sudo[3769]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -ax

Jan 11 20:38:34 volumio sudo[3769]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)

Jan 11 20:38:35 volumio volumio-remote-updater[480]: [2024-01-11 20:38:35] [error] handle_read_frame error: websocketpp.transport:7 (End of File)

Jan 11 20:38:35 volumio volumio-remote-updater[480]: [2024-01-11 20:38:35] [disconnect] Disconnect close local:[1006,End of File] remote:[1006]

Jan 11 20:38:35 volumio systemd[1]: volumio.service: Main process exited, code=exited, status=1/FAILURE

– Subject: Unit process exited

– Defined-By: systemd

– Support: Debian -- User Support

–

– An ExecStart= process belonging to unit volumio.service has exited.

–

– The process’ exit code is ‘exited’ and its exit status is 1.

Jan 11 20:38:35 volumio systemd[1]: volumio.service: Failed with result ‘exit-code’.

– Subject: Unit failed

– Defined-By: systemd

– Support: Debian -- User Support

–

– The unit volumio.service has entered the ‘failed’ state with result ‘exit-code’.

Jan 11 20:38:35 volumio systemd[1]: Started dynamicswap service.

– Subject: A start job for unit dynamicswap.service has finished successfully

– Defined-By: systemd

– Support:

–

– A start job for unit dynamicswap.service has finished successfully.

–

– The job identifier is 3776.

Jan 11 20:38:35 volumio systemd[1]: dynamicswap.service: Succeeded.

– Subject: Unit succeeded

– Defined-By: systemd

– Support:

–

– The unit dynamicswap.service has successfully entered the ‘dead’ state.

Jan 11 20:38:35 volumio systemd[1]: volumio.service: Service RestartSec=100ms expired, scheduling restart.

Jan 11 20:38:35 volumio systemd[1]: volumio.service: Scheduled restart job, restart counter is at 7.

– Subject: Automatic restarting of a unit has been scheduled

– Defined-By: systemd

– Support:

–

– Automatic restarting of the unit volumio.service has been scheduled, as the result for

– the configured Restart= setting for the unit.

Jan 11 20:38:35 volumio systemd[1]: Started dynamicswap service.

– Subject: A start job for unit dynamicswap.service has finished successfully

– Defined-By: systemd

– Support:

–

– A start job for unit dynamicswap.service has finished successfully.

–

– The job identifier is 3844.

Jan 11 20:38:35 volumio systemd[1]: Stopped Volumio Backend Module.

– Subject: A stop job for unit volumio.service has finished

– Defined-By: systemd

– Support:

–

– A stop job for unit volumio.service has finished.

[balbuze]

I can’t say what happens but please don’t select part of log you think useful. Send a log link in which dev team will find more info.
Thanks

[Wolfman74]

How to send a log link for a bug report?

Remember to also paste the link to the log file in this thread!

[yiran]

Thanks for the guidance on how to gather the log message.
There is the link from my device. Please check it.
http://logs.volumio.org/volumio/EHGVd67.html

[dvo]

in comming signal is bad … check the cables and home network first,
otherwise you have a bad signal from out side.

[Wheaten]

@yiran

Hi please solve your network connection first as almost all outgoing connections are failing. Guess this is related to your location.

# volumio endpointstest ---------------
TESTING REMOTE ENDPOINTS
https://google.com, 5091 ms: FAILED
https://www.googleapis.com, 5082 ms: FAILED
https://securetoken.googleapis.com, 5082 ms: FAILED
https://myvolumio.firebaseio.com, 5083 ms: FAILED
https://functions.volumio.cloud, 5083 ms: FAILED
https://oauth-performer.dfs.volumio.org, 1061 ms: OK
https://browsing-performer.dfs.volumio.org, 968 ms: OK
http://cddb.volumio.org, 1395 ms: OK
https://functions.volumio.cloud, 5094 ms: FAILED
http://pushupdates.volumio.org, 6617 ms: FAILED
http://plugins.volumio.org, 5939 ms: FAILED
https://database.volumio.cloud, 1314 ms: OK
https://radio-directory.firebaseapp.com, 811 ms: OK
----------
WARNING!!! Some remote endpoints cannot be reached!
Failing endpoints: 
https://google.com, 811 ms
https://www.googleapis.com, 811 ms
https://securetoken.googleapis.com, 811 ms
https://myvolumio.firebaseio.com, 811 ms
https://functions.volumio.cloud, 811 ms
https://functions.volumio.cloud, 811 ms
http://pushupdates.volumio.org, 811 ms
http://plugins.volumio.org, 811 ms
----------

[yiran]

I know my network is very bad in this country. But I can’t understand why this leads to the main process of volumio restarting frequently.

[yiran]

It made me confused that the network connection affects the main process. Because all my music files are stored in the same home network and mounted through Samba.

Jan 12 11:25:12 volumio volumio[745]: |||||||||||||||||||||||| WARNING: FATAL ERROR |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jan 12 11:25:12 volumio volumio[745]: Error: connect ETIMEDOUT 74.86.12.172:443
Jan 12 11:25:12 volumio volumio[745]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
Jan 12 11:25:12 volumio volumio[745]:   errno: -110,
Jan 12 11:25:12 volumio volumio[745]:   code: 'ETIMEDOUT',
Jan 12 11:25:12 volumio volumio[745]:   syscall: 'connect',
Jan 12 11:25:12 volumio volumio[745]:   address: '74.86.12.172',
Jan 12 11:25:12 volumio volumio[745]:   port: 443
Jan 12 11:25:12 volumio volumio[745]: }
Jan 12 11:25:12 volumio volumio[745]: |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jan 12 11:25:12 volumio sudo[2507]:  volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl --since=2024-01-12 11:24
Jan 12 11:25:12 volumio sudo[2507]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 12 11:25:12 volumio sudo[2507]: pam_unix(sudo:session): session closed for user root
Jan 12 11:25:14 volumio volumio-remote-updater[485]: [2024-01-12 11:25:14] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Jan 12 11:25:14 volumio volumio-remote-updater[485]: [2024-01-12 11:25:14] [disconnect] Disconnect close local:[1006,End of File] remote:[1006]
Jan 12 11:25:14 volumio systemd[1]: volumio.service: Main process exited, code=exited, status=1/FAILURE
Jan 12 11:25:14 volumio systemd[1]: volumio.service: Failed with result 'exit-code'.
Jan 12 11:25:14 volumio systemd[1]: Started dynamicswap service.
Jan 12 11:25:14 volumio systemd[1]: dynamicswap.service: Succeeded.
Jan 12 11:25:14 volumio systemd[1]: volumio.service: Service RestartSec=100ms expired, scheduling restart.
Jan 12 11:25:14 volumio systemd[1]: volumio.service: Scheduled restart job, restart counter is at 1.
Jan 12 11:25:14 volumio systemd[1]: Stopped Volumio Backend Module.
Jan 12 11:25:14 volumio systemd[1]: Started Volumio Backend Module.
Jan 12 11:25:14 volumio systemd[1]: Started dynamicswap service.
Jan 12 11:25:14 volumio systemd[1]: dynamicswap.service: Succeeded.

[Wheaten]

It’s they way how Volumio works. It relies on cloud services, google,…

[yiran]

Oh, that is a frustrating message. I don’t think I can solve the network dilemma.
Maybe, I should give it up.

[Wheaten]

You can try using a VPN?

I am ready to give up VOLUMIO and cancel the membership, because I tried many ways and couldn't log in

Unfortunately, My Volumio is not available in China unless you use a VPN on both the controlling device and the volumio device itself. This does not depend on us, but My Volumio uses authentication and Realtime Database from Google, and they are not available in China for known reasons. We tried lot of things to make it work, but unfortunately to no avail.

[yiran]

At now, my device is just stuck occasionally. It is still a nice player for me. I’m just confused about the reason. As my music files are stored in a local network device, it should just miss some information for display and didn’t lead to the breakdown of volumio process.