[FS#516] procd doesn't wait for a process to quit during restart

LEDE Bugs lede-bugs at lists.infradead.org
Tue Feb 14 16:46:19 PST 2017


A new Flyspray task has been opened.  Details are below. 

User who did this - Stijn Tintel (stintel) 

Attached to Project - LEDE Project
Summary - procd doesn't wait for a process to quit during restart
Task Type - Bug Report
Category - Base system
Status - New
Assigned To - 
Operating System - All
Severity - Medium
Priority - Medium
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - Some software takes some time to do a clean shutdown, but procd doesn't wait for a process to quit during restart. This can cause several problems, one of them being the new process unable to bind to the socket because the old process still has it open.


Wed Feb 15 01:41:52 2017 daemon.info domoticz: Domoticz is exiting...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: Closing application!...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: Stopping worker...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: RxQueue: queue worker stopped...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: WebServer(HTTP) stopped
Wed Feb 15 01:41:52 2017 daemon.info domoticz: Domoticz is starting up....
Wed Feb 15 01:41:52 2017 daemon.info domoticz: Domoticz running...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: EventSystem: reset all events...
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: WebServer(HTTP) started on address: :: with port 8080
Wed Feb 15 01:41:52 2017 daemon.notice domoticz: Proxymanager started.
Wed Feb 15 01:41:52 2017 daemon.err domoticz: Error: Exception starting shared server: bind: Address in use


It seems procd simply does not support this basic feature, so this should be implemented and I'd say this should even be default behavior.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=516



More information about the lede-bugs mailing list