|
From: Victor T. <vic...@gm...> - 2005-12-18 23:32:38
|
Jamie, To me it seems as though mail_search.cgi and view_mail.cgi runs the shell hostname process. It is this hostname process that is taking 100%. After a week or so, if I don't manually kill the hostname processes, I'll have 4-5 processes all competing for 100% CPU. What could be causing this? Is Webmin waiting for results from /bin/sh -c (hostname) but never getting anything? Perhaps my system isn't properly configured in some way? If it helps, I am running Gentoo (AMD64 SMP) and Webmin 1.250. I think it started when I upgraded to Webmin 1.230, and I was hoping 1.250 would fix it, but it hasn't. I also upgraded some other packages around the time of 1.230 as well, so I can't isolate that it is being caused by Webmin. Thanks, Victor On Mon, 19 Dec 2005 9:06:00 1100, Jamie Cameron <jca...@we...> wrote= : > Hi Victor, > So is it the hostname process that is using up all the CPU time, or Webmi= n's mail_search.cgi script? The hostname command is just called to get the = system's name to display at the top (or bottom) of the page, but really sho= uldn't be taking much time to run .. > > The mail_search.cgi script however could take a while, especially for a h= uge mailbox or if it has a bug :-) What size mail file are you trying to se= arch there? > > - Jamie > > -----Original Message----- > > From: Victor Trac <vic...@gm...> > Subj: Re: [webmin-l] /bin/sh -c (hostname) > Date: Mon 19 Dec 2005 8:14 am > Size: 1K > To: web...@li... > > Sorry, I guess it was hard to tell from my email, but I followed the > parent PID of the shell processes and found that they were started by > /usr/libexec/webmin/mailboxes/mail_search.cgi, which was launched by > /usr/libexec/webmin/miniserv.pl /etc/webmin/miniserv.conf. This > correlates with the webmin mail reader timing out when I'm reading > mail. It only happens when I (or someone else on my box) is using > webmin to read email. > > > > ---- > > It might be helpful to find out which processes are causing the race > > conditions and I use top for that. In your case, it's possible that it > > isn't the shell process but something occurring within the shell. > > > > Craig > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > - > > Forwarded by the Webmin mailing list at web...@li...= .net > > To remove yourself from this list, go to > > http://lists.sourceforge.net/lists/listinfo/webadmin-list > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=CCk > - > Forwarded by the Webmin mailing list at web...@li....n= et > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list > > --- message truncated --- > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > - > Forwarded by the Webmin mailing list at web...@li....n= et > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list > |