Sometimes, the “volumio stop” cmdline command hangs, i.e. the call to volumio does not return. Is this a known problem?
Could you share some logs (journalctl
) when this happens?
I’ll try. I’ve now updated to 2.779 and it seems to work better now. Haven’t tried extensively though.
Ok, it happened now. This is the log from volumio:
Jun 12 09:12:14 volumio volumio[1010]: info: CoreCommandRouter::volumioGetState
Jun 12 09:12:14 volumio volumio[1010]: info:
Jun 12 09:12:14 volumio volumio[1010]: ---------------------------- Client requests Volumio stop
Jun 12 09:12:14 volumio volumio[1010]: info: CoreCommandRouter::volumioStop
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::stop
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::setConsumeUpdateService undefined
Jun 12 09:12:14 volumio volumio[1010]: UNSET VOLATILE
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::stPlaybackTimer
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::updateTrackBlock
Jun 12 09:12:14 volumio volumio[1010]: info: CorePlayQueue::getTrackBlock
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::pushState
Jun 12 09:12:14 volumio volumio[1010]: info: CorePlayQueue::getTrack 0
Jun 12 09:12:14 volumio volumio[1010]: info: CoreCommandRouter::volumioPushState
Jun 12 09:12:14 volumio volumio[1010]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jun 12 09:12:14 volumio volumio[1010]: info: CoreStateMachine::serviceStop
Jun 12 09:12:14 volumio volumio[1010]: info: CorePlayQueue::getTrack 0
Jun 12 09:12:14 volumio volumio[1010]: info: CoreCommandRouter::serviceStop
Jun 12 09:12:14 volumio volumio[1010]: info: [1591953134123] ControllerWebradio::stop
Jun 12 09:12:14 volumio volumio[1010]: verbose: ControllerMpd::sendMpdCommand stop
Jun 12 09:12:14 volumio volumio[1010]: error: MPD error: Error: read ECONNRESET
Jun 12 09:12:14 volumio volumio[1010]: error: Upnp client error: Error: This socket has been ended by the other party
Jun 12 09:12:19 volumio volumio[1010]: error: updateQueue error: null
I first do a “volumio status” to get the current state, to be able to restore it. Then I do a “volumio stop”.
In the meantime, I worked around the problem by not calling volumio stop unless current state is “play”. That way I can manually stop volumio before doing measurements.