cc_skavenger,
Thanks for your help.
Eth0 is LAN. There are 3 servers on this LAN: SME for website & e-mail (this is the one with the problem), SME for Internet access, Windows 2003 for Domain. All have DHCP disabled (verified).
I do not get any of these denylog messages in the logfile of my second SME server. The server in question though logs them back at least as far as March 15th (last log), but I didn't start having the lockups until about a week ago, so I may be dealing with more than one issue.
Do you know of anything else that uses those ports for anything other than DHCP (since there aren't any DHCP servers on my LAN)?
If it isn't the denylog entries locking the server up, do you know how to track down what it is? The server screen is black and unresponsive when it freezes. A reboot takes care of it, but then it freezes again the next night (last log entry listed in "messages" shows 3:05:48 and the last thing listed is the denylog entry as mentioned in original post). Do you know if there is a log file, command, or utility that might give an indication of what the issue might be?
To further "cloud" the issue (at least for me) ...
Without filling the forum with the entire log (I can if needed add more), does the below excerpt indicate that the server was rebooted at 3:06 AM (following a denylog listing)?
Apr 24 03:05:19 webserver kernel: denylog:IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0e:7f:d6:9d:d8:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=64 ID=11816 PROTO=UDP SPT=68 DPT=67 LEN=556
Apr 24 03:06:27 webserver syslogd 1.4.1: restart.
Apr 24 03:06:27 webserver syslog: syslogd startup succeeded
... The log continues with a long listing of restarted services ... seemingly corresponding to a server reboot.
This corresponds with the time that the server seems to be freezing (as indicated by last listing in messages and antivir logs - as well as the antivirus scan report normally mailed to admin account is not received), but cron log lists other things occurring at incremental times after that. Am I correct that the cron log lists what HAS ran, not what is SUPPOSED to have run? I had thought I had traced it to a clam scan that runs at this time (and it has frozen on manual scans before), but with the seemingly conflicting logs, I’m no longer sure (as well, some nights it completes the scan and the server isn't frozen the next morning).
Thanks again. Any further direction would be appreciated.