Re: [Bacula-users] Logwatch report

2022-07-06 Thread Eric Bollengier via Bacula-users

Hello Gestio,

On 6/23/22 11:25, GestiĆ³ Servidors wrote:

Hello,

I have copied scripts from "logwatch" bacula source folder, but when I run
"logwatch --debug High --service bacula --output stdout", logwatch doesn't
run fine because it can't locate "Logwatch.pm". It seems logwatch process
gets wells all logs files (I log some servers in some different files), but
when all files concatenated go by the perl pipe, it fails in this line:

Processing Service: bacula ( cat /var/cache/logwatch/logwatch.dSY3aBHv/bacula
|  /usr/bin/perl /etc/logwatch/scripts/shared/applybaculadate ''
|/usr/bin/perl /etc/logwatch/scripts/services/bacula) 2>&1


If I run this line manually, I get this error message:

Can't locate Logwatch.pm in @INC (you may need to install the Logwatch
module)


I believe that you need to install the logwatch package on your system.
Scripts are installed, but the base software is not.

Hope it helps!

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Logwatch report

2022-06-23 Thread GestiĆ³ Servidors
Hello,

I have copied scripts from "logwatch" bacula source folder, but when I run 
"logwatch --debug High --service bacula --output stdout", logwatch doesn't run 
fine because it can't locate "Logwatch.pm". It seems logwatch process gets 
wells all logs files (I log some servers in some different files), but when all 
files concatenated go by the perl pipe, it fails in this line:

Processing Service: bacula
( cat /var/cache/logwatch/logwatch.dSY3aBHv/bacula  |  /usr/bin/perl 
/etc/logwatch/scripts/shared/applybaculadate '' |/usr/bin/perl 
/etc/logwatch/scripts/services/bacula) 2>&1


If I run this line manually, I get this error message:

Can't locate Logwatch.pm in @INC (you may need to install the Logwatch module) 
(@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 
/usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 
/usr/share/perl5) at /etc/logwatch/scripts/shared/applybaculadate line 21.
BEGIN failed--compilation aborted at 
/etc/logwatch/scripts/shared/applybaculadate line 21.

I have copied logwatch scripts doing the "README" explanation (I have installed 
Bacula-11.0.6 from source files):

For manual install copy the files as indicated below:
cp -p scripts/logwatch/bacula /etc/log.d/scripts/services/bacula
cp -p scripts/logwatch/applybacula /etc/log.d/scripts/shared/applybaculadate
cp -p scripts/logwatch/logfile.bacula.conf /etc/log.d/conf/logfiles/bacula.conf
cp -p scripts/logwatch/services.bacula.conf /etc/log.d/conf/services/bacula.conf
chmod 755 /etc/log.d/scripts/services/bacula
chmod 755 /etc/log.d/scripts/shared/applybaculadate
chmod 644 /etc/log.d/conf/logfiles/bacula.conf
chmod 644 /etc/log.d/conf/services/bacula.conf

Why am I getting this error and why am not getting logwatch bacula report?

Thanks.

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] logwatch

2009-12-15 Thread Craig White
On Mon, 2009-12-14 at 08:22 -0700, Craig White wrote:
 A relatively new bacula 3.0.3 installation on CentOS 5
 
 I get an error every day from logwatch...
 
 
 
 obviously generated by
 cron...run-parts /etc/cron.daily
 
 
 /etc/cron.daily/0logwatch:
 
 Cannot find shared script applybaculadate
 
 Now I can find the script...
 /usr/src/redhat/BUILD/bacula-3.0.3/scripts/logwatch/applybaculadate
 
 and I can see that...
 
 # cat /etc/logwatch/conf/services/bacula.conf
 Title = bacula
 
 # Which logfile group...
 LogFile = bacula
 
 *ApplyBaculaDate =
 
 What is it that I am supposed to do?

with help from Steve Ellis...

apparently the source rpm needs to do the following...

mkdir /etc/logwatch/scripts/shared
cp \
/usr/src/redhat/BUILD/bacula-3.0.3/scripts/logwatch/applybaculadate \
/etc/logwatch/scripts/shared
chmod 755 /etc/logwatch/scripts/shared/applybaculadate

and a terse bacula log is included with logwatch or otherwise, generates
an error.

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] logwatch

2009-12-14 Thread Craig White
A relatively new bacula 3.0.3 installation on CentOS 5

I get an error every day from logwatch...



obviously generated by
cron...run-parts /etc/cron.daily


/etc/cron.daily/0logwatch:

Cannot find shared script applybaculadate

Now I can find the script...
/usr/src/redhat/BUILD/bacula-3.0.3/scripts/logwatch/applybaculadate

and I can see that...

# cat /etc/logwatch/conf/services/bacula.conf
Title = bacula

# Which logfile group...
LogFile = bacula

*ApplyBaculaDate =

What is it that I am supposed to do?

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] logwatch

2009-12-14 Thread Steve Ellis
On 12/14/2009 7:22 AM, Craig White wrote:
 A relatively new bacula 3.0.3 installation on CentOS 5

 I get an error every day from logwatch...

...
 Cannot find shared script applybaculadate

...
 *ApplyBaculaDate =

 What is it that I am supposed to do?

 Craig


I had the same error when I switched back to the Fedora supplied RPM 
after upgrading to Fedora 12.  For Fedora, there is an updated set of 
bacula RPMs in updates-testing that fixes the problem.  With the updated 
bacula-director-common RPM, applybaculadate is in 
/etc/logwatch/scripts/shared (and the .conf file still looks the same as 
yours).  If you can't get an updated RPM, copying the script to that 
location may fix the problem you are having.

Hope that helps,
-se

--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users