I am Running Centos 4.4 on a Poweredge box 2600
Aug 8th 7.30 am, the server had a problem when all the
available disk space had gone, there should of been
180 Gig.
Investigating the logs the last activity was at 04.02
in the morning with this:
**********************************
Aug 8 04:02:05 localhost nmbd[3799]: [2007/08/08
04:02:05, 0] nmbd/nmbd.crocess(542)
Aug 8 04:02:05 localhost nmbd[3799]: Got SIGHUP
dumping debug info.
Aug 8 04:02:05 localhost nmbd[3799]: [2007/08/08
04:02:05, 0]
nmbd/nmbd_workgroupdb.c:dump_workgroups(284)
Aug 8 04:02:05 localhost nmbd[3799]: dump_workgroups()
Aug 8 04:02:05 localhost nmbd[3799]: dump workgroup on
subnet 10.0.0.115: netmask= 255.255.255.0:
Aug 8 04:02:05 localhost nmbd[3799]: WORKGROUP(1)
current master browser = NETPILOT
Aug 8 04:02:05 localhost nmbd[3799]: LINUXSERVER
40019a03 (LinuxServer)
Aug 8 04:02:05 localhost nmbd[3799]: NETPILOT 400c9a03
(Samba 2.0.6)
Aug 8 08:41:01 localhost gdm(pam_unix)[4568]: session
opened for user kingsmead by (uid=0)
Aug 8 08:41:02 localhost gconfd (kingsmead-14752):
starting (version 2.8.1), pid 14752 user 'kingsmead'
Aug 8 08:41:02 localhost gconfd (kingsmead-14752):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a
read-only configuration source at position 0
Aug 8 08:41:02 localhost gconfd (kingsmead-14752):
Resolved address
"xml:readwrite:/home/kingsmead/.gconf" to a writable
configuration source at position 1
Aug 8 08:41:02 localhost gconfd (kingsmead-14752):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a
read-only configuration source at position 2
Aug 8 08:41:09 localhost gconfd (kingsmead-14752):
Resolved address
"xml:readwrite:/home/kingsmead/.gconf" to a writable
configuration source at position 0
************************************************
A reboot was successful and the disk space was back to
normal, I had also notice before reboot that on the
system monitor the /dev/mapper/VolGroup00-logVol00 was
reading 98% and system activity was going crazy.
Since that reboot all system activity has been normal
and seems stable. There was no loss of data.
Looking at the logs again there is still the nmbd
dump_workgroups () message at 4 am, but is this normal
log rotation? or is there a problem with Samba
configuration ?
Thanks to anyone who can help throw some light on
this, I see there has been quite a few question about
this ( nmbd dump_workgroups () messages at 4 am) .
Thanks in advance for any help
