On 10/12/2018 14.58, Per Jessen wrote:
Carlos E. R. wrote:
On 09/12/2018 19.43, Andrei Borzenkov wrote:
09.12.2018 13:57, Carlos E.R. пишет:
I wrongly expected systemd to log the error messages :-(
systemd does not log anything beyond its own messages.
Well, that's a failure.
Uh, not really. As Andrei says, systemd does not log anything beyond its own messages. Logging is for journald or a syslog daemon. As to why those nscd syntax errors were not in the log/journal, that is interesting.
Well, yes, but I consider the journal part of systemd. The starting of a daemon should log the error messages of that daemon, and when I ask "systemctl status service" I should get them. This is syslog: <3.6> 2018-12-08T22:17:51.044920+01:00 Isengard systemd 1 - - Starting Name Service Cache Daemon... <3.6> 2018-12-08T22:17:51.049333+01:00 Isengard nscd 3973 - - /usr/sbin/nscd: Parse error: <===== <3.6> 2018-12-08T22:17:51.050023+01:00 Isengard nscd 3973 - - /usr/sbin/nscd: Unknown option: CER por <3.6> 2018-12-08T22:17:51.050345+01:00 Isengard nscd 3973 - - /usr/sbin/nscd: failure while reading configuration file; this is fatal <3.5> 2018-12-08T22:17:51.050614+01:00 Isengard systemd 1 - - nscd.service: Control process exited, code=exited status=1 <3.3> 2018-12-08T22:17:51.051098+01:00 Isengard systemd 1 - - Failed to start Name Service Cache Daemon. <3.5> 2018-12-08T22:17:51.051593+01:00 Isengard systemd 1 - - nscd.service: Unit entered failed state. <3.4> 2018-12-08T22:17:51.052032+01:00 Isengard systemd 1 - - nscd.service: Failed with result 'exit-code'. <3.6> 2018-12-08T22:17:51.279871+01:00 Isengard systemd 1 - - nscd.service: Service RestartSec=100ms expired, scheduling restart. <3.6> 2018-12-08T22:17:51.292145+01:00 Isengard systemd 1 - - Stopped Name Service Cache Daemon. <3.4> 2018-12-08T22:17:51.292648+01:00 Isengard systemd 1 - - nscd.service: Start request repeated too quickly. <3.3> 2018-12-08T22:17:51.293239+01:00 Isengard systemd 1 - - Failed to start Name Service Cache Daemon. <3.5> 2018-12-08T22:17:51.293668+01:00 Isengard systemd 1 - - nscd.service: Unit entered failed state. <3.4> 2018-12-08T22:17:51.294068+01:00 Isengard systemd 1 - - nscd.service: Failed with result 'exit-code'. I see the problem clearly in there, just by searching in "less" for "nscd". It is obvious! It is logged by nscd itself, not by systemd. The journal (for the same instant) said (it is on the first post, doing what the error told me to do «See "systemctl status nscd.service" and "journalctl -xe" for details.»): Dec 08 22:17:51 Isengard systemd[1]: Failed to start Name Service Cache Daemon. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Service RestartSec=100ms expired, scheduling restart. Dec 08 22:17:51 Isengard systemd[1]: Stopped Name Service Cache Daemon. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Start request repeated too quickly. Dec 08 22:17:51 Isengard systemd[1]: Failed to start Name Service Cache Daemon. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. The problem is not there... And "journalctl -xe" said:
Dec 08 22:17:51 Isengard systemd[1]: Failed to start Name Service Cache Daemon. -- Subject: Unit nscd.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has failed. -- -- The result is failed. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Service RestartSec=100ms expired, scheduling restart. Dec 08 22:17:51 Isengard systemd[1]: Stopped Name Service Cache Daemon. -- Subject: Unit nscd.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has finished shutting down. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Start request repeated too quickly. Dec 08 22:17:51 Isengard systemd[1]: Failed to start Name Service Cache Daemon. -- Subject: Unit nscd.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has failed. -- -- The result is failed. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:17:51 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Dec 08 22:18:00 Isengard login[1905]: pam_unix(login:session): session closed for user root Dec 08 22:18:00 Isengard systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart. Dec 08 22:18:00 Isengard systemd[1]: Stopped Getty on tty1.
Maybe a plain and brute "journalctl" and grep would have found it. But it takes minutes, even on ssd... I tried now, and I'm still waiting... It is displaying July entries. My fault for trusting the journal, I should have looked at syslog instead at the start. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)