Server rebooting frequently : Redhat 7

Hi,
I have a production server rebooting frequently. I am unable to find the exact cause of reboot.

I will attach dmesg output.

Suspected messages causing reboot...

1. libceph: module verification failed: signature and/or required key missing - tainting kernel

2. systemd-journal[287]: Runtime journal is using 8.0M (max 4.0G, leaving 4.0G of free 58.9G, current limit 4.0G).

3. Nov 16 03:36:02 NVMBD1CII030V01 systemd: Failed to mark scope session-21839.scope as abandoned : Stale file handle.
Nov 16 03:36:02 NVMBD1CII030V01 systemd: Failed to mark scope session-21838.scope as abandoned : Stale file handle.

4. Nov 20 13:51:10 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2010" x-info="http://www.rsyslog.com"] start
Nov 21 08:54:17 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2012" x-info="http://www.rsyslog.com"] start
Nov 21 10:41:10 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2024" x-info="http://www.rsyslog.com"] start
Nov 21 11:59:53 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2017" x-info="http://www.rsyslog.com"] start
Nov 21 14:11:55 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2028" x-info="http://www.rsyslog.com"] start
Nov 21 14:23:50 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2028" x-info="http://www.rsyslog.com"] exiting on signal 15.
Nov 21 14:26:17 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2042" x-info="http://www.rsyslog.com"] start
Nov 21 15:45:15 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2031" x-info="http://www.rsyslog.com"] start

I have not worked on redhat 7. Is this to do with systemd??
Is any other information required?

Originally Posted by amit.kanade1983 Hi, I have a production server rebooting frequently. I am unable to find the exact cause of reboot. I will attach dmesg output. Suspected messages causing reboot... 1. libceph: module verification failed: signature and/or required key missing - tainting kernel 2. systemd-journal[287]: Runtime journal is using 8.0M (max 4.0G, leaving 4.0G of free 58.9G, current limit 4.0G). 3. Nov 16 03:36:02 NVMBD1CII030V01 systemd: Failed to mark scope session-21839.scope as abandoned : Stale file handle. 4. Nov 20 13:51:10 NVMBD1CII030V01 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="2010" x-info="http://www.rsyslog.com"] start I have not worked on redhat 7. Is this to do with systemd?? Is any other information required?

There is a LOT of information you didn't include. Dmesg output is near meaningless in this context.

If you tried to look anything up, you'd have found that two of the four errors you posted are listed on Red Hat's knowledgebase as known issues, for which patches have been issued. Since you are using RHEL7, you can CALL RED HAT SUPPORT, and they can walk you through doing a system trace/dump, and get you the patches you need. However, unless you are PAYING FOR RHEL, you WILL NOT get these patches.

Short answer: yes, it's systemd related, but it's been fixed. Since you're paying for RHEL, you can get the fix from Red Hat.

Originally Posted by TB0ne There is a LOT of information you didn't include.

Can you let me know what info I did not include?

i do not have redhat supp in our environment and won't be getting it anytime sooner.
Also this is a guest on ESXi. I observed today caps and scroll leds blinking together.
when I
A google search yielded reason as kernel panic. how to debug a kernel panic?
I am unable to figure out how/where to start. any help in this regard would be appreciated.

Originally Posted by amit.kanade1983 Can you let me know what info I did not include?

Again, as said before, the system logs.

i do not have redhat supp in our environment and won't be getting it anytime sooner.

Then you are NOT going to get it fixed. As was explained to you, this is related to a patch released by Red Hat...that you WILL NOT GET unless you PAY FOR RED HAT. Simple...pay for Red Hat, or don't use it.

Also this is a guest on ESXi.

..which makes no difference at all...

I observed today caps and scroll leds blinking together.

...because the system crashed.

when I A google search yielded reason as kernel panic. how to debug a kernel panic?

As said, you look at the system logs, and determine the cause. However, as has been explained to you, the cause (in your case), is a system bug. One that has been patched for users that PAY FOR RHEL, as you should.

I am unable to figure out how/where to start. any help in this regard would be appreciated.

As said before, you start by paying for Red Hat, and applying the patch they released to fix this. And if you STILL have problems, you call Red Hat support, since you're paying for it then.

Otherwise, you can load CentOS for free, and get the patch. But if you insist on using RHEL, then pay for it.