[opensuse] After update, nscd does not start.
Hi, After update (15.0), nscd does not start. Have a lot of fun... Isengard:~ # systemctl status nscd ● nscd.service - Name Service Cache Daemon Loaded: loaded (/usr/lib/systemd/system/nscd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-12-08 22:16:20 CET; 1min 18s ago Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Service RestartSec=100ms expired, scheduling restart. Dec 08 22:16:20 Isengard systemd[1]: Stopped Name Service Cache Daemon. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Start request repeated too quickly. Dec 08 22:16:20 Isengard systemd[1]: Failed to start Name Service Cache Daemon. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Isengard:~ # systemctl start nscd Job for nscd.service failed because the control process exited with error code. See "systemctl status nscd.service" and "journalctl -xe" for details. Isengard:~ # systemctl status nscd ● nscd.service - Name Service Cache Daemon Loaded: loaded (/usr/lib/systemd/system/nscd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-12-08 22:17:51 CET; 1min 50s ago Process: 3973 ExecStart=/usr/sbin/nscd (code=exited, status=1/FAILURE) 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'. Isengard:~ # 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. I have not modified it recently: Isengard:~ # l /etc/nscd.conf* -rw-r--r-- 1 root root 2480 Nov 4 15:32 /etc/nscd.conf Isengard:~ # Isengard:~ # cat /etc/nscd.conf | egrep -v "^[[:space:]]*$|^#" server-user nscd debug-level 0 paranoia no enable-cache passwd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cache group yes positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes #CER por defecto es "yes", no estoy seguro de lo que conviene. Tengo servidor DNS en esta máquina enable-cache hosts no positive-time-to-live hosts 600 negative-time-to-live hosts 0 suggested-size hosts 211 check-files hosts yes persistent hosts no shared hosts yes max-db-size hosts 33554432 enable-cache services yes positive-time-to-live services 28800 negative-time-to-live services 20 suggested-size services 211 check-files services yes persistent services yes shared services yes max-db-size services 33554432 enable-cache netgroup yes positive-time-to-live netgroup 28800 negative-time-to-live netgroup 20 suggested-size netgroup 211 check-files netgroup yes persistent netgroup yes shared netgroup yes max-db-size netgroup 33554432 Isengard:~ # Isengard:~ # rpm -qi nscd Name : nscd Version : 2.26 Release : lp150.11.9.1 Architecture: x86_64 Install Date: Sun Nov 4 13:27:20 2018 Group : System/Daemons Size : 162835 License : GPL-2.0+ Signature : RSA/SHA256, Fri Oct 26 14:28:10 2018, Key ID b88b2fd43dbdc284 Source RPM : glibc-2.26-lp150.11.9.1.src.rpm Build Date : Fri Oct 26 14:24:07 2018 Build Host : lamb16 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.gnu.org/software/libc/libc.html Summary : Name Service Caching Daemon Description : Nscd caches name service lookups and can dramatically improve performance with NIS, NIS+, and LDAP. Distribution: openSUSE Leap 15.0 Isengard:~ # Isengard:~ # zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... The following 4 items are locked and will not be changed by any action: Available: PackageKit gnome-packagekit pk-update-icon plymouth Nothing to do. Isengard:~ # Ideas? besides that, the server seems to be running Ok. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-08-18 16:34]:
Hi,
After update (15.0), nscd does not start.
Have a lot of fun... Isengard:~ # systemctl status nscd ● nscd.service - Name Service Cache Daemon Loaded: loaded (/usr/lib/systemd/system/nscd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-12-08 22:16:20 CET; 1min 18s ago
Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Service RestartSec=100ms expired, scheduling restart. Dec 08 22:16:20 Isengard systemd[1]: Stopped Name Service Cache Daemon. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Start request repeated too quickly. Dec 08 22:16:20 Isengard systemd[1]: Failed to start Name Service Cache Daemon. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Unit entered failed state. Dec 08 22:16:20 Isengard systemd[1]: nscd.service: Failed with result 'exit-code'. Isengard:~ # systemctl start nscd Job for nscd.service failed because the control process exited with error code. See "systemctl status nscd.service" and "journalctl -xe" for details. Isengard:~ # systemctl status nscd ● nscd.service - Name Service Cache Daemon Loaded: loaded (/usr/lib/systemd/system/nscd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-12-08 22:17:51 CET; 1min 50s ago Process: 3973 ExecStart=/usr/sbin/nscd (code=exited, status=1/FAILURE)
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'. Isengard:~ #
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.
I have not modified it recently:
Isengard:~ # l /etc/nscd.conf* -rw-r--r-- 1 root root 2480 Nov 4 15:32 /etc/nscd.conf Isengard:~ #
Isengard:~ # cat /etc/nscd.conf | egrep -v "^[[:space:]]*$|^#" server-user nscd debug-level 0 paranoia no enable-cache passwd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cache group yes positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes #CER por defecto es "yes", no estoy seguro de lo que conviene. Tengo servidor DNS en esta máquina enable-cache hosts no positive-time-to-live hosts 600 negative-time-to-live hosts 0 suggested-size hosts 211 check-files hosts yes persistent hosts no shared hosts yes max-db-size hosts 33554432 enable-cache services yes positive-time-to-live services 28800 negative-time-to-live services 20 suggested-size services 211 check-files services yes persistent services yes shared services yes max-db-size services 33554432 enable-cache netgroup yes positive-time-to-live netgroup 28800 negative-time-to-live netgroup 20 suggested-size netgroup 211 check-files netgroup yes persistent netgroup yes shared netgroup yes max-db-size netgroup 33554432 Isengard:~ #
Isengard:~ # rpm -qi nscd Name : nscd Version : 2.26 Release : lp150.11.9.1 Architecture: x86_64 Install Date: Sun Nov 4 13:27:20 2018 Group : System/Daemons Size : 162835 License : GPL-2.0+ Signature : RSA/SHA256, Fri Oct 26 14:28:10 2018, Key ID b88b2fd43dbdc284 Source RPM : glibc-2.26-lp150.11.9.1.src.rpm Build Date : Fri Oct 26 14:24:07 2018 Build Host : lamb16 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.gnu.org/software/libc/libc.html Summary : Name Service Caching Daemon Description : Nscd caches name service lookups and can dramatically improve performance with NIS, NIS+, and LDAP. Distribution: openSUSE Leap 15.0 Isengard:~ #
Isengard:~ # zypper patch Loading repository data... Reading installed packages... Resolving package dependencies...
The following 4 items are locked and will not be changed by any action: Available: PackageKit gnome-packagekit pk-update-icon plymouth
Nothing to do. Isengard:~ #
Ideas?
besides that, the server seems to be running Ok.
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
chmod o-rx /var/run/chrony -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [12-08-18 20:42]: ...
chmod o-rx /var/run/chrony
disreguard -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi, It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
auxsvr wrote:
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi,
It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong.
Maybe even running it from the commandline - it might just tell you something. Like Peter's, my nscd is running fine, but I'm just running an update, I'll let you know how it goes. -- Per Jessen, Zürich (9.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/12/2018 11.22, Per Jessen wrote:
auxsvr wrote:
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi,
It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong.
Maybe even running it from the commandline - it might just tell you something.
Yes, exactly. I forgot to do that, but often daemons have to started in an specific manner. I wrongly expected systemd to log the error messages :-(
Like Peter's, my nscd is running fine, but I'm just running an update, I'll let you know how it goes.
It had failed a month ago and I did not see it, booting in graphical mode, and just after upgrading from 42.3 to 15.0. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-10-18 08:20]:
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.
it's a failure that systemd doesn't log failures from kmail or thunderbird or digikam? surely you jest. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/12/2018 14.24, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [12-10-18 08:20]:
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.
it's a failure that systemd doesn't log failures from kmail or thunderbird or digikam? surely you jest.
A failure to report the error on starting nscd.service. Where do you get the kmail idea from? not form me. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [12-10-18 08:36]:
On 10/12/2018 14.24, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [12-10-18 08:20]:
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.
it's a failure that systemd doesn't log failures from kmail or thunderbird or digikam? surely you jest.
A failure to report the error on starting nscd.service. Where do you get the kmail idea from? not form me.
not systemd's problem when nscd fail because it is misconfigured.... nor for kmail or .... why are you so quick to blame systemd? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Per Jessen, Zürich (5.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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)
On 09/12/2018 09.43, auxsvr wrote:
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi,
It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong.
Ah! Parse error on the configuration file. A line like this: [TAB]#CER ... text The comment symbol has to be exactly on the first char :-( I would think that a bug. And another that systemd doesn't report the real error output. Isengard:~ # /usr/sbin/nscd /usr/sbin/nscd: Parse error: /usr/sbin/nscd: Unknown option: CER por /usr/sbin/nscd: failure while reading configuration file; this is fatal Isengard:~ # This error is a month old, the computer has been running for a month without that daemon just fine, not needed then. And I did not notice, there is no way on a graphical boot to know a service failed unless one looks carefully as the machine boots. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E.R. wrote:
This error is a month old, the computer has been running for a month without that daemon just fine, not needed then.
That's true, it isn't _needed_ , it's just a performance optimisation. -- Per Jessen, Zürich (9.5°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/12/2018 13.30, Per Jessen wrote:
Carlos E.R. wrote:
This error is a month old, the computer has been running for a month without that daemon just fine, not needed then.
That's true, it isn't _needed_ , it's just a performance optimisation.
But I did not feel any slowness, over a month. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 09/12/2018 13.30, Per Jessen wrote:
Carlos E.R. wrote:
This error is a month old, the computer has been running for a month without that daemon just fine, not needed then.
That's true, it isn't _needed_ , it's just a performance optimisation.
But I did not feel any slowness, over a month.
Performance optimizations are not necessarily all meant for you to notice. :-) You won't notice that every repeat DNS lookup is a little bit faster than the first lookup. It still means better performance locally as well as for the DNS system. Also means less network traffic. -- Per Jessen, Zürich (9.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/12/2018 16.40, Per Jessen wrote:
Carlos E. R. wrote:
On 09/12/2018 13.30, Per Jessen wrote:
Carlos E.R. wrote:
This error is a month old, the computer has been running for a month without that daemon just fine, not needed then.
That's true, it isn't _needed_ , it's just a performance optimisation.
But I did not feel any slowness, over a month.
Performance optimizations are not necessarily all meant for you to notice. :-) You won't notice that every repeat DNS lookup is a little bit faster than the first lookup. It still means better performance locally as well as for the DNS system. Also means less network traffic.
The DNS server is local to that machine, so actually I did: /etc/nscd.conf: #CER ... comment in Spanish enable-cache hosts no and this caused nscd to fail without recording an error message to syslog or system catpturing the text output to terminal and recording it. The corrected entry now is: /etc/nscd.conf: #CER ... comment in Spanish enable-cache hosts no -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
09.12.2018 13:54, Carlos E.R. пишет:
On 09/12/2018 09.43, auxsvr wrote:
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi,
It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong.
Ah! Parse error on the configuration file. A line like this:
[TAB]#CER ... text
The comment symbol has to be exactly on the first char :-(
I would think that a bug. And another that systemd doesn't report the real error output.
Again systemd bashing without even slightest attempt to diagnose what happened.
Isengard:~ # /usr/sbin/nscd /usr/sbin/nscd: Parse error: /usr/sbin/nscd: Unknown option: CER por /usr/sbin/nscd: failure while reading configuration file; this is fatal Isengard:~ #
Logs do contain this output. No, they are not spoon fed to you, but you are not newbie either. At this point you should know how to use journalctl or where to find syslog output.
On 09/12/2018 19.46, Andrei Borzenkov wrote:
09.12.2018 13:54, Carlos E.R. пишет:
On 09/12/2018 09.43, auxsvr wrote:
On Saturday, 8 December 2018 23:33:22 EET Carlos E. R. wrote:
Hi,
After update (15.0), nscd does not start. Ideas? besides that, the server seems to be running Ok.
Hi,
It works here. What does it return when you run /usr/sbin/nscd? Also, strace would help to find out what's wrong.
Ah! Parse error on the configuration file. A line like this:
[TAB]#CER ... text
The comment symbol has to be exactly on the first char :-(
I would think that a bug. And another that systemd doesn't report the real error output.
Again systemd bashing without even slightest attempt to diagnose what happened.
Isengard:~ # /usr/sbin/nscd /usr/sbin/nscd: Parse error: /usr/sbin/nscd: Unknown option: CER por /usr/sbin/nscd: failure while reading configuration file; this is fatal Isengard:~ #
Logs do contain this output. No, they are not spoon fed to you, but you are not newbie either. At this point you should know how to use journalctl or where to find syslog output.
Yes, I bash systemd for not reporting the error it got, because the journal had absolutely nothing about the problem. You can see it in the first message. The proper message was in syslog, not in journal. I only looked at the journal. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (6)
-
Andrei Borzenkov -
auxsvr -
Carlos E. R. -
Carlos E.R. -
Patrick Shanahan -
Per Jessen