leaking memory, alerts.cfg problems
Our organization is one of I'd assume many that are evaluating our options now that Dell no longer supports BigBrother.
We had a fairly smooth transition to Xymon (we compiled form source on Ubuntu 14.04.1 LTS x86-64).
The problem that we're having is that we can't find a sane way to remove a service check from our switches/routers, specifically TELNET.
We removed the column from displaying on our webpage, but we were still receiving alerts on it.
We've made customization to our alerts, but now no matter what we try, we can't get alerts to fire and sometimes see messages like:
someuser at somehost:~$ sudo vi /etc/xymon/alerts.cfg
[sudo] password for someuser: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
I've scoured the internet to no avail. Any insight? If we can get the product running reliably we're sure to use it for years to come. :)
-Tres
- Tres.Finocchiaro at gmail.com
On 9 September 2014 23:57, Tres Finocchiaro <tres.finocchiaro at gmail.com> wrote:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
This is a bug in Samba. Refer: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
This is entirely unrelated to Xymon.
If you don't have "telnet" listed for a host/device in hosts.cfg, or in the ".default." entry, then Xymon should not include it in its service checks.
J
@Jeremy,
This is a bug in Samba. Refer: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
This is entirely unrelated to Xymon.
Terrific, thank you.
If you don't have "telnet" listed for a host/device in hosts.cfg, or in the ".default." entry, then Xymon should not include it in its service checks.
OK, this is where I'm struggling. We have a separate host group for our switches:
group-sorted UFIRST Switches
0.0.0.0 .default. # NOCOLUMNS:telnet 192.168.0.5 SWITCH1 # ssh
But originally had had:
192.168.0.5 SWITCH1 # telnet
We followed the instructions for purging the history:
xymon 127.0.0.1 "drop SWITCH1 telnet"
But we still received alerts.
red Wed Sep 3 09:26:38 2014 telnet NOT ok
Service telnet on SWITCH1 is not OK : Service unavailable (Connection refused) Seconds: 0.00
So I tried filtering it in the alerts.cfg:
HOST=%* SERVICE=%*
MAIL tres at company.local EXSERVICE=telnet
But now we aren't receiving any alerts at all.
To verify it's not an email settings:
mail -s "Test Email" tres at company.local < /dev/null
Which succeeds.
The only part I did not mention is that some of our hosts were renamed from lowercase to uppercase for aesthetics.
participants (3)
-
Carl.Inglis＠rakon.com
-
jlaidman＠rebel-it.com.au
-
tres.finocchiaro＠gmail.com