Hello Michel ^^)

Le 21/11/2024 à 08:33, Michel Verdier a écrit :
On 2024-11-20, Jean-François Bachelet wrote:

I might be reading this wrong, but the "ExecStart" command is a shell script
which basically says "if the $START_DAEMON variable does not equal 'true',
then echo 'aborted' and stop". Given you get sh printing the word 'aborted',
I think you're reading that branch.
Did you set "START_DAEMON=true" in /etc/default/fwlogwatch or similar?
there is no such stuff in the confs...

I reply to you on debian-user-french yesterday

fwlogwatch.service use /lib/systemd/system/fwlogwatch.service
which use conf file /etc/default/fwlogwatch
and if START_DAEMON is not "true" it does exit 1
So you just need to put in /etc/default/fwlogwatch
START_DAEMON='true'

Did you check the right file /etc/default/fwlogwatch ? What version do
you have ? Provide us :
dpkg -l fwlogwatch

~/Bureau$ dpkg -l fwlogwatch

Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| 
État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom            Version      Architecture Description
+++-==============-============-============-=================================
ii  fwlogwatch     1.4-4        amd64        Firewall log analyzer

apt says it it upto date.


here is what the cron daily conf says for it :
[..]
as said, /etc/fwlogwatch.config is all commented out except for the pid
file.

I don't know where you find "/etc/fwlogwatch.config"
sorry, mistaping ;) it's in '/etc/fwlogwatch/fwlogwatch.config'

in this script I found :
CONFIG=/etc/default/fwlogwatch

oups, the only place I'vee not checked... you're right it was there at false, dunno why... changed it for 'true'.

and still crashing...

looking at the 'systemctl --failed' log it appears that it lacks the '/var/log/messages' directory, another thing that has not been created at installation of fwlogwatch...

IMHO that should be corrected in the installer...

BTW, now its up and running. :) let's see if I get messages from it ^^)

Thanks everyone :)

Jeff

Reply via email to