I have a Redhat 7.3 system that has 0 byte logs for Secure, messages, spooler xferlog, maillog, bootlog. The files are their, just 0 bytes. The logs are not getting updated when I log in for example or the server is restarted. File date & size does not change. When I touch the log, it does update by the way.

I don't think it's been comprised yet but I welcome any ideas or tests I should perform.

Is syslog(d) running? :
ps aux | grep syslog
service syslog status

that explains my logs. Now I have to figure out a kernel panic.

Thanks.

Having logging get mysteriously turned off AND kernel panics should raise a *major* red flag. Short of complete log deletion, it's suggestive of someone was attempting to avoid detection by subverting logging. The kernel panics can be a side-effect of exploitation or a buggy rootkit.

You should check roots bash history (just type "history" as root) and look for any commands that might have turn off logging. For the panics, first check the system logs to see what the actual panic message is, then if the cause still isn't clear try running chkrootkit or preferably rootkit hunter (newer versions of the suckit rootkit have the ability to avoid detection by chkrookit).

It's entirely possible that it's caused by something benign, but it definitely isn't something to take lightly until you are absolutely sure of the cause.

History command showed commands that all looked good.

Very strange. I did run the check for root kits already and did not find anything. Any thing else that I should look for?

You might want to try skdetect and kern_check.c, otherwise I'd focus on trying to figure out the cause of the panics (what is the actual panic message?).