Package: fwlogwatch
Version: 1.4-4
Severity: important
X-Debbugs-Cc: jfbache...@free.fr
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I really don't know why it crashes, as logs says it never has started since
installation of Debian 12 (uptodate)
* What exactly did you do (or not do) that was effective (or
ineffective)?
tried stating it by hand via systemctl, read the logs, read the doc, coorected
a missing /run/fwlogwatch.pid file needed by systemd that hadn't been created
at install time...
* What was the outcome of this action?
stil don't start with the same error code.
see my post on the mailling-list about this bug (lotsa infos)
* What outcome did you expect instead?
as it is installed by default it should work ^^)
*** End of the template - remove these template lines ***
Regards,
Jeff
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-27-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwlogwatch depends on:
ii debconf [debconf-2.0] 1.5.82
ii exim4-daemon-light [mail-transport-agent] 4.96-15+deb12u6
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u9
ii libcrypt1 1:4.4.33-2
ii lsb-base 11.6
ii rsyslog [system-log-daemon] 8.2302.0-1
ii sysvinit-utils [lsb-base] 3.06-4
ii zlib1g 1:1.2.13.dfsg-1
fwlogwatch recommends no packages.
fwlogwatch suggests no packages.
-- debconf information:
fwlogwatch/realtime: false
fwlogwatch/cron_parameters: -p -d -O ta -t -e -l 1d
fwlogwatch/notify: no
fwlogwatch/buildconfig: true
fwlogwatch/respond: no
fwlogwatch/cron_email: none
fwlogwatch/email: root@localhost
Hello Tomas 🙂
Le 20/11/2024 à 13:38, to...@tuxteam.de a écrit :
> On Wed, Nov 20, 2024 at 01:19:24PM +0100, Jean-François Bachelet wrote:
>> Hello folks 🙂
>>
>> I got a machine to look at, so I've issued a 'systemctl status' and see a
>> 'degraded' state.
>>
>> so I've done a 'systemctl status --failed' and see that 'fwlogwatch.service'
>> was never started and shows 'exit code' as reasons...
>>
>> looking at the logs it appears it has never started fine since debian 12
>> install on this machine...
> Guessing by the package description, fwlogwatch just collects diverse
> firewall logs and (optionally) may take actions. Moreover, the description
> encourages the guess that you might try starting it manually, to see
> what kind of complaints it has?
it is started by systemd at boot but crash.
I've tested starting it manualy with 'systemctl start fwlogwatch' but or reboot
after disabling ufw, but no changes.
it seems to be installed by default, but if it not work what's the point ? :/
> It seems to have a man page.
checked it, nothing special in it, the only thing turned on is the
'fwlogwatch.pid' file that must be found by systemd in /run...
after check that file hasn't be created at installation time...
so I've 'touched' it 😉
and tried again a start... crash but some more infos now :
'systemctl start fwlogwatch.service' (root mode ;))
failed with exit code...
'systemctl status fwlogwatch.service' :
> fwlogwatch.service - Firewall log analyzer
> Loaded: loaded (/lib/systemd/system/fwlogwatch.service; enabled; preset:
> enabled)
> Active: failed (Result: exit-code) since Wed 2024-11-20 17:02:18 CET;
> 1min 27s ago
> Docs: man:fwlogwatch
> Process: 294164 ExecStart=/bin/sh -c if [ "x${START_DAEMON}" != "xtrue"
> ]; then echo "aborted"; exit 1; fi; exec /usr/sbin/fwlogwatch -c
> /etc/fwlogwatch/fwlogwatch.config -R ${PARAMS} (code=exited, status=1/FAILURE)
> CPU: 16ms
>
> nov. 20 17:02:18 deb systemd[1]: Starting fwlogwatch.service - Firewall log
> analyzer...
> nov. 20 17:02:18 deb sh[294164]: aborted
> nov. 20 17:02:18 deb systemd[1]: fwlogwatch.service: Control process exited,
> code=exited, status=1/FAILURE
> nov. 20 17:02:18 deb systemd[1]: fwlogwatch.service: Failed with result
> 'exit-code'.
> nov. 20 17:02:18 deb systemd[1]: Failed to start fwlogwatch.service -
> Firewall log analyzer.
'journalctl -xeu fwlogwatch.service' :
> ░░ L'unité (unit) fwlogwatch.service a échoué, avec le résultat failed.
> nov. 20 17:02:18 voxdeb systemd[1]: Starting fwlogwatch.service - Firewall
> log analyzer...
> ░░ Subject: L'unité (unit) fwlogwatch.service a commencé à démarrer
> â–‘â–‘ Defined-By: systemd
> â–‘â–‘ Support: https://www.debian.org/support
> â–‘â–‘
> ░░ L'unité (unit) fwlogwatch.service a commencé à démarrer.
> nov. 20 17:02:18 voxdeb sh[294164]: aborted
> nov. 20 17:02:18 voxdeb systemd[1]: fwlogwatch.service: Control process
> exited, code=exited, status=1/FAILURE
> â–‘â–‘ Subject: Unit process exited
> â–‘â–‘ Defined-By: systemd
> â–‘â–‘ Support: https://www.debian.org/support
> â–‘â–‘
> â–‘â–‘ An ExecStart= process belonging to unit fwlogwatch.service has exited.
> â–‘â–‘
> â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
> nov. 20 17:02:18 voxdeb systemd[1]: fwlogwatch.service: Failed with result
> 'exit-code'.
> â–‘â–‘ Subject: Unit failed
> â–‘â–‘ Defined-By: systemd
> â–‘â–‘ Support: https://www.debian.org/support
> â–‘â–‘
> â–‘â–‘ The unit fwlogwatch.service has entered the 'failed' state with result
> 'exit-code'.
> nov. 20 17:02:18 voxdeb systemd[1]: Failed to start fwlogwatch.service -
> Firewall log analyzer.
> ░░ Subject: L'unité (unit) fwlogwatch.service a échoué
> â–‘â–‘ Defined-By: systemd
> â–‘â–‘ Support: https://www.debian.org/support
> â–‘â–‘
> ░░ L'unité (unit) fwlogwatch.service a échoué, avec le résultat failed.
try to see if a reboot changes anything here : no more chances, still don't
start.
I'm puzzled here ????
