Summary: | =net-analyzer/ntop-3.2-r3 fails to stop because it can't locate ntop.pid | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew Schultz <mattsch> |
Component: | New packages | Assignee: | Gentoo Netmon project <netmon> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fbcyborg, mrness, zerochaos |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matthew Schultz
2009-01-07 17:55:37 UTC
I just tested =net-analyzer/ntop-3.3.8 and ntop.pid is placed correctly in /var/run in this version. Hello, I have net-analyzer/ntop-3.3.10-r1 but I still have this problem. When I shutdown the system I get: start-stop-daemon: fopen `/var/run/ntop.pid': No such file or directory But the strange fact is that I made some changes to the /etc/init.d/ntop initscript i.e.: I changed the line start-stop-daemon --stop --retry 30 --pidfile /var/run/ntop.pid to start-stop-daemon --stop --retry 30 --pidfile /var/lib/ntop/ntop.pid because performing a `locate ntop.pid' it given me /var/lib/ntop/ntop.pid. Then, at the next shutdown I got: start-stop-daemon: no matching processes found. So I changed again the previous line to the original state and all seemed to be OK. But now, after another reboot the problem is still here! At the moment if I perform a `locate ntop.pid' again, it returns nothing. So the ntop.pid file is neither in /var/run, nor in in /var/lib/ntop. But, if now I restart ntop `/etc/init.d/ntop restart' i get: * Stopping ntop ... * start-stop-daemon: fopen `/var/run/ntop.pid': No such file or directory [ ok ] * Starting ntop ... Fri Jan 1 17:44:25 2010 NOTE: Interface merge enabled by default Fri Jan 1 17:44:25 2010 Initializing gdbm databases And the file /var/run/ntop.pid is right there!!! O_O Of course, if I restart ntop again no warning and error messages appear. I don't understand why these things happen, but they are very strange. Any idea? By the way, I found out that each time ntop want to start at boot, it fails (???) but I don't see any significant message about it. Actually, if I do: # /etc/init.d/ntop status I get: * status: crashed But, why it is crashing? This bug is not valid for any version currently in portage. Please close. Thanks flea ~ # /etc/init.d/ntop start ntop | * Caching service dependencies ... [ ok ] ntop | * Starting ntop ... ntop |Fri Feb 25 22:42:06 2011 NOTE: Interface merge enabled by default ntop |Fri Feb 25 22:42:06 2011 Initializing gdbm databases [ ok ] flea ~ # /etc/init.d/ntop stop ntop | * Stopping ntop ... [ ok ] flea ~ # ps aux | grep ntop root 15123 0.0 0.0 6252 584 pts/1 S+ 22:43 0:00 grep --color=always ntop flea ~ # emerge --nodep -vp '=ntop-3.3.10-r2' These are the packages that would be merged, in order: ... done! [ebuild R ] net-analyzer/ntop-3.3.10-r2 USE="ipv6 ssl tcpd" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB flea ~ # (In reply to comment #4) > This bug is not valid for any version currently in portage. Please close. No, don't close it. This problem still remains instead, just right every time when I shut down the computer. Maybe the problem is due to the fact that the daemon doesn't correctly start at boot time. Actually, if I try to start and stop manually as Rick does, the problem doesn't exist and the ntop.pid can be found. That is very odd, I'll try to reproduce that on my end and see what is going on. (In reply to comment #6) > That is very odd, I'll try to reproduce that on my end and see what is going > on. > This is very odd to me too actually, but that's what it happens! :( Thank you for your patience. This seems to be fixed in 4.0.x so please test 4.0.x and reopen this bug if this issue is still persistent. |