[Logwatch] Logwatch 5.0-1 doesn't seem to like RedHat 6.2...

Patrick Salsbury salsbury@sculptors.com
Sat, 15 Nov 2003 06:29:24 -0800


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: message/rfc822

X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: logwatch@logwatch.org
Cc: salsbury
Subject: Logwatch 5.0-1 doesn't seem to like RedHat 6.2...
X-Image-Url: http://reality.sculptors.com/~salsbury/Gifs/patrick-salsbury_01-20-03_small.jpg
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I'm just going through my various Logwatch mails from the past few days and 
found an unexpected (and not-great) surprise. Logwatch reports from an old 
RedHat 6.2 box that I have started spewing errors and giving me 
ever-increasingly-large emails. 

The first one after the auto-upgrade (via autorpm) on Nov 12 on the RH6.2 
machine jumped frin 169,714 bytes (message 834, below) to an unseemly bloat of 
4,119,174 (msg 836) the next day, and has continued to grow to 5.74Mb and 7.53Mb in the 
following days. (messages 838 & 840, respectively). 

Note that the odd-numbered files, which are from a RedHat8.0 box stay 
relatively the same, as do some from a RH9.0 box (not shown here). 

>lh ~/Mail/Logwatch/
total 95116
- -rw-------    1 salsbury users      178844 Nov 15 04:02 841
- -rw-------    1 salsbury users     7536374 Nov 14 04:16 840
- -rw-------    1 salsbury users      201223 Nov 14 04:02 839
- -rw-------    1 salsbury users     5743069 Nov 13 04:27 838
- -rw-------    1 salsbury users      185806 Nov 13 04:02 837
- -rw-------    1 salsbury users     4119174 Nov 12 04:25 836
- -rw-------    1 salsbury users      285418 Nov 12 04:02 835
- -rw-------    1 salsbury users      169714 Nov 11 04:18 834
- -rw-------    1 salsbury users      569004 Nov 11 04:02 833


"What could be causing this bloaty goodness?", I hear you asking yourself...

Here's what I see in the Logwatch report:

################### LogWatch 5.0 (11/10/03) #################### 
       Processing Initiated: Wed Nov 12 04:07:49 2003
       Date Range Processed: yesterday
     Detail Level of Output: 0
          Logfiles for Host: rh6.sculptors.com
 ################################################################ 

 --------------------- AutoRPM Begin ------------------------ 

[ UPGRADED] logwatch: 4.3.2-1 -> 5.0-1

 ---------------------- AutoRPM End ------------------------- 


 --------------------- httpd Begin ------------------------ 

Use of uninitialized value at /etc/log.d/scripts/services/http line 121, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 127, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 137, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 164, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 168, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 175, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 176, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 176, <STDIN> chunk 1.
Use of uninitialized value at /etc/log.d/scripts/services/http line 176, <STDIN> chunk 1.
	[...tens of thousands of lines like this deleted...]

	In fact, there really are a hell of a lot of these lines. Most of 'em, 
as it turns out:

>wc -l ~/Mail/Logwatch/836
  44519 /home/salsbury/Mail/Logwatch/836
>g 'Use of uninitialized value at' ~/Mail/Logwatch/836 | wc -l
  44188

>wc -l ~/Mail/Logwatch/838
  61962 /home/salsbury/Mail/Logwatch/838
>g 'Use of uninitialized value at' ~/Mail/Logwatch/838 | wc -l
  61634

>wc -l ~/Mail/Logwatch/840
  81231 /home/salsbury/Mail/Logwatch/840
>g 'Use of uninitialized value at' ~/Mail/Logwatch/840 | wc -l
  80900


	Eventually, it does finish, though, and even gives me the fortune at 
the end. :-) I see this stuff near the very end of the report:

bootstrap(6:22am) 3092>tail -60 ~/Mail/Logwatch/836 | head -20
Use of reserved word "our" is deprecated at /etc/log.d//lib/Logwatch.pm line
83. Bareword "our" not allowed while "strict subs" in use at /etc/log.d//lib/
Logwatch.pm line 83. Unquoted string "our" may clash with future reserved word
at /etc/log.d//lib/Logwatch.pm line 83. Array found where operator expected at /
etc/log.d//lib/Logwatch.pm line 83, at end of line
        (Do you need to predeclare our?)
Global symbol "@ISA" requires explicit package name at /etc/log.d//lib/
Logwatch.pm line 83. Use of reserved word "our" is deprecated at /etc/log.d//
lib/Logwatch.pm line 84. Bareword "our" not allowed while "strict subs" in use
at /etc/log.d//lib/Logwatch.pm line 84. Unquoted string "our" may clash with
future reserved word at /etc/log.d//lib/Logwatch.pm line 84. Array found where
operator expected at /etc/log.d//lib/Logwatch.pm line 84, at end of line
        (Do you need to predeclare our?)
	[...]

	Is this an incompatibility with Perl? Or maybe a module therein? 

	Figured I'd post a heads-up, in case no one else has seen it. No idea 
how it behaves on the RH7.x series, but I might be able to check that, as I 
think I've got it on a notebook or two around here. 

	Any ideas? (Other than the obvious "Upgrade that creaky old machine!", 
that is! ;^)  ) That's already a work in progress. But is there anything I can 
do for this version? 


- -- 
Pat
	   ___________________Think For Yourself____________________
	 Patrick G. Salsbury - http://reality.sculptors.com/~salsbury/
      Interested in learning or teaching about the future? Check out the
    future-studies mailing list at http://reality.sculptors.com/lists.html
	   ---------------------------------------------------------
Eris is not hateful or malicious.  But she is mischievous, and does
get a little bitchy at times.			--The Principia Discordia


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Don't know what GPG is? Check http://www.pgpi.org/

iD8DBQE/tjhEHJeVqQarW2cRAtDiAKCapSDNo5VYsGsfbIsv+gs41IlY2wCdH+xs
lYnglksKPR1Z1wz8CcvcOC0=
=jaTO
-----END PGP SIGNATURE-----