This may not help, but....
I've had core dumps from xymonnet that I *think* are related to running LDAP checks against an Active Directory that won't talk back. Or possibly it gets junk back that it can't understand, I don't know. Some times xymonnet core-dumps, other times it hangs up. Once it hangs, no more network tests happen - I guess the scheduler sees xymonnet already running and won't start another. I've had to install a cron job that looks for xymonnet running longer than 30 minutes and kills it. This is with xymon-4.3.12, RHEL5, compiled from source.
Can you separate out some of your network tests? Maybe spin up another copy of xymon and offload either your ping or ssh or http(s) tests to it?
Ralph Mitchell
On Mon, Dec 14, 2020 at 9:53 AM Carl Melgaard <Carl.Melgaard at stab.rm.dk> wrote:
Hi,
After running for 5 hrs on my new installation on a RH 7.9, xymond has already allocated 11.5GB of memory? Last night it core-dumped multiple times, and threw ?Cannot allocate memory? in multiple xymon logfiles, ala ?newstrbuffer: Attempt to allocate failed (initialsize=1009956863): Cannot allocate memory?. Monitoring 1900 hosts currently ? on my primary system I do this with only 4 GB of memory with no issues.
Any idea where I should start to look ? it?s a terabithia installation.
Heres a couple of the core-dumps gdb?ed:
Reading symbols from /usr/libexec/xymon/xymongen...Reading symbols from /usr/lib/debug/usr/libexec/xymon/xymongen.debug...done.
done.
[New LWP 10035]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `xymongen --recentgifs --subpagecolumns=4 --report --max-eventtime=1440 --max-ac'.
Program terminated with signal 6, Aborted.
#0 0x00007f8bb64aa387 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0 0x00007f8bb64aa387 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1 0x00007f8bb64aba78 in __GI_abort () at abort.c:90
#2 0x0000561f05bf6115 in sigsegv_handler (signum=<optimized out>) at sig.c:57
#3 <signal handler called>
#4 strbuf_addtobuffer (buf=0x0, newtext=0x561f0701db60 "extcombo", ' ' <repeats 192 times>..., newlen=2000) at strfunc.c:115
#5 0x0000561f05bf79b5 in addtobufferraw (buf=<optimized out>, newdata=<optimized out>, bytes=<optimized out>) at strfunc.c:184
#6 0x0000561f05c00d32 in combo_start () at sendmsg.c:908
#7 0x0000561f05bd7ccb in main (argc=6, argv=0x7ffe092839a8) at xymongen.c:706
Reading symbols from /usr/libexec/xymon/xymonnet...Reading symbols from /usr/lib/debug/usr/libexec/xymon/xymonnet.debug...done.
done.
[New LWP 15437]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `xymonnet --report --ping --checkresponse --dns-timeout=3 --dnslog=/var/log/xymo'.
Program terminated with signal 6, Aborted.
#0 0x00007f96383f0387 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) bt
#0 0x00007f96383f0387 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1 0x00007f96383f1a78 in __GI_abort () at abort.c:90
#2 0x0000000000422d95 in sigsegv_handler (signum=<optimized out>) at sig.c:57
#3 <signal handler called>
#4 strbuf_addtobuffer (buf=0x0, newtext=0x2a99910 "extcombo", ' ' <repeats 192 times>..., newlen=2000) at strfunc.c:115
#5 0x0000000000424635 in addtobufferraw (buf=<optimized out>, newdata=<optimized out>, bytes=<optimized out>) at strfunc.c:184
#6 0x000000000042d9b2 in combo_start () at sendmsg.c:908
#7 0x00000000004064dc in main (argc=6, argv=0x7ffc4e0055d8) at xymonnet.c:2554
Seems like all core-dumps are from xymonnet and xymongen?
Where do I start?
Regards,
Carl Melgaard
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon