Unknown messages in LogWatch output

[Eric Leung_2]

Dear Experts,

There are thousand of lines - "Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 34" in the LogWatch output of my Linux server. What is the meaning of these lines? Should and can I do something to eliminate them?

I am using Red Hat Linux ES 3. Automount service is started to handle several hundreds mount points from 100+ servers which are at distributed locations.

Thanks.

Please see the output below:

################### LogWatch 4.3.2 (02/18/03) ####################
Processing Initiated: Tue Oct 4 04:02:05 2005
Date Range Processed: yesterday
Detail Level of Output: 0
Logfiles for Host: ux21itb
################################################################

--------------------- Automount Begin ------------------------

Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 34, line 2.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 34, line 2.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 34, line 5.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 34, line 8.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 11.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 14.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 17.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 20.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 23.
Use of uninitialized value in hash element at /etc/log.d/scripts/services/automount line 28, line 26

[njia_1]

Hi

Looks like it is automount related. Stop automount service for few hours if possible to see if those messages go away. If it does, then check your automount configuration.

thanks

[Ivan Ferreira]

It seems that there is a problem with the script used to check the automount service.

If you don't use automount, you can disable the verification of that service configuring the "Service =" option in logwatch.conf.