Hello

librrd has changed dependencies, I do not know if that cause
the problem.

Regards,

// Ola

On Sun, Jan 23, 2005 at 02:57:16AM -0500, A Costa wrote:
> Package: ntop
> Version: 2:3.0-3
> Severity: important
> 
>  
> 'ntop' doesn't seem to run on my system.  Not as root:
> 
>       ntop; echo $?
>       Sun Jan 23 02:34:47 2005  ntop will be started as user nobody
>       Sun Jan 23 02:34:47 2005  ntop v.3.0 SourceForge .tgz MT (SSL)
>       Sun Jan 23 02:34:47 2005  Configured on Aug  9 2004 13:13:22, built on 
> Aug  9 2004 13:14:07.
>       Sun Jan 23 02:34:47 2005  Copyright 1998-2004 by Luca Deri <[EMAIL 
> PROTECTED]>
>       Sun Jan 23 02:34:47 2005  Get the freshest ntop from 
> http://www.ntop.org/
>       Sun Jan 23 02:34:47 2005  Initializing ntop
>       Sun Jan 23 02:34:47 2005  Checking ppp0 for additional devices
>       Sun Jan 23 02:34:47 2005  Resetting traffic statistics for device ppp0
>       Sun Jan 23 02:34:47 2005  **WARNING** DLT: Device 0 [ppp0] MTU value 
> unknown
>       Sun Jan 23 02:34:47 2005  **WARNING** DLT: Processing continues OK
>       Sun Jan 23 02:34:47 2005  DLT: Device 0 [ppp0] is 113, mtu 65355, 
> header 0
>       Sun Jan 23 02:34:47 2005  Initializing gdbm databases
>       Sun Jan 23 02:34:47 2005  Now running as requested user 'nobody' 
> (65534:65534)
>       Sun Jan 23 02:34:48 2005  **FATAL_ERROR** ....open of 
> /var/lib/ntop/prefsCache.db failed: File open error
>       Sun Jan 23 02:34:48 2005  1. Is another instance of ntop running?
>       Sun Jan 23 02:34:48 2005  2. Make sure that the use you specified can 
> write in the target directory
>       255

What user have permission to that file?

Regards,

// Ola

> Not as user:
> 
>       ntop; echo $?
>       Sun Jan 23 02:34:56 2005  **WARNING** You need root capabilities to 
> capture network packets.
>       Sun Jan 23 02:34:56 2005  Unable to read shadow passwords. Become root 
> first and start ntop again
>       255
> 
> If an 'ntop' daemon should be running, it isn't:
> 
>       ps -A | grep ntop ; echo $?
>       1
> 
> Purging and reinstalling the 'ntop' package doesn't fix it.
> 
> If it matters my net connection is via a modem.
> 
> The file mentioned in the "FATAL_ERROR" exists:
> 
>       ls -Gg /var/lib/ntop/prefsCache.db
>       -rw-r--r--  1 12795 Jan 23 02:52 /var/lib/ntop/prefsCache.db
> 
> 
> Diagnosis:  I dunno...
> 
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.9-1-686
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
> 
> Versions of packages ntop depends on:
> ii  debconf                     1.4.42       Debian configuration management 
> sy
> ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries 
> an
> ii  libfreetype6                2.1.7-2.3    FreeType 2 font engine, shared 
> lib
> ii  libgd2-xpm                  2.0.33-1.1   GD Graphics Library version 2
> ii  libgdbm3                    1.8.3-2      GNU dbm database routines 
> (runtime
> ii  libglib1.2                  1.2.10-9     The GLib library of C routines
> ii  libjpeg62                   6b-9         The Independent JPEG Group's 
> JPEG 
> ii  libpcap0.7                  0.7.2-7      System interface for user-level 
> pa
> ii  libpng12-0                  1.2.8rel-1   PNG library - runtime
> ii  libssl0.9.7                 0.9.7e-3     SSL shared libraries
> ii  libxml2                     2.6.11-5     GNOME XML library
> ii  zlib1g                      1:1.2.2-4    compression library - runtime
> 
> -- debconf information:
> * ntop/interfaces: ppp0
> * ntop/user: alfie
> 
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to