One of our servers got a massive overload at peak hours an hour ago due to swapping quicking in, and from top result below it looks like due to monitor.pl process eating up loooots of RAM:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
31725 root 20 0 1656m 1.5g 3576 D 8 43.3 0:14.00 monitor.pl
In urgency, we had to kill that process, but then had to take server down and finally reboot it due to heavy swap not able to resume from this situation.
How can it be that monitor.pl is even able to use that much RAM ???
That server runs fine with 2.5 Gigs usually, and has 3.5 gigs RAM allocated. But the combined usage of RAM, and most probably of disk access contention generated by that process just killed the whole server.
btw "Collect all available package updates" was off if that matters (for collectinfo.pl).
I'm stumped and worried that this may happen again on that high-traffic server.