Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12377 - ntop crashes often

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Sunday, 07 December 2008, 18:52 GMT
Last edited by Douglas Soares de Andrade (dsa) - Monday, 02 February 2009, 02:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Douglas Soares de Andrade (dsa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
ntop randomly exits with the following error:
Dec 5 21:05:17 oldbaz ntop[13712]: CLEANUP[t3072345792]: ntop caught signal 14 [state=7]

This happens randomly, sometimes at startup, sometimes after ntop has been running for minutes or hours. I haven't been able to keep ntop running reliably overnight in 3 days.
this same error happens on three systems with different processors and different amounts of RAM and signficiantly different configurations, all running arch i686. I don't have x86_64 systems to test on.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
install ntop, set password for ntop, run ntop using init script. ntop crashes periodically
This task depends upon

Closed by  Douglas Soares de Andrade (dsa)
Monday, 02 February 2009, 02:07 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Not happening here.
Comment by Douglas Soares de Andrade (dsa) - Monday, 08 December 2008, 09:21 GMT
Hi,

Did you do some research to see if the problem is not upstream ?

We just compile it in arch, so i dont see a point for it be a Arch problem.

I see that many people have problems with ntop because of configuration, could you talk if the ntop people to see if they correct ?

Im not saying that your configs are wrong, just to check then, because errors like this can be painful to fix.

Thanks
Comment by Jan de Groot (JGC) - Monday, 08 December 2008, 10:54 GMT
Signal 14 is the ALRM signal. I only know this signal from fetchmail that wakes up when it receives this signal. Is something on your system sending ALRM signals to random processes?

Edit: this SIGALRM is sent from the cleanup function. Is something logged before the signal 14 message? This message will always show up in your logs, no matter what happens when ntop exits.
Comment by Christ Schlacta (aarcane) - Monday, 08 December 2008, 16:28 GMT
I have three different systems with vastly different configurations. it's possible that signal 14 is being randomly sent by some process, but highly unlikely. as for it being an upstream bug.. I can't know, and I can't find any sort of upstream support channel for ntop, or I would have tried that as well.
Comment by Glenn Matthys (RedShift) - Thursday, 11 December 2008, 07:39 GMT
Ntop's bugtracker is here: https://svn.ntop.org/trac/report (and it really wasn't that difficult to find).
Comment by Glenn Matthys (RedShift) - Friday, 12 December 2008, 11:37 GMT
I have been running ntop on my x86_64 server for two days and I cannot reproduce this problem. Can you check crons and other timed events?
Comment by Christ Schlacta (aarcane) - Friday, 12 December 2008, 17:58 GMT
okay, only one machine is running crond. the only thing the three machines have in common is i686 architecture, arch linux, nfs, samba, and ntop. it's not cron or any other timing issue :(. also, since you can't reproduce it on x86_64, I think it's x86 specific.

Loading...