On Wed, Jun 1, 2016 at 3:07 PM, XYZDragon <[email protected]> wrote:
> Hello, > > When trying to restart isc-dhcp-server, I was wondering why it didn't > start. After executing the suggested `journalctl -xe` I could see that > something was wrong: > > May 27 13:32:15 my-pc isc-dhcp-server[26032]: Starting ISC DHCPv4 server: > dhcpddhcpd service already running (pid file /var/run/dhcpd.pid currenty > exists) ... failed! > > The message was helpful. I checked the file and noticed that it seemed > contain a process id. After checking with `ps -p` it seemed that that > process wasn't running anymore. In my opinion isc-dhcp-server should do > this check itself without user interaction, deleting the file if it exists, > but contains a process id of a dead process. After deleting the file > everything worked. > > Also note the word doubling 'dhcpdhcpd' and the missing 'l' in 'currenty' > in the debug message. Those could be fixed. > Then inform people whose software is printing that message – it's not systemd's output. You're currently starting dhcpd via Debian's auto-generated "compatibility" .service, which merely starts /etc/init.d/isc-dhcp-server and lets it do whatever it used to do back in the dark ages; this apparently includes printing messages with typos and exiting when it finds a stale pidfile. -- Mantas Mikulėnas <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
