Debian Systemd doesn't start any service  Topic is solved

Post questions regarding lower-level issues will here.

Debian Systemd doesn't start any service  Topic is solved

Postby Dikus » March 7th, 2019, 1:16 pm

I don't know how nor why but my Debian systemd stopped starting any service, particularly sshd service so I can't access to my machine. It's a headless machine without monitor and moreover I can't connect one.

I know systemd is working because when I boot with a USB with puppy, and I chroot the debian partition, I can read logs with journalclt. Everything seems working OK, but the system suddenly gets stucked receiving watchdog events ad infinitum.

I paste the tail of the output:

Code: Select all
[...]
mar 06 19:36:26 DEBIAN-LXDE systemd[1]: ifup@eth0.service: Child 560 belongs to ifup@eth0.service
mar 06 19:36:26 DEBIAN-LXDE systemd[1]: ifup@eth0.service: Main process exited, code=exited, status=0/SUCCESS
mar 06 19:36:26 DEBIAN-LXDE systemd[1]: ifup@eth0.service: Failed to destroy cgroup /system.slice/ifup@eth0.service, ignoring: Device or resource busy
mar 06 19:36:26 DEBIAN-LXDE systemd[1]: ifup@eth0.service: Changed running -> exited
mar 06 19:36:32 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:36:44 DEBIAN-LXDE ntpdate[729]: step time server 158.227.98.15 offset 9.571738 sec
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: Time has been changed
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: Received SIGCHLD from PID 722 (ntpdate).
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: Child 722 (ntpdate) died (code=exited, status=0/SUCCESS)
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: ifup@eth0.service: Child 722 belongs to ifup@eth0.service
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: ifup@eth0.service: cgroup is empty
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 19 (stored), closing.
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: Got cgroup empty notification for: /system.slice/ifup@eth0.service
mar 06 19:36:44 DEBIAN-LXDE systemd[1]: ifup@eth0.service: cgroup is empty
mar 06 19:37:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:37:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:37:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:38:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:38:02 DEBIAN-LXDE systemd[1]: systemd-journald.service: Got notification message from PID 237 (WATCHDOG=1)
mar 06 19:38:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:38:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:39:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:39:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:39:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:39:42 DEBIAN-LXDE systemd[1]: systemd-journald.service: Got notification message from PID 237 (WATCHDOG=1)
mar 06 19:40:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:40:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:40:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:41:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:41:02 DEBIAN-LXDE systemd[1]: systemd-journald.service: Got notification message from PID 237 (WATCHDOG=1)
mar 06 19:41:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:41:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:42:02 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:42:22 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
mar 06 19:42:42 DEBIAN-LXDE systemd[1]: systemd-udevd.service: Got notification message from PID 293 (WATCHDOG=1)
[...]


And it countinues that way until I rebooted.

Nevertheless the logs in /var/log/ were written few days ago. I thought the problem could be because some usb drive attached but I disconnected all of them and the result is the same. I read a lot in the web but I could't find anyting similar. Only about specific services.


I tried to write a check service as:
Code: Select all
[Unit]
Description=Avisa cuando se arranca el sistema
Requires=network.target
After=network.target

[Service]
Type=simple
RemainAfterExit=no
ExecStart=/usr/bin/mail -s "AVISOOOO" aspidnet@gmail.com

[Install]
WantedBy=default.target


But the mail is never sent.


Any ideas? How could I find out what the problem is?
Dikus
 
Posts: 1
Joined: March 7th, 2019, 1:11 pm

Re: Debian Systemd doesn't start any service

Postby cynwulf » March 15th, 2019, 3:51 pm

cynwulf
 
Posts: 2548
Joined: April 26th, 2011, 2:46 pm


Return to System Issues

Who is online

Users browsing this forum: No registered users and 0 guests

x