The alarm() message occurs when the (surprise :-)) alarm is tripped. This is set (at 15 seconds) when ntop starts to create a page. It's not 'normal', but it can happen if there are 10000s of hosts - the table walk to select + sort can take a long (very long) time.
We would need to see what page is causing this and how much data you have - the former probably needs the URL_DEBUG messages enabled (see globals-defines.h in the source) and the latter is part of the Problem Report data (the bug icon). -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of rahmad > Sent: Tuesday, July 27, 2004 12:57 PM > To: [EMAIL PROTECTED] > Subject: [Ntop-dev] Problem with Ntop > > > Hi, > > We recently ntop v3.0 on Fedora Core 2 and are proxying web requests > through Apache 2 so that we can restrict access to the data. However, > quite often, ntop stops responding to web requests; in the > /var/log/messages file, it says "Jul 27 13:48:22 ntop ntop[9215]: > **ERROR** http generation failed, alarm() tripped. Please report this to > ntop-dev list!" and we're not sure what this means. Any help would be > greatly appreciated. > > Thanks, > > Razi Ahmad > NYU Stern School of Business > > -- > Razi Ahmad > Network Administrator > Information Technology > Leonard N. Stern School of Business, New York University > 212-998-0172 > [EMAIL PROTECTED] > > _______________________________________________ > Ntop-dev mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
