Going to sleep

2bit-gehirn

New Member
Hallo.
In unregelmäßigen Abständen fährt mein V-Server (Greatnet) runter. Nun habe ich einmal in den Logbüchern nachgesehen und folgendes gefunden:

Code:
XXXXX:/var/log # cat zmd-messages.log
28 Mar 2009 05:42:04 INFO  Daemon               Starting ZMD version 7.1.100
28 Mar 2009 05:42:04 INFO  Daemon               Using Mono 1.1.18.1
28 Mar 2009 05:42:04 INFO  KeyManager           Loading key whitelist
28 Mar 2009 05:42:04 INFO  Daemon               Loading trusted certificates...
28 Mar 2009 05:42:04 WARN  NetworkManagerModule Failed to connect to NetworkManager
28 Mar 2009 05:42:04 INFO  PackageManagementModule Using ZYPP backend
28 Mar 2009 05:42:05 INFO  RPMBackend           Loading installed packages
28 Mar 2009 05:42:05 INFO  RPMBackend           Finished loading installed packages
28 Mar 2009 05:42:05 INFO  ModuleLoader         Loaded 'NetworkManager' - 'NetworkManager support'
28 Mar 2009 05:42:05 INFO  ModuleLoader         Loaded 'Package Management' - 'Package Management module for Linux'
28 Mar 2009 05:42:05 INFO  ModuleLoader         Loaded 'ZENworks Server' - 'SOAP methods used by a ZENworks server'
28 Mar 2009 05:42:05 INFO  ModuleLoader         Loaded 'XML-RPC interface' - 'Export ZMD public interfaces over XML-RPC'
28 Mar 2009 05:42:05 INFO  ServiceManager       Mounting Initial Services
28 Mar 2009 05:42:05 INFO  ServiceManager       Adding service (keeping if fail): @local
28 Mar 2009 05:42:05 INFO  ServiceManager       Adding service (keeping if fail): cd:///?devices=/dev/hdc&alias=20070121-184511
28 Mar 2009 05:42:05 INFO  Daemon               Waiting for services to mount...
28 Mar 2009 05:42:05 INFO  ServiceManager       Successfully added service '@local'
28 Mar 2009 05:42:06 INFO  HelperProgress       Unknown alias '20070121-184511' passed.
28 Mar 2009 05:42:07 INFO  ServiceManager       Successfully added service '20070121-184511'
28 Mar 2009 05:42:07 INFO  WebCache             Expiring cached files...
28 Mar 2009 05:42:07 INFO  ServiceManager       Finished Service Refresh
28 Mar 2009 05:42:07 INFO  RPMBackend           Updating status of patches...
28 Mar 2009 05:42:09 INFO  RPMBackend           Finished updating patch status
28 Mar 2009 05:42:10 INFO  UnixWebServer        Unix server listening for connections.
28 Mar 2009 05:42:10 WARN  Daemon               Not starting remote web server
28 Mar 2009 05:42:10 INFO  DaemonHealth         Current RSS size is 23888 KB
28 Mar 2009 06:42:05 INFO  DaemonHealth         Current RSS size is 4588 KB
[COLOR=Red]28 Mar 2009 06:42:08 WARN  ShutdownManager      Preparing to sleep...
28 Mar 2009 06:42:09 WARN  ShutdownManager      Going to sleep, waking up at 03/29/2009 05:32:04[/COLOR]
28 Mar 2009 17:15:00 INFO  Daemon               Starting ZMD version 7.1.100
28 Mar 2009 17:15:00 INFO  Daemon               Using Mono 1.1.18.1
28 Mar 2009 17:15:01 INFO  WebCache             Expiring cached files...
28 Mar 2009 17:15:01 INFO  KeyManager           Loading key whitelist
28 Mar 2009 17:15:01 INFO  Daemon               Loading trusted certificates...
28 Mar 2009 17:15:01 WARN  NetworkManagerModule Failed to connect to NetworkManager
28 Mar 2009 17:15:01 INFO  PackageManagementModule Using ZYPP backend
28 Mar 2009 17:15:07 INFO  RPMBackend           Loading installed packages
28 Mar 2009 17:15:08 INFO  RPMBackend           Finished loading installed packages
28 Mar 2009 17:15:08 INFO  ModuleLoader         Loaded 'NetworkManager' - 'NetworkManager support'
28 Mar 2009 17:15:08 INFO  ModuleLoader         Loaded 'Package Management' - 'Package Management module for Linux'
28 Mar 2009 17:15:08 INFO  ModuleLoader         Loaded 'ZENworks Server' - 'SOAP methods used by a ZENworks server'
28 Mar 2009 17:15:08 INFO  ModuleLoader         Loaded 'XML-RPC interface' - 'Export ZMD public interfaces over XML-RPC'
28 Mar 2009 17:15:09 INFO  ServiceManager       Mounting Initial Services
28 Mar 2009 17:15:09 INFO  ServiceManager       Adding service (keeping if fail): @local
28 Mar 2009 17:15:09 INFO  ServiceManager       Successfully added service '@local'
28 Mar 2009 17:15:09 INFO  ServiceManager       Adding service (keeping if fail): cd:///?devices=/dev/hdc&alias=20070121-184511
28 Mar 2009 17:15:09 WARN  Daemon               Not starting remote web server
28 Mar 2009 17:15:09 INFO  UnixWebServer        Unix server listening for connections.
28 Mar 2009 17:15:10 INFO  DaemonHealth         Current RSS size is 17384 KB
28 Mar 2009 17:15:14 INFO  HelperProgress       Unknown alias '20070121-184511' passed.
28 Mar 2009 17:15:15 INFO  ServiceManager       Successfully added service '20070121-184511'
28 Mar 2009 17:15:15 INFO  WebCache             Expiring cached files...
28 Mar 2009 17:15:15 INFO  ServiceManager       Finished Service Refresh
28 Mar 2009 17:15:15 INFO  RPMBackend           Updating status of patches...
28 Mar 2009 17:15:20 INFO  RPMBackend           Finished updating patch status
XXXXX:/var/log #
Ich mache dann immer, wenn ich mitbekomme, dass der Server wieder mal "hängt" über die Management-Console von Greatnet einen Kaltstart des Servers - was aber keine wirkliche Lösung ist. Zudem funktioniert dabei ja auch nicht der Mail-Server, wonach ich in dieser Zeit keine eMails empfangen kann und der Sender eine Fehlermeldung bekommt.

Kann mir dabei bitte jemand helfen? Das wäre nett.

Gruß, 2Bit-Gehirn

PS: Ich bin Anfänger was Linux und Server angeht.
 
Ich nehme mal an, dass es sich um ein Suse-Betriebssystem handelt?
Der Suse-ZMD, dessen Logfile du gepostet hast, macht irgendwas, was sich mir auch gerade nicht erschließt, solche Einträge sind aber durchaus normal, da der Daemon ja nicht die ganze Zeit aktiv sein muss.

Das Logfile, wo du Einträge zu den Problemen finden solltest, ist unter /var/log/messages. ;)

Wenn der Server "hängt" - kannst du ihn dann noch anpingen, oder sind dann nur einige Dienste unerreichbar?
 
@Lord Gurke: Vielen Dank für deine erste Einschätzung. Entschuldige bitte, du hast natürlich recht. Es handelt sich um ein Suse-OS. Hätte es erwähnen müssen.

Ich habe einmal die Datei View attachment messages.zip diesem Post angehangen, allerdings nur Auszugsweise für den besagten Tag. Sind dennoch viele Einträge vorhanden. Ich habe allerdings keine Anhaltspunkte gefunden - aber ich bin eben auch nur ein Leihe...
 
Last edited by a moderator:
Laie. :rolleyes:

Was das anpingen angeht, so werde ich beim nächsten Mal daran denken und es ausprobieren. Bis jetzt habe ich es allerdings noch nicht versucht.
 
Mar 28 08:41:22 t1397 kernel: [<ffffffff8024e696>] out_of_memory+0x6d/0x1bf
[...]
Mar 28 17:14:56 t1397 syslog-ng[3139]: syslog-ng version 1.6.11 starting

Der "out_of_memory"-Fehler kommt ja ohne Ende vor, bis die Maschine (von dir?) um 17:14 neugestartet wurde.
Möglicherweise läuft da ein Prozess auf dem Server irgendwann Amok und braucht den ganzen Speicher auf. Eventuell ist es auch ein Angriff auf eine Lücke in der SASL-Bibliothek (wird für die Authentifizierung am Mailserver genutzt). Diese Lücke führt dazu, dass SASL sich Speicher reserviert, diesen aber nicht wieder freigibt.
Hast du in der /var/log/mail.info eventuell sehr viele fehlgeschlagene Loginversuche?

Auf jeden Fall ringt dein System um jedes Byte freien Speicher und schießt dabei vermutlich nach und nach Apache, SSH etc... ab.
 
@Lord Gurke: Zu dem besagten Zeitraum steht in der mail.info nichts drin. Der einzigste Eintrag vor dem "Going to sleep" ist am 27.03. um 21:15 Uhr.

Code:
Mar 27 21:15:25 XXXXX postfix/anvil[5403]: statistics: max connection rate 1/60s for (smtp:62.159.194.68) at Mar 27 21:11:58
Mar 27 21:15:25 XXXXX postfix/anvil[5403]: statistics: max connection count 1 for (smtp:62.159.194.68) at Mar 27 21:11:58
Mar 27 21:15:25 XXXXX postfix/anvil[5403]: statistics: max cache size 1 at Mar 27 21:11:58
Mar 28 13:01:52 XXXXX spamd[3581]: prefork: child states: II
Mar 28 14:53:42 XXXXX spamd[3581]: prefork: child states: II
Mar 28 17:14:59 XXXXX postfix/postfix-script: starting the Postfix mail system
Mar 28 17:14:59 XXXXX postfix/master[3537]: daemon started -- version 2.3.2, configuration /etc/postfix
Mar 28 17:15:02 XXXXX spamd[3437]: logger: removing stderr method
Mar 28 17:15:03 XXXXX spamd[3669]: config: failed to parse line, skipping: use_dcc 1
Mar 28 17:15:03 XXXXX spamd[3669]: config: failed to parse, now a plugin, skipping: ok_languages all
Mar 28 17:15:03 XXXXX spamd[3669]: rules: meta test DIGEST_MULTIPLE has undefined dependency 'DCC_CHECK'
Mar 28 17:15:03 XXXXX spamd[3669]: spamd: server started on port 783/tcp (running version 3.1.6)
Mar 28 17:15:03 XXXXX spamd[3669]: spamd: server pid: 3669
Mar 28 17:15:03 XXXXX spamd[3669]: spamd: server successfully spawned child process, pid 3693
Mar 28 17:15:03 XXXXX spamd[3669]: spamd: server successfully spawned child process, pid 3694
Mar 28 17:15:03 XXXXX spamd[3669]: prefork: child states: II
Der Server wurde von mir um 17:14 Uhr über die Greatnet-Management-Console neu gestartet.

Ich habe hier auch einmal den Tagesauszug vom 28. aus der mail.warn heraus gesucht:

Code:
Mar 28 01:33:19 XXXXX postfix/pickup[8547]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 01:33:19 XXXXX postfix/pickup[8547]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 03:13:19 XXXXX postfix/pickup[9333]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 03:13:19 XXXXX postfix/pickup[9333]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 04:53:19 XXXXX postfix/pickup[10029]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 04:53:19 XXXXX postfix/pickup[10029]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 06:33:20 XXXXX postfix/pickup[10918]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 06:33:20 XXXXX postfix/pickup[10918]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 08:13:20 XXXXX postfix/pickup[11558]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 08:13:20 XXXXX postfix/pickup[11558]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 11:12:50 XXXXX postfix/pickup[12105]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 11:12:52 XXXXX postfix/pickup[12105]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 13:29:16 XXXXX postfix/pickup[12854]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 13:29:19 XXXXX postfix/pickup[12854]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 16:02:20 XXXXX spamd[3581]: Use of uninitialized value in vec at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 268.
Mar 28 17:14:58 XXXXX postfix[3385]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:58 XXXXX postfix[3385]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:58 XXXXX postfix/master[3428]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:58 XXXXX postfix/master[3428]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:58 XXXXX postfix/master[3428]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:58 XXXXX postfix/master[3428]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:58 XXXXX postfix/postsuper[3476]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:58 XXXXX postfix/postsuper[3476]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:59 XXXXX postfix/postfix-script: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:59 XXXXX postfix/postfix-script: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:59 XXXXX postfix/master[3537]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:59 XXXXX postfix/master[3537]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:59 XXXXX postfix/master[3537]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:59 XXXXX postfix/master[3537]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:59 XXXXX postfix/pickup[3563]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:59 XXXXX postfix/pickup[3563]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:14:59 XXXXX postfix/qmgr[3564]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:14:59 XXXXX postfix/qmgr[3564]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:15:00 XXXXX postfix[3595]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:15:00 XXXXX postfix[3595]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 16:15:00 XXXXX postfix/postqueue[3600]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 16:15:00 XXXXX postfix/postqueue[3600]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:03 XXXXX postfix/smtpd[4198]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:03 XXXXX postfix/smtpd[4198]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:03 XXXXX postfix/proxymap[4202]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:03 XXXXX postfix/proxymap[4202]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:04 XXXXX postfix/anvil[4207]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:04 XXXXX postfix/anvil[4207]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:04 XXXXX postfix/trivial-rewrite[4211]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:04 XXXXX postfix/trivial-rewrite[4211]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:04 XXXXX postfix/cleanup[4216]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:04 XXXXX postfix/cleanup[4216]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 17:35:04 XXXXX postfix/local[4222]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 17:35:04 XXXXX postfix/local[4222]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/smtpd[5076]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/smtpd[5076]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/proxymap[5080]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/proxymap[5080]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/anvil[5084]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/anvil[5084]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/trivial-rewrite[5088]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/trivial-rewrite[5088]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/cleanup[5092]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/cleanup[5092]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:31:49 XXXXX postfix/local[5096]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:31:49 XXXXX postfix/local[5096]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 18:53:59 XXXXX postfix/pickup[6253]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 18:53:59 XXXXX postfix/pickup[6253]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 20:33:59 XXXXX postfix/pickup[7138]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 20:33:59 XXXXX postfix/pickup[7138]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 22:13:59 XXXXX postfix/pickup[8112]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 22:13:59 XXXXX postfix/pickup[8112]: warning: inet_protocols: configuring for IPv4 support only
Mar 28 23:53:59 XXXXX postfix/pickup[8959]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Mar 28 23:53:59 XXXXX postfix/pickup[8959]: warning: inet_protocols: configuring for IPv4 support only
Vielleicht ist noch die Datei warn interessant, jedenfalls hier als Anhang für den 28.3. (View attachment warn.zip).
 
Es ist kein April-Scherz!

Am 1. April hat er wieder herunter gefahren (going to sleep) - genau genommen um 18:35 Uhr. Zum Glück bin ich zu dem Zeitpunkt gerade an einer der Webseiten, welche sich auf dem Server befinden, beschäftigt gewesen.

Dabei habe ich auch gleich versucht, den Server anzupingen, das hat geklappt. (Von Windows mit ping [IP-Adresse des Servers] ergab 4 Pakete gesendet, 4 empfangen in 40 ms.)

Außerdem habe ich eben auch gesehen, dass er wohl auch nach 20 Uhr nochmals eingeschlafen ist.

Ich habe überhaupt keine Ahung, was ich machen soll wegen des ständigen einschlafens des Servers. Es nervt nur langsam und es macht durchaus einige Projekte, welche auf dem Server laufen, kaputt.

View attachment logs.zip
 
Back
Top