Custom Query (245 matches)

ntpd corrigeert wel de tijd, maar maakt geen ntpd.drift bestand aan, zodat telkens weer een relatief grote correctie moet worden uitgevoerd en de klok onnauwkeurig is.

Er is ook een boodschap 'servers not reachable' die ik niet kan thuisbrengen.

Zie de logfile: /var/log/ntp.log:

27 Feb 11:20:45 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 27 Feb 11:20:54 ntpd[8202]: time reset +9.127663 s 27 Feb 11:28:22 ntpd[8202]: synchronized to 172.17.8.68, stratum 3 27 Feb 11:28:52 ntpd[8202]: no servers reachable 28 Feb 18:47:23 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 28 Feb 18:53:52 ntpd[8202]: time reset +388.824812 s 28 Feb 19:00:02 ntpd[8202]: synchronized to 172.17.8.68, stratum 3 28 Feb 19:00:16 ntpd[8202]: no servers reachable 28 Feb 19:01:07 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 28 Feb 19:02:13 ntpd[8202]: no servers reachable 1 Mar 01:44:01 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 1 Mar 01:45:25 ntpd[8202]: time reset +84.560951 s 1 Mar 01:56:50 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 1 Mar 01:57:30 ntpd[8202]: no servers reachable 1 Mar 09:39:12 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 1 Mar 09:40:50 ntpd[8202]: time reset +97.666245 s 1 Mar 09:48:28 ntpd[8202]: synchronized to 172.20.128.98, stratum 3 1 Mar 09:49:22 ntpd[8202]: no servers reachable

NodeHuub was vandaag op hol geslagen: geen ssh inlog mogelijk en op serieele monitor een lawine van boodschappen (ongeveer 1 per sec.): "kern.maxfiles limit exceeded by uid 0, please see tuning(7)" ook een enkele boodschap er tussen met uid 53.

uid 0 is root (no surprise here) uid 53 is bind

Ik lees dat je die parameter kunt ophogen in sysctl.conf Het handboek zegt:

The kern.maxfiles sysctl determines how many open files the system sup- ports. The default is typically a few thousand but you may need to bump this up to ten or twenty thousand if you are running databases or large descriptor-heavy daemons. The read-only kern.openfiles sysctl may be interrogated to determine the current number of open files on the system.

maar ik lees ook op het web dat er teveel processen open kunnen zijn ("it turned out to be an issue caused by too many processes being called with the default of 4,000. Bumped it up to 25k and it seemed to take care of it").

Na reboot heb ik niet meer dan 135 open files:

root@CNodeHuub /etc]# sysctl kern.openfiles kern.openfiles: 135

Nu had ik dit probleem ook al met de 6.0 versie, dus is hier mogelijk iets anders aan de hand? Een virus dat op het netwerk rondzwerft? We hadden ook een probleem bij Unigor en Lijtweg (daar staan nu schakelklokken), maar het is niet duidelijk of daar dezelfde foutmelding kwam (als we een loghost hebben zouden we het na kunnen kijken).

/var zat vol door een MB grote snmpd.log file. Zie hieronder. Zie ook boodschap 'no access control information configured'

mibII/mta_sendmail.c:open_sendmailst: could not guess version of statistics file "/var/log/sendmail.st" Warning: no access control information configured.

It's unlikely this agent can serve any useful purpose in this state. Run "snmpconf -g basic_setup" to help you configure the snmpd.conf

file for this agent. Creating directory: /var/net-snmp NET-SNMP version 5.4.2.1 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-2319 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-6433 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-14236 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-5286 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.19.137.66]:-5286 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-5286 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-5286 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-5286 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.19.137.66]:-9239 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7194 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7370 Received SNMP packet(s) from UDP: [0.0.0.0]->[172.16.2.114]:-7370 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7370 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7370 Connection from UDP: [0.0.0.0]->[172.16.2.114]:-7370

etc etc