systemd-logind: Failed to remove runtime directory

General support questions
Hellkeeper
Posts: 52
Joined: 2005/07/10 22:16:30
Contact:

systemd-logind: Failed to remove runtime directory

Post by Hellkeeper » 2016/10/27 15:01:31

Hello,
today I noticed thousands of those Errors within m< /var/log/messages:

Code: Select all

Oct 27 16:54:31 servername systemd-logind: Failed to remove runtime directory /run/user/0: Device or resource busy
Oct 27 16:55:31 servername systemd-logind: Failed to remove runtime directory /run/user/0: Device or resource busy
Oct 27 16:56:31 servername systemd-logind: Failed to remove runtime directory /run/user/0: Device or resource busy
Oct 27 16:57:31 servername systemd-logind: Failed to remove runtime directory /run/user/0: Device or resource busy
Oct 27 16:58:31 servername systemd-logind: Failed to remove runtime directory /run/user/0: Device or resource busy
Unfortunately I was not able to find the Source of those Errors (googled the last 2 Hours ...)
Hope someone here can help me finding out what's wrong here?!

Code: Select all

uname -a: Linux servername 3.10.0-042stab116.1 #1 SMP Thu Oct 20 18:18:21 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/redhat-release: CentOS Linux release 7.2.1511 (Core)
lsof +D /run/user: *nothing*
df -h: tmpfs               63G  104K   63G   1% /run
       tmpfs              1.3G     0  1.3G   0% /run/user/0
Thx
Andreas Schnederle-Wagner

User avatar
TrevorH
Forum Moderator
Posts: 32031
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: systemd-logind: Failed to remove runtime directory

Post by TrevorH » 2016/10/27 15:05:23

Run fuser -m /run/user/0 and see if that tells you anything.

Unfortunately you're not running CentOS, you're running an openvz container that's pretending to be CentOS and you'll need to ask your hoster for assistance.
CentOS 8 died a premature death at the end of 2021 - migrate to Rocky/Alma/OEL/Springdale ASAP.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are dead, do not use them.
Use the FAQ Luke

Hellkeeper
Posts: 52
Joined: 2005/07/10 22:16:30
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by Hellkeeper » 2016/10/27 15:19:14

Hi Trevor,
thank you for your fast reply! ;-)

Code: Select all

[root@servername ~]# fuser -a /run/user/0
/run/user/0:
[root@servername ~]# fuser -m /run/user/0
Actually we *are* the Hoster ... and I just try to find out why this is happening in one of our Containers! ;-)
Not sure it the Problem is based on Centos Side or Virtuozzo - it it's Virtuozzo - I will open a Case with them.

thx
Andreas

rodrigo-gomes
Posts: 24
Joined: 2016/11/10 04:06:05
Location: Brazil
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by rodrigo-gomes » 2016/11/10 04:21:08

I'm having the same problem, but for me are for multiple users.

Code: Select all

Nov  9 12:50:02 server systemd: Removed slice user-1098.slice.
Nov  9 12:50:02 server systemd: Stopping user-1098.slice.
Nov  9 12:50:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov  9 12:50:02 server systemd: Removed slice user-1096.slice.
Nov  9 12:50:02 server systemd: Stopping user-1096.slice.
Nov  9 12:50:02 server systemd: Removed slice user-1092.slice.
Nov  9 12:50:02 server systemd: Stopping user-1092.slice.
Nov  9 12:50:03 server systemd: Removed slice user-1058.slice.
Nov  9 12:50:03 server systemd: Stopping user-1058.slice.
Nov  9 12:50:13 server systemd: Removed slice user-977.slice.
Nov  9 12:50:13 server systemd: Stopping user-977.slice.
Nov  9 12:51:01 server systemd: Removed slice user-1096.slice.
Nov  9 12:51:01 server systemd: Stopping user-1096.slice.
Nov  9 12:51:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov  9 12:51:01 server systemd: Removed slice user-1058.slice.
Nov  9 12:51:01 server systemd: Stopping user-1058.slice.
Nov  9 12:51:01 server systemd: Removed slice user-1092.slice.
Nov  9 12:51:01 server systemd: Stopping user-1092.slice.

Code: Select all

[~]# uname -a
Linux server 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[~]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)

[~]# lsof +D /run/user
*nothing*

[~]# df -h
/dev/mapper/centos_server--server-root   50G   31G   20G  62% /
devtmpfs                                9,8G     0  9,8G   0% /dev
tmpfs                                   9,8G  144K  9,8G   1% /dev/shm
tmpfs                                   9,8G   49M  9,7G   1% /run
tmpfs                                   9,8G     0  9,8G   0% /sys/fs/cgroup
/dev/sdb                                493G   73M  467G   1% /mnt/Backup
/dev/mapper/centos_server--server-home  435G  118G  318G  27% /home
/dev/sda1                               497M  351M  146M  71% /boot
tmpfs                                   2,0G   28K  2,0G   1% /run/user/0
tmpfs                                   2,0G     0  2,0G   0% /run/user/977

[~]# rpm -qa kernel\* | sort
kernel-3.10.0-327.28.2.el7.x86_64
kernel-3.10.0-327.28.3.el7.x86_64
kernel-3.10.0-327.36.1.el7.x86_64
kernel-3.10.0-327.36.2.el7.x86_64
kernel-3.10.0-327.36.3.el7.x86_64
kernel-devel-3.10.0-327.28.2.el7.x86_64
kernel-devel-3.10.0-327.28.3.el7.x86_64
kernel-devel-3.10.0-327.36.1.el7.x86_64
kernel-devel-3.10.0-327.36.2.el7.x86_64
kernel-devel-3.10.0-327.36.3.el7.x86_64
kernel-headers-3.10.0-327.36.3.el7.x86_64
kernel-tools-3.10.0-327.36.3.el7.x86_64
kernel-tools-libs-3.10.0-327.36.3.el7.x86_64

[~]# dmidecode -s system-product-name
VirtualBox

systemd-logind: Failed to remove runtime directory /run/user/*****: Device or resource busy

I see this error many times in /var/log/messages.
Does anyone know tell me what this error means? And if I should worry about it?

rodrigo-gomes
Posts: 24
Joined: 2016/11/10 04:06:05
Location: Brazil
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by rodrigo-gomes » 2016/11/10 19:36:59

This is the log of the last hour, in 1 hour happened 68 times. :?

Code: Select all

Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1002: Device or resource busy
Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1009: Device or resource busy
Nov 10 16:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 16:31:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:33:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:35:03 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:36:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:38:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:39:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:40:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:40:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 16:41:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:42:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:43:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:45:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:45:03 server systemd-logind: Failed to remove runtime directory /run/user/1002: Device or resource busy
Nov 10 16:45:03 server systemd-logind: Failed to remove runtime directory /run/user/1009: Device or resource busy
Nov 10 16:45:03 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:45:03 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 16:46:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:50:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:51:02 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 16:53:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:54:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 16:55:03 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 16:56:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 16:56:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:00:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:00:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:00:02 server systemd-logind: Failed to remove runtime directory /run/user/1002: Device or resource busy
Nov 10 17:00:03 server systemd-logind: Failed to remove runtime directory /run/user/1009: Device or resource busy
Nov 10 17:00:03 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:00:04 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 17:01:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:03:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:03:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:05:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:06:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:07:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:07:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:10:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:11:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:12:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:13:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:14:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:14:01 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:15:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:15:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:15:02 server systemd-logind: Failed to remove runtime directory /run/user/1002: Device or resource busy
Nov 10 17:15:02 server systemd-logind: Failed to remove runtime directory /run/user/1009: Device or resource busy
Nov 10 17:15:03 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:15:03 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 17:19:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:20:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:24:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:26:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:28:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:29:02 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:30:02 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy
Nov 10 17:30:02 server systemd-logind: Failed to remove runtime directory /run/user/1098: Device or resource busy
Nov 10 17:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1002: Device or resource busy
Nov 10 17:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1058: Device or resource busy
Nov 10 17:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1009: Device or resource busy
Nov 10 17:30:03 server systemd-logind: Failed to remove runtime directory /run/user/1092: Device or resource busy
Nov 10 17:31:01 server systemd-logind: Failed to remove runtime directory /run/user/1096: Device or resource busy

rodrigo-gomes
Posts: 24
Joined: 2016/11/10 04:06:05
Location: Brazil
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by rodrigo-gomes » 2016/11/11 19:14:17

Does anyone have any idea what this might be?
Is anyone reading this topic? :?

User avatar
TrevorH
Forum Moderator
Posts: 32031
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: systemd-logind: Failed to remove runtime directory

Post by TrevorH » 2016/11/11 19:15:22

It means that a process is still using that directory. Do your users spawn background processes and leave them running?
CentOS 8 died a premature death at the end of 2021 - migrate to Rocky/Alma/OEL/Springdale ASAP.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are dead, do not use them.
Use the FAQ Luke

rodrigo-gomes
Posts: 24
Joined: 2016/11/10 04:06:05
Location: Brazil
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by rodrigo-gomes » 2016/11/11 19:26:53

TrevorH wrote:It means that a process is still using that directory. Do your users spawn background processes and leave them running?
I believe that yes, I use cpanel and host many websites.
My users ran php tasks with cron. We have php, mysql, apache, running on that server.

User avatar
TrevorH
Forum Moderator
Posts: 32031
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: systemd-logind: Failed to remove runtime directory

Post by TrevorH » 2016/11/11 19:39:10

So, it's possible that they are still using the mount. Try running e.g fuser -m /run/user/987 (or whatever the mountpoint is in one of the more recent messages. You'll get back a list of PIDs and you can use ps to see what those are.
CentOS 8 died a premature death at the end of 2021 - migrate to Rocky/Alma/OEL/Springdale ASAP.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are dead, do not use them.
Use the FAQ Luke

rodrigo-gomes
Posts: 24
Joined: 2016/11/10 04:06:05
Location: Brazil
Contact:

Re: systemd-logind: Failed to remove runtime directory

Post by rodrigo-gomes » 2016/11/11 21:27:24

TrevorH wrote:So, it's possible that they are still using the mount. Try running e.g fuser -m /run/user/987 (or whatever the mountpoint is in one of the more recent messages. You'll get back a list of PIDs and you can use ps to see what those are.
Hello TrevorH,

After following this tutorial: http://www.linux-faqs.info/general/how- ... ystem-busy

I got the following information:

Code: Select all

[~]# ps -lf  -p $(fuser -c /run/user/1058 2>/dev/null)
F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY        TIME CMD
4 S root         1     0  1  80   0 - 52035 ep_pol Nov09 ?         38:17 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
4 S root       511     1  0  80   0 - 15464 ep_pol Nov09 ?          0:30 /usr/lib/systemd/systemd-journald
4 S root       530     1  0  80   0 - 31669 poll_s Nov09 ?          0:00 /usr/sbin/lvmetad -f
4 S root       539     1  0  80   0 - 10969 ep_pol Nov09 ?          0:00 /usr/lib/systemd/systemd-udevd
4 S root       684     1  0  99  19 -  4189 poll_s Nov09 ?          0:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main
4 S libstor+   696     1  0  80   0 -  1655 poll_s Nov09 ?          0:00 /usr/bin/lsmd -d
4 S root       698     1  0  80   0 - 36967 skb_re Nov09 ?          0:00 /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/local/cpanel/bin/pureauth
4 S root       706     1  0  80   0 - 52216 poll_s Nov09 ?          0:00 /usr/sbin/abrtd -d -s
5 S nscd       707     1  0  80   0 - 434361 ep_pol Nov09 ?         0:22 /usr/sbin/nscd
4 S dbus       731     1  0  80   0 -  6912 ep_pol Nov09 ?          2:15 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
1 S root       745     1  0  80   0 - 50842 ep_pol Nov09 ?          0:00 /usr/sbin/gssproxy -D
4 S avahi      853     1  0  80   0 -  6603 poll_s Nov09 ?          0:03 avahi-daemon: running [server-server.local]
4 S root       873     1  0  80   0 - 83404 poll_s Nov09 ?          0:13 /usr/sbin/rsyslogd -n
4 S root       875     1  0  80   0 -  6206 ep_pol Nov09 ?          0:41 /usr/lib/systemd/systemd-logind
4 S root       905     1  0  80   0 - 131247 poll_s Nov09 ?         0:46 /usr/sbin/NetworkManager --no-daemon
1 S avahi      976   853  0  80   0 -  6572 unix_s Nov09 ?          0:00 avahi-daemon: chroot helper
1 S root      1504     1  0  80   0 - 84613 sigtim Nov09 ?          0:25 /usr/sbin/VBoxService --pidfile /var/lock/subsys/vboxadd-service
4 S root      1780     1  0  80   0 -  7240 ep_pol Nov09 ?          0:03 /usr/sbin/dovecot -F -c /etc/dovecot/dovecot.conf
4 S root      1794     1  0  80   0 - 138634 poll_s Nov09 ?         0:00 /usr/sbin/libvirtd
4 S root      1803     1  0  80   0 -  6066 hrtime Nov09 ?          0:00 /usr/sbin/atd -f
4 S root      1806     1  0  80   0 - 31106 hrtime Nov09 ?          0:02 /usr/sbin/crond -n
4 S dovenull  1814  1780  0  80   0 - 11427 ep_pol Nov09 ?          0:02 dovecot/pop3-login
4 S dovenull  1815  1780  0  80   0 - 11712 ep_pol Nov09 ?          0:20 dovecot/imap-login
4 S dovecot   1816  1780  0  80   0 -  2389 ep_pol Nov09 ?          0:00 dovecot/anvil
4 S root      1817  1780  0  80   0 -  2422 ep_pol Nov09 ?          0:01 dovecot/log
4 S dovenull  1822  1780  0  80   0 - 11448 ep_pol Nov09 ?          0:01 dovecot/pop3-login
4 S dovenull  1824  1780  0  80   0 - 11620 ep_pol Nov09 ?          0:13 dovecot/imap-login
4 S root      1826  1780  0  80   0 -  3424 ep_pol Nov09 ?          0:03 dovecot/config
4 S root      2230     1  0  80   0 - 47354 poll_s Nov09 ?          0:07 cPhulkd - processor
4 S casegu2+  8364  1780  0  80   0 - 10403 ep_pol 13:51 ?          0:00 dovecot/imap
4 S casegu2+  8549  1780  0  80   0 - 10474 ep_pol 13:51 ?          0:00 dovecot/imap
4 S casegu2+  9878  1780  0  80   0 - 10375 ep_pol 13:58 ?          0:00 dovecot/imap
4 S casegu2+ 14573  1780  0  80   0 - 10488 ep_pol 18:33 ?          0:00 dovecot/imap
4 S casegu2+ 14576  1780  0  80   0 - 10375 ep_pol 18:33 ?          0:00 dovecot/imap
4 S casegu2+ 15582  1780  0  80   0 - 10380 ep_pol 18:36 ?          0:00 dovecot/imap
4 S casegu2+ 15982  1780  0  80   0 - 10384 ep_pol 18:38 ?          0:00 dovecot/imap
4 S root     17117     1  0  80   0 - 23828 wait   18:42 ?          0:00 login -- root
0 S root     17547 17346  0  80   0 - 322332 poll_s 18:43 ?         0:04 /usr/libexec/gnome-settings-daemon
0 S root     17619     1  0  80   0 - 99297 poll_s 18:43 ?          0:00 /usr/libexec/mission-control-5
0 S root     17771 17346  0  80   0 - 62629 poll_s 18:43 ?          0:00 /usr/bin/python /usr/libexec/gnome-tweak-tool-lid-inhibitor
4 S casegu2+ 18141  1780  0  80   0 - 10688 ep_pol 18:43 ?          0:00 dovecot/imap
5 S varnish  18656     1  0  80   0 - 33881 poll_s Nov09 ?          0:10 /usr/sbin/varnishd -P /var/run/varnish.pid -f /etc/varnish/default.vcl -a 209.133.207.181:80 -T 127.0.0.1
5 S root     23397     1  0  80   0 - 35257 poll_s 01:36 ?          0:00 cpgreylistd - processor
4 S root     27580     1  0  80   0 - 47852 ep_pol Nov09 ?          0:00 /usr/sbin/cupsd -f
4 S dovecot  28169  1780  0  80   0 -  7525 ep_pol 19:13 ?          0:00 dovecot/auth
4 S root     28171  1780  0  80   0 -  2388 ep_pol 19:13 ?          0:00 dovecot/ssl-params
4 S dovecot  28175  1780  0  80   0 -  4149 ep_pol 19:13 ?          0:00 dovecot/dict
5 S root     28334  1806  0  80   0 - 44671 pipe_w 19:14 ?          0:00 /usr/sbin/CROND -n
5 S root     30714     1  0  80   0 - 55898 hrtime 00:00 ?          0:34 lfd - sleeping
5 S csf      30745 30714  0  80   0 - 45651 inet_c 00:00 ?          0:00 lfd HTML messenger
5 S csf      30746 30714  0  80   0 - 45651 inet_c 00:00 ?          0:00 lfd TEXT messenger
4 S casegu2+ 31211  1780  0  80   0 - 10667 ep_pol 15:19 ?          0:00 dovecot/imap

[~]# ps -lf  -p $(fuser -c /run/user/1096 2>/dev/null)
F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY        TIME CMD
4 S root         1     0  1  80   0 - 52046 ep_pol Nov09 ?         38:20 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
4 S root       511     1  0  80   0 - 15464 ep_pol Nov09 ?          0:31 /usr/lib/systemd/systemd-journald
4 S root       530     1  0  80   0 - 31669 poll_s Nov09 ?          0:00 /usr/sbin/lvmetad -f
4 S root       539     1  0  80   0 - 10969 ep_pol Nov09 ?          0:00 /usr/lib/systemd/systemd-udevd
4 S root       684     1  0  99  19 -  4189 poll_s Nov09 ?          0:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main
4 S libstor+   696     1  0  80   0 -  1655 poll_s Nov09 ?          0:00 /usr/bin/lsmd -d
4 S root       698     1  0  80   0 - 36967 skb_re Nov09 ?          0:00 /usr/sbin/pure-authd -s /var/run/ftpd.sock -r /usr/local/cpanel/bin/pureauth
4 S root       706     1  0  80   0 - 52216 poll_s Nov09 ?          0:00 /usr/sbin/abrtd -d -s
5 S nscd       707     1  0  80   0 - 434361 ep_pol Nov09 ?         0:22 /usr/sbin/nscd
4 S dbus       731     1  0  80   0 -  6912 ep_pol Nov09 ?          2:16 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
1 S root       745     1  0  80   0 - 50842 ep_pol Nov09 ?          0:00 /usr/sbin/gssproxy -D
4 S avahi      853     1  0  80   0 -  6603 poll_s Nov09 ?          0:03 avahi-daemon: running [server-server.local]
4 S root       873     1  0  80   0 - 83404 poll_s Nov09 ?          0:13 /usr/sbin/rsyslogd -n
4 S root       875     1  0  80   0 -  6206 ep_pol Nov09 ?          0:42 /usr/lib/systemd/systemd-logind
4 S root       905     1  0  80   0 - 131247 poll_s Nov09 ?         0:46 /usr/sbin/NetworkManager --no-daemon
1 S avahi      976   853  0  80   0 -  6572 unix_s Nov09 ?          0:00 avahi-daemon: chroot helper
1 S root      1504     1  0  80   0 - 84613 sigtim Nov09 ?          0:25 /usr/sbin/VBoxService --pidfile /var/lock/subsys/vboxadd-service
4 S root      1780     1  0  80   0 -  7240 ep_pol Nov09 ?          0:03 /usr/sbin/dovecot -F -c /etc/dovecot/dovecot.conf
4 S root      1794     1  0  80   0 - 138634 poll_s Nov09 ?         0:00 /usr/sbin/libvirtd
4 S root      1803     1  0  80   0 -  6066 hrtime Nov09 ?          0:00 /usr/sbin/atd -f
4 S root      1806     1  0  80   0 - 31106 hrtime Nov09 ?          0:02 /usr/sbin/crond -n
4 S dovenull  1814  1780  0  80   0 - 11427 ep_pol Nov09 ?          0:02 dovecot/pop3-login
4 S dovenull  1815  1780  0  80   0 - 11712 ep_pol Nov09 ?          0:20 dovecot/imap-login
4 S dovecot   1816  1780  0  80   0 -  2389 ep_pol Nov09 ?          0:00 dovecot/anvil
4 S root      1817  1780  0  80   0 -  2422 ep_pol Nov09 ?          0:01 dovecot/log
4 S dovenull  1822  1780  0  80   0 - 11448 ep_pol Nov09 ?          0:01 dovecot/pop3-login
4 S dovenull  1824  1780  0  80   0 - 11620 ep_pol Nov09 ?          0:13 dovecot/imap-login
4 S root      1826  1780  0  80   0 -  3424 ep_pol Nov09 ?          0:03 dovecot/config
4 S root      2230     1  0  80   0 - 47354 poll_s Nov09 ?          0:07 cPhulkd - processor
4 S casegu2+  8364  1780  0  80   0 - 10403 ep_pol 13:51 ?          0:00 dovecot/imap
4 S casegu2+  8549  1780  0  80   0 - 10474 ep_pol 13:51 ?          0:00 dovecot/imap
4 S casegu2+  9878  1780  0  80   0 - 10375 ep_pol 13:58 ?          0:00 dovecot/imap
4 S root     17117     1  0  80   0 - 23828 wait   18:42 ?          0:00 login -- root
0 S root     17547 17346  0  80   0 - 322398 poll_s 18:43 ?         0:05 /usr/libexec/gnome-settings-daemon
0 S root     17619     1  0  80   0 - 99363 poll_s 18:43 ?          0:00 /usr/libexec/mission-control-5
0 S root     17771 17346  0  80   0 - 62629 poll_s 18:43 ?          0:00 /usr/bin/python /usr/libexec/gnome-tweak-tool-lid-inhibitor
5 S varnish  18656     1  0  80   0 - 33881 poll_s Nov09 ?          0:10 /usr/sbin/varnishd -P /var/run/varnish.pid -f /etc/varnish/default.vcl -a 123.456.789.10:80 -T 127.0.0.1
5 S root     23397     1  0  80   0 - 35257 poll_s 01:36 ?          0:00 cpgreylistd - processor
4 S root     27580     1  0  80   0 - 47852 ep_pol Nov09 ?          0:00 /usr/sbin/cupsd -f
5 S root     30714     1  0  80   0 - 55898 hrtime 00:00 ?          0:34 lfd - sleeping
5 S csf      30745 30714  0  80   0 - 45651 inet_c 00:00 ?          0:00 lfd HTML messenger
5 S csf      30746 30714  0  80   0 - 45651 inet_c 00:00 ?          0:00 lfd TEXT messenger
4 S casegu2+ 31211  1780  0  80   0 - 10667 ep_pol 15:19 ?          0:00 dovecot/imap
Honestly, I do not quite understand what these logs are trying to say. :|
It looks like it tries to shut down the user automatically.

But I have some process that I really want to let go ran the background. Like the Varnish.
Last edited by rodrigo-gomes on 2019/03/09 03:44:39, edited 1 time in total.

Post Reply