[systemd-devel] How do I remove dead process managed by Systemd?
Hi, fellows: How do I remove a dead process (D-state process) wrapped as a Systemd service unit? The process's parent is systemd (pid=1) and I still did not find a way to remove such process without rebooting. I have tried the following: $ systemctl restart # timeout $ systemctl daemon-reexec $ kill -9 # won't work of course Or anyone knows of hacks that do the trick? Thanks in advance! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Missing previous boot system journal
I'm serious. It was run as root; but just as requested. $ journalctl -n5 Journal file /var/log/journal/65f854e19e1d43049c5e058f1f93648f/user-4994.journal is truncated, ignoring file. -- Logs begin at Fri 2016-02-05 00:16:50 CST, end at Wed 2016-11-23 19:38:16 CST. -- Nov 23 19:38:01 server CROND[18450]: (b02902009) CMD (~/bin/iframe.sh) Nov 23 19:38:01 server CROND[18444]: pam_unix(crond:session): session closed for user b02902009 Nov 23 19:38:01 server CROND[18443]: pam_unix(crond:session): session closed for user b01902090 Nov 23 19:38:02 server CROND[18442]: pam_unix(crond:session): session closed for user b04902111 Nov 23 19:38:16 server nscd[930]: 930 checking for monitored file `/var/db/passwd.db': 沒有此一檔案或目錄 $ id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),19(log) On Wed, Nov 23, 2016 at 6:52 PM, Lennart Poettering wrote: > On Wed, 23.11.16 18:50, Yunchih Chen (yunchih@gmail.com) wrote: > > > I am 100% sure it is run as root. > > Is there other debug info I can provide? Thanks for your help. > > Just run your journalctl commands as root again? The "id" command lets > you know your user identity... > > > Lennart > > -- > Lennart Poettering, Red Hat > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Missing previous boot system journal
I've explicitly enabled persistent storage in journald.conf. However, it seems that the system journal of previous boot is still missing; only some user journal persisted. Am I missing anything? Thanks in advance. I'm running on Archlinux with Linux 4.8.4 and systemd 231-4. Here's some output: $ journalctl -b -1 -k -- No entries -- $ journalctl -b -1 -- Logs begin at Fri 2016-02-05 00:16:50 CST, end at Tue 2016-11-22 23:35:47 CST. -- Nov 09 08:27:14 server systemd[19336]: Reached target Timers. Nov 09 08:27:14 server systemd[19336]: Listening on Sound System. Nov 09 08:27:14 server systemd[19336]: Starting D-Bus User Message Bus Socket. Nov 09 08:27:14 server systemd[19336]: Reached target Paths. Nov 09 08:27:14 server systemd[19336]: Listening on D-Bus User Message Bus Socket. Nov 09 08:27:14 server systemd[19336]: Reached target Sockets. Nov 09 08:27:14 server systemd[19336]: Reached target Basic System. Nov 09 08:27:14 server systemd[19336]: Starting Update XDG user dir configuration... Nov 09 08:27:14 server systemd[19336]: Started Update XDG user dir configuration. Nov 09 08:27:14 server systemd[19336]: Reached target Default. Nov 09 08:27:14 server systemd[19336]: Startup finished in 124ms. Nov 09 08:53:57 server systemd[19336]: Stopped target Default. Nov 09 08:53:57 server systemd[19336]: Stopped target Basic System. Nov 09 08:53:57 server systemd[19336]: Stopped target Paths. Nov 09 08:53:57 server systemd[19336]: Stopped target Timers. Nov 09 08:53:57 server systemd[19336]: Stopped target Sockets. Nov 09 08:53:57 server systemd[19336]: Closed D-Bus User Message Bus Socket. Nov 09 08:53:57 server systemd[19336]: Closed Sound System. Nov 09 08:53:57 server systemd[19336]: Reached target Shutdown. Nov 09 08:53:58 server systemd[19336]: Starting Exit the Session... Nov 09 08:53:58 server systemd[19336]: Received SIGRTMIN+24 from PID 6632 (kill). Nov 09 08:58:54 server systemd[8229]: Reached target Timers. Nov 09 08:58:54 server systemd[8229]: Reached target Paths. Nov 09 08:58:54 server systemd[8229]: Starting D-Bus User Message Bus Socket. Nov 09 08:58:54 server systemd[8229]: Listening on Sound System. // There's only one system.journal file under /var/log/journal $ ls /var/log/journal/65f854e19e1d43049c5e058f1f93648f | tail -rw-r-+ 1 root systemd-journal 8388608 Nov 22 22:21 user-30130.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 22:46 user-66461.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 22:46 user-66401.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 22:56 user-66358.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 23:27 user-1000.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 23:32 user-66704.journal -rw-r-+ 1 root systemd-journal 25165824 Nov 22 23:37 user-1.journal -rw-r-+ 1 root systemd-journal 8388608 Nov 22 23:37 user-65979.journal -rw-r-+ 1 root systemd-journal 16777216 Nov 22 23:37 system.journal $ journalctl --list-boots -6 8d87ad64bd304262a3fb7dd168e5b281 Fri 2016-02-05 00:16:50 CST—Fri 2016-02-05 01:00:15 CST -5 f23f466ad9b14b99ae32df044cb99f5f Sun 2016-04-24 15:29:21 CST—Sat 2016-04-30 10:01:31 CST -4 d834ef74d7504da0a10389581de5521a Sun 2016-06-19 14:02:16 CST—Sat 2016-07-09 10:01:31 CST -3 940aeff685804fe193f4e4e767234c24 Mon 2016-07-25 08:06:07 CST—Sat 2016-08-06 07:00:25 CST -2 fa52bc6f582b4df083e57863e000ffad Thu 2016-09-29 18:04:51 CST—Tue 2016-10-25 23:59:19 CST -1 2815d7f541644e9a8a9d778f1c69838e Wed 2016-11-09 08:27:18 CST—Mon 2016-11-21 17:57:41 CST 0 0ab0d3a3955241e9b16b22674046cea7 Tue 2016-11-22 21:15:26 CST—Tue 2016-11-22 23:40:28 CST Here's the content of /etc/systemd/journald.conf: [Journal] Storage=persistent #Compress=yes #Seal=yes #SplitMode=uid #SyncIntervalSec=5m #RateLimitIntervalSec=30s #RateLimitBurst=1000 #SystemMaxUse= #SystemKeepFree= #SystemMaxFileSize= #SystemMaxFiles=100 #RuntimeMaxUse= #RuntimeKeepFree= #RuntimeMaxFileSize= #RuntimeMaxFiles=100 #MaxRetentionSec= #MaxFileSec=1month #ForwardToSyslog=no #ForwardToKMsg=no #ForwardToConsole=no #ForwardToWall=yes #TTYPath=/dev/console #MaxLevelStore=debug #MaxLevelSyslog=debug #MaxLevelKMsg=notice #MaxLevelConsole=info #MaxLevelWall=emerg -- I send this mail for the second time since it seems to fail previously. Please ignore this if you find it a duplicate. ( : ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
