Package: mrtg
Version: 2.16.2-3
Severity: important

if mrtg run by cron I get this the second time cron run it:

2008-09-29 12:40:02: ERROR: I guess another mrtg is running. A lockfile 
(/var/lock/mrtg/_etc_mrtg.cfg_l) aged
1800 seconds is hanging around. If you are sure that no other mrtg
is running you can remove the lockfile

If I add an rm to cron to delete the file after mrtg runned, then mrtg 
will not collect al the info it should. It only heppens with 2.16.2-3 
and not with 2.16.2-2. I don't know how it's possible.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing'), (101, 
'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages mrtg depends on:
ii  debconf [debconf-2.0]  1.5.22            Debian configuration management sy
ii  libc6                  2.7-13            GNU C Library: Shared libraries
ii  libgd2-noxpm           2.0.36~rc1~dfsg-3 GD Graphics Library version 2 (wit
ii  libpng12-0             1.2.27-1          PNG library - runtime
ii  libsnmp-session-perl   1.12-1            Perl support for accessing SNMP-aw
ii  perl                   5.10.0-14         Larry Wall's Practical Extraction 
ii  perl-modules           5.10.0-14         Core Perl modules
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

mrtg recommends no packages.

Versions of packages mrtg suggests:
ii  apache2-mpm-prefork [httpd] 2.2.9-7      Apache HTTP Server - traditional n
ii  links [www-browser]         2.1pre37-1.1 Web browser running in text mode
ii  lynx-cur [www-browser]      2.8.7dev9-2  Text-mode WWW Browser with NLS sup
pn  mrtg-contrib                <none>       (no description available)

-- debconf information:
  mrtg/own_user: true
* mrtg/conf_mods: false



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

Reply via email to