With sys-apps/openrc-0.31.2 and above, start-stop-daemon cannot start multiple instances of a daemon anymore, if they are differentiated just by the pidfile and not by name or uid. Taking apache as an example, the first instance with SVCNAME apache2-u1 starts fine, but the second with SVCNAME apache2-u2 wont start: #> /etc/init.d/apache2-u2 start * Starting apache2-u2 … * start-stop-daemon: fopen `/run/apache2-u2.pid': No such file or directory * Sending signal 0 to PID 24323 ... [ ok ] * Sending signal 0 to PID 24314 ... [ ok ] * Sending signal 0 to PID 24306 ... [ ok ] * Sending signal 0 to PID 24303 ... [ ok ] * start-stop-daemon: /usr/sbin/apache2 is already running The apache2-u2.pid file does not exist, as apache2-u2 is not running yet. However, start-stop-daemon seems to find the four processes of apache2-u1 and beliefs –u2 is already running. Up to sys-apps/openrc-0.31.1, the config setup works like a charm. For a simpler config setup, I tested with multiple instances of net-misc/iperf(3) as well, but same result.
I just started multiple instances of my own test daemon with a multiplexed script that only changes the pid file for each instance and it worked successfully. This is with OpenRC 0.34.5. Can you verify whether you have the issue with that version? Thanks, William
Created attachment 502756 [details, diff] test.patch Hi, Can you please apply this patch and let me know if it fixes your issue? Thanks, William
Hi, can you please test with OpenRC 0.34.6 and let me know if the issue is still there? Thanks, William
sys-apps/openrc-0.34.6 fixed this issue, multiple instances do start up again. Many thanks!
No problem, closing.