You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2014-03-07 21:46:46
- Seditio
- Member
- From: France
- Registered: 2012-10-24
- Posts: 9
- Website
Systemd not working.
So, I don't know since when but most systemctl commands are failing to execute... I've searched for answers and found no answer...
user@quad-srv ~ % sudo systemctl status nginx -l
Failed to get properties: Connection timed outuser@quad-srv ~ % sudo systemctl restart sshd
Failed to restart sshd.service: Activation of org.freedesktop.systemd1 timed outAny ideas..?
Offline
#2 2014-03-07 21:50:20
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 12,575
Re: Systemd not working.
If you're not on 210-3, update.
Offline
#3 2014-03-07 21:55:32
- Seditio
- Member
- From: France
- Registered: 2012-10-24
- Posts: 9
- Website
Re: Systemd not working.
warning: systemd-210-3 is up to date -- reinstalling
Offline
#4 2014-03-07 22:21:40
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Systemd not working.
Not a Sysadmin issue, moving to NC...
Offline
#5 2014-03-07 22:42:20
- WorMzy
- Administrator
- From: Scotland
- Registered: 2010-06-16
- Posts: 12,700
- Website
Re: Systemd not working.
Have you rebooted since updating systemd?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
#6 2014-03-08 13:49:07
- Seditio
- Member
- From: France
- Registered: 2012-10-24
- Posts: 9
- Website
Re: Systemd not working.
Yes I have
Offline
#8 2014-03-08 18:29:36
- Seditio
- Member
- From: France
- Registered: 2012-10-24
- Posts: 9
- Website
Re: Systemd not working.
user@quad-srv ~ % sudo lsof /run/dbus/system_bus_socket
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dbus-daem 262 dbus 3u unix 0xffff880233308700 0t0 9496 /run/dbus/system_bus_socket
I also noticed that I have more than 30 000 processes showing up as 'sshd' running by user 'nobody', log files are huge but unreadable...
Last edited by Seditio (2014-03-08 20:22:12)
Offline
#9 2014-03-08 21:44:56
- Seditio
- Member
- From: France
- Registered: 2012-10-24
- Posts: 9
- Website
Re: Systemd not working.
Fixed by multiple hard reboots...
Offline
#10 2014-03-09 03:12:22
- HiImTye
- Member
- From: Halifax, NS, Canada
- Registered: 2012-05-09
- Posts: 1,072
Re: Systemd not working.
log files are huge but unreadable...
you have to use journalctl to read them
sudo journalctlit's pretty handy though, for instance
sudo journalctl -b 0 -u sshddisplays your logs only since last boot for only 'sshd' type events
Offline
#11 2014-03-09 15:16:21
- Stebalien
- Member
- Registered: 2010-04-27
- Posts: 1,239
- Website
Re: Systemd not working.
user@quad-srv ~ % sudo lsof /run/dbus/system_bus_socket
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dbus-daem 262 dbus 3u unix 0xffff880233308700 0t0 9496 /run/dbus/system_bus_socket
DBus was obviously starting but it's systemd should have been listed there as well (systemd opens the socket and then passes it to dbus). Glad it's fixed but it's still really odd...
Offline
Pages: 1