Hi ,
>> "After an boot S-alive works fine 10 - 20 hours, but not more than that."
If you use "External (errorlevel)" checks, be sure to enable the "Kill the
external application when not stopped in time" option. Otherwise some badly
written external commands (scripts) could consume all the memory.
Kind regards,
Pieter
From: Salive [mailto:salive-boun...@woodstone.nu] On Behalf Of Asko Ikävalko HKI
Sent: woensdag 5 december 2018 7:53
To: salive@woodstone.nu
Subject: [SA-List] S-alive unstable?
Hi all colleagues,
I'm experiencing Servers Alive version 9.0.2805 unstable in my environment. I
receive timeout errors for my ping tests (and "exe process alive" tests) even
while manual ping from command prompt answers in 10-100 ms.
Have tried:
- Different hardware (old laptop vs. new virtual machine)
- Different OS (Win 7 vs. Win 2012)
- More time between cycle runs (2 min vs. 9 min)
- Sent log files to supp...@woodstone.nu (got some help but no final solution)
Also scheduled windows boot once a week. After an boot S-alive works fine 10 -
20 hours, but not more than that. :-(
Demo version worked with 10 checking lines very fine for several months. Now I
have 85 checking lines, it shouldn't be too much?
Have anyone faced similar symptoms? Any workaround ideas?
regards,
Asko Ikavalko
IT-specialist
Helsinki, FINLAND
Dit bericht wordt verzonden vanuit een e-mailadres voor professioneel gebruik.
De verantwoordelijken binnen de organisatie kunnen kennis nemen van alle
berichten verzonden naar dit adres.
Le présent message est envoyé d'une adresse e-mail pour usage professionnel.
Les responsables de l'organisation peuvent prendre connaissance de tous les
messages envoyés à cette adresse.
This message is sent from an e-mail address for professional use only. The
persons in charge of the organisation may take note of all messages sent to
this address.
___
Salive mailing list
Salive@woodstone.nu
To unsubscribe send a mail to salive-requ...@woodstone.nu and in the subject
of the mail put the following:
unsubscribe
