part of /etc/conf.d/local.start swissgrid_cmd & weather_refresh & ups_refresh & { sleep 120 /bin/zcat /var/log/messages-2* | grep "XXX" >/var/log/xxx /bin/cat /var/log/messages | grep "XXY" >>/var/log/xxx } & /etc/init.d/mpd restart /etc/init.d/samba restart in short, to WA several XEN bug 293717 ... i have to restart several services during boot. Some times, MPD fails to restart: * Starting vixie-cron ... [ ok ] * Starting Xen domains from /etc/xen/auto * Creating screen session to hold domain consoles ... [ ok ] * Starting local ... * Stopping Music Player Daemon ... [ ok ] * Starting Music Player Daemon ... listen: Failed to listen on localhost (line 70): Address already in use /etc/init.d/mpd: line 20: 9263 Aborted /usr/bin/mpd /etc/mpd.conf [ !! ] * ERROR: mpd failed to start * samba -> start: smbd ... [ ok ] * samba -> start: nmbd ... [ ok ] Typically, this happens when system is under heavy load; not by the load average value, but, instant load in the previous seconds. It may happend with some other services, but, most frequently MPD. Also Samba from time to time IIRC. The bug is not reported against MPD package or ebuild, but, against the way Gentoo manages and implements the "restart" feature/function: after stop, the system does not way long enough to perform the start. Or does not way "properly" that the PID has exited: sending a kill signal is not enough: if a process catches the kill signal, it can refuse to die, or wait some time. Before the stop command returns, we need to wait for the PID to die (but only in the case of a restart; waiting for this during a normal shutdown is not desirable). "port in use" is a very explicit issue. The bug is not specific to boot time. It can also happen when i need to restart mpd during normal use, when the computer is doing very heavy work (99%CPU + 99% MEM + heavy work on way) since short time. When the load average (value in my permanent "top" window) had time to increase, I never see this happen. Only happen when i run a restart just after starting an heavy task.
Created attachment 246613 [details] /tmp/emerge--info
Can you please test this with mpd-0.16? Judging from the source this shouldn't happen.
Please reopen if this still happens with 0.16. I cannot reproduce it.
