/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Backup Configure

Appliance reboots/resets unexpectedly

SUMMARY

In certain cases, the ipmiutil watchdog timer service has been left enabled and can produce unexpected behavior such as a hard reset of the DPU.

ISSUE

Appliance reboots/resets without reason and you may see the following when checking the BMC event log.

[root@Recovery-933S ~]# ipmiutil sel -e
ipmiutil ver 2.97
isel: version 2.97
-- BMC version 1.86, IPMI version 2.0
SEL Ver 0 Support 03, Size = 512 records (Used=6, Free=506)
RecId Date/Time_______ SEV Src_ Evt_Type___ Sens# Evt_detail - Trig [Evt_data]
0001 05/05/16 00:29:31 MAJ BMC  Watchdog_2 #ca Timer interrupt 6f [c8 04 ff]
0002 05/05/16 00:29:32 CRT BMC  Watchdog_2 #ca Hard Reset action 6f [c1 04 ff]
0003 05/05/16 00:36:30 MAJ BMC  Watchdog_2 #ca Timer interrupt 6f [c8 04 ff]
0004 05/05/16 00:36:31 CRT BMC  Watchdog_2 #ca Hard Reset action 6f [c1 04 ff]
0005 05/05/16 00:44:31 MAJ BMC  Watchdog_2 #ca Timer interrupt 6f [c8 04 ff]
0006 05/05/16 00:44:32 CRT BMC  Watchdog_2 #ca Hard Reset action 6f [c1 04 ff]
ipmiutil sel, completed successfully

RESOLUTION

Perform the following to first verify that the watchdog timer service is enabled.

[root@Recovery-933S ~]# service ipmiutil_wdt status
ipmiutil ver 2.97
iwdt ver 2.97
-- BMC version 1.86, IPMI version 2.0
wdt data: 04 01 00 00 84 03 84 03
Watchdog timer is stopped for use with SMS/OS. Logging
               pretimeout is 0 seconds, pre-action is None
               timeout is 90 seconds, counter is 90 seconds
               action is Hard Reset

ipmiutil wdt, completed successfully
ipmiutil_wdt is running...

Once you've verified that the ipmiutil_wdt service is running as indicated by the output above, stop and disable the service from running at boot by issuing the following commands.

[root@Recovery-933S ~]# service ipmiutil_wdt stop
Stopping /usr/bin/ipmiutil wdt:

[root@Recovery-933S ~]# chkconfig ipmiutil_wdt off

Finally, do verify that the service is stopped considering the init script does not output the results of the stop argument.

[root@Recovery-933S ~]# service ipmiutil_wdt status
ipmiutil ver 2.97
iwdt ver 2.97
-- BMC version 1.86 IPMI version 2.0
wdt data: 01 00 1e 00 b0 04 b0 04
Watchdog timer is stopped for use with BIOS FRB2. Logging
               pretimeout is 30 seconds, pre-action is None
               timeout is 120 seconds, counter is 120 seconds
               action is No action

ipmiutil wdt, completed successfully
ipmiutil_wdt is stopped

CAUSE

In certain cases, the ipmiutil watchdog timer service has been left enabled and can produce unexpected behavior such as a hard reset of the DPU.