You're going to hate me guys, for (still) reporting problems so close to a
release.

On this morning's CVS, I can't get daemon mode to work :
Sep  9 09:05:41 loic ntop[15981]:  [report:47] Device  0.
eth0                           (active)
Sep  9 09:05:41 loic ntop[15981]:  [report:94] Note: Reporting device initally
set to 0 [eth0]
Sep  9 09:05:41 loic ntop[15981]:  [webInterface:4775] WEB: Initializing web
server
Sep  9 09:05:41 loic ntop[15981]:  [webInterface:4781] WEB: Initializing tcp/ip
socket connections for web server
Sep  9 09:05:41 loic ntop[15981]:  [webInterface:4615] Initializing socket, port
10999, address (any)
Sep  9 09:05:41 loic ntop[15981]:  [webInterface:4684] **FATAL_ERROR** WEB:
Unable to create a new socket - returned 0, error is 'Success'(0)
Sep  9 09:05:41 loic kernel: device eth0 left promiscuous mode

Looks like a previous issue under FreeBSD (except that it's not the same
'error'), IIRC, but I am under RH9 (trace level 5 enabled)...

A few days ago, I had the same problem but forgot to report it (found unfinished
mail in my drafts box...) :
Sep  3 10:11:26 bridgetest ntop[4177]:  [main:1164] Starting web server
Sep  3 10:11:26 bridgetest ntop[4177]:  [webInterface:4576] WEB: Initializing
Sep  3 10:11:26 bridgetest ntop[4177]:  [webInterface:4619] Note: Reporting
device set to 0 [eth0]
Sep  3 10:11:26 bridgetest ntop[4177]:  [webInterface:4650] **FATAL_ERROR** WEB:
Unable to create a new socket (error 17: 'File exists')

Each time, running as a regular task (ntop @/etc/ntop.conf) or as a background
task (ntop @/etc/ntop.conf &) works, but daemon mode (ntop @/etc/ntop.conf -d)
fails...

Looking at today's code, what about the attached patch ? Works for me... ;-)

"Burton M. Strauss III" a �crit :

> 5) There are a couple of 'graph' and 'reporting' problems reported by B.Loic
> around the 25th of August
>      - Strange interface traffic pie chart with --no-interface-merge option
>      - OSPF traffic reported as "Other IP" in the TCP/UDP page
>      - colors in ntop unicast/broadcast/multicast graph

On this later issue, I noticed that :
    - it can happen on ALL pie chart graphs, wherever they are in ntop (does it
too in the protocols distribution on any host info page)
    - does it only when one of the values is very small compared to the others

Lo�c

Attachment: webinterface.c.diff
Description: application/unknown-content-type-diff_auto_file

Reply via email to