Moin, /var/log/syslog sieht auch etwas komisch aus, z.B. Jun 18 19:53:09 server kernel: [ 10.737058] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null) Jun 18 19:53:09 server kernel: [ 11.779206] r8169 0000:01:00.0: eth0: link down Jun 18 19:53:09 server kernel: [ 11.779219] r8169 0000:01:00.0: eth0: link down Jun 18 19:53:09 server kernel: [ 11.779837] ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 18 19:53:09 server kernel: [ 13.974125] r8169 0000:01:00.0: eth0: link up Jun 18 19:53:09 server kernel: [ 13.974834] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 18 19:53:09 server kernel: [ 24.448025] eth0: no IPv6 routers present Jun 18 19:53:09 server acpid: starting up with netlink and the input layer Jun 18 19:53:09 server acpid: 1 rule loaded Jun 18 19:53:09 server acpid: waiting for events: event logging is off Jun 18 19:53:09 server /usr/sbin/cron[2126]: (CRON) INFO (pidfile fd = 3) Jun 18 19:53:09 server /usr/sbin/cron[2127]: (CRON) STARTUP (fork ok) Jun 18 19:53:09 server /usr/sbin/cron[2127]: (CRON) INFO (Running @reboot jobs) Jun 18 19:53:10 server kernel: [ 980.884700] RPC: Registered named UNIX socket transport module. Jun 18 19:53:10 server kernel: [ 980.884708] RPC: Registered udp transport module. Jun 18 19:53:10 server kernel: [ 980.884713] RPC: Registered tcp transport module. Jun 18 19:53:10 server kernel: [ 980.884717] RPC: Registered tcp NFSv4.1 backchannel transport module. Jun 18 19:53:10 server kernel: [ 980.929080] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Jun 18 19:53:10 server kernel: [ 981.076651] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jun 18 19:53:10 server kernel: [ 981.091513] NFSD: starting 90-second grace period Man sieht den deutlichen zeitlichen Sprung nach dem Aktivieren von eth0. Das ist genau der Zeitraum, in dem ich die Meldung von rpcbind beim Starten von NFS common utilities sehe. Komisch, die (und die folgenden Zeilen, die ich danach nur kurz sehe) tauchen im Log nicht auf. Jun 18 19:53:10 server rpc.mountd[2449]: Version 1.2.6 starting Jun 18 19:53:10 server ntpd[2479]: ntpd 4.2.6p5@1.2349-o Fri Jul 22 18:00:30 UTC 2016 (1) Jun 18 19:53:10 server ntpd[2480]: proto: precision = 1.305 usec Jun 18 19:53:10 server ntpd[2480]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jun 18 19:53:10 server ntpd[2480]: Listen and drop on 1 v6wildcard :: UDP 123 Jun 18 19:53:10 server ntpd[2480]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jun 18 19:53:10 server ntpd[2480]: Listen normally on 3 eth0 192.168.1.205 UDP 123 Jun 18 19:53:10 server ntpd[2480]: Listen normally on 4 lo ::1 UDP 123 Jun 18 19:53:10 server ntpd[2480]: Listen normally on 5 eth0 fe80::290:fbff:fe3d:9c82 UDP 123 Jun 18 19:53:10 server ntpd[2480]: peers refreshed Jun 18 19:53:10 server ntpd[2480]: Listening on routing socket on fd #22 for interface updates Jun 18 19:53:11 server ntpd[2480]: Cannot find user ID 104 Das finde ich ebenfalls komisch - user ID 104 nicht gefunden? server:/var/log# cat syslog Jun 19 00:25:03 server rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2030" x-info="http://www.rsyslog.com";] rsyslogd was HUPed Jun 19 00:25:03 server rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2030" x-info="http://www.rsyslog.com";] rsyslogd was HUPed Jun 19 00:26:33 server /USR/SBIN/CRON[4614]: (root) MAIL (mailed 1 byte of output; but got status 0x0001, #012) Jun 19 01:00:39 server rpc.statd[5319]: Version 1.2.6 starting Jun 19 01:00:39 server sm-notify[5320]: Version 1.2.6 starting Jun 19 01:00:39 server sm-notify[5320]: Already notifying clients; Exiting! Jun 19 01:00:39 server rpc.statd[5319]: Failed to access local netconfig database: Netconfig database not found Jun 19 01:00:39 server rpc.statd[5319]: failed to create RPC listeners, exiting Auch das erscheint mir auffällig, die CRON-Meldung sieht eigentlich anders aus. Mit einer "netconfig database" kann ich aber nichts anfangen... Hilft das irgendwie? -- Mit freundlichem Gruß Jan Kappler
Attachment:
signature.asc
Description: OpenPGP digital signature