[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Over a year old, never addressed. Closing. I think it eventually went away so probably fixed. ** Changed in: chkrootkit (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
forgot to reset to new when I added my update. ** Changed in: chkrootkit (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Serge: at the moment, no. I can't manually reproduce it. However, I left the machine sitting over night and came back this morning to find that it was stuck yet again, this time, the egrep process was using 7.1GB of 8GB, but PS only showed 2 instances running... I'm currently running tiger manually to see if it's tiger itself, or something related to running via CRON. after the manual run, I'll try running the commands from the cron scripts manually and see if that recreates the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
This is a batch mode output from top, showing the egrep process consuming 6.7GB of my RAM... ** Attachment added: top.log https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287476/+files/top.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
this is a capture of ps axf before rebooting the system to make it usable again. Notice the 14 instances of egrep spawned by chkrootkit. ** Attachment added: ps-axf.log https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287477/+files/ps-axf.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Also, this might actually be an issue created by tiger, rather than chkrootkit itself... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 828437] Re: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram
Thanks for taking the time to submit this bug. It does seem from the ps forest output that tiger is the initial problem. Is this easily reproducible with tiger? If so, if you run chkrootkit without tiger, does it work fine? (If so, we know where to start looking and we should retarget the bug) ** Changed in: chkrootkit (Ubuntu) Importance: Undecided = Medium ** Changed in: chkrootkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/828437 Title: chkrootkit cron job went nuts, spawned 14 instances and consumed nearly 90% of my ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
