Nexus 5K rebooting continuously

r.shummoogum · ‎11-26-2010

I have a Nexus 5K that is continuously rebooting in a loop with the following error.

How can I get out of this? Thanks

Nov 24 10:23:41 %SYSMGR-2-SERVICE_CRASHED Service "syslogd" (PID 4028) hasn't caught signal 11 (core will be saved).

Nov 24 10:23:45 %SYSMGR-2-LAST_CORE_BASIC_TRACE core_client_main: PID 4740 with

message filename = 0x101_syslogd_log.4028.tar.gz

Shutdown Ports..

writing reset reason 16, syslogd hap reset

INIT: Sending pNov 24 10:23:50 %STP-2-PROFILE SIGNAL Handler:: crossed (0 secs),

elapsed (0 secs 2 usecs), usr (0 secs 0 usecs), sys (0 secs 0 usecs) :

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "netstack" (PID 4245) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "altos" (PID 4135) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vshd" (PID 4064) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vlan_mgr" (PID 4153) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vdc_mgr" (PID 4111) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 4143) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "u6rib" (PID 4142) is forced exit.

Nov 24 10:23:51 %TTYD-2-TTYD_ERROR TTYD Error ttyd bad select

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 4148) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "AAA Daemon" (PID 4138) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Tacacs Daemon" (PID 4166) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "licmgr" (PID 4068) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 4136) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 4137) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "smm" (PID 4065) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 4116) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "npacl" (PID 4121) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "m2rib" (PID 4152) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "l3vm" (PID 4140) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "igmp" (PID 4291) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 4244) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "adjmgr" (PID 4167) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 4289) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 4069) is forced exit.

Nov 24 10:23:51 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "eth_dstats" (PID 4129)is forced exit.

Nov 24 10:23:52 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "arp" (PID 4243) is forced exit.

INIT: Sending processes the KILL signal

Unexporting directories for NFS kernel daemon...done.

Stopping NFS kernel daemon: rpc.mountd rpc.nfsd done.

Unexporting directories for NFS kernel daemon...done.

Stopping portmap daemon: portmap.

Stopping kernel log daemon: klogd.

Sending all processes the TERM signal... done.

Sending all processes the KILL signal... done.

Unmounting remote filesystems... done.

Deactivating swap...umount: none busy - remounted read-only done.

Unmounting local filesystems...umount: none busy - remounted read-only done.

mount: you must specify the filesystem type

Starting reboot command: reboot

Rebooting...

Restarting system.

r.shummoogum · ‎12-06-2010

The problem is now fixed after some trial and error.

But I still find this hard to believe.

I had an entry in the config where I was referring to the log server as xxxxx and xxxxx could not be be resolved.

logging server xxxxx

So in other words if xxxxx was defined using the ip host command or could be resolved by dns then no issue.

Lsimancek_2 · ‎02-16-2011

I have a nexus 5548 that just started doing this last night. I had it on our test bench, wrote off the config then reload it and it won't stop. Did you figure out this on yourself or did Cisco help you? if so did they give you any other ideas on what could be wrong? I'm not getting very far with TAC right now ..

r.shummoogum · ‎02-16-2011

I figure it out myself after I compared the bad config with a working config that I had saved on the flash:

Can you post or PM the config.

Lsimancek_2 · ‎02-16-2011

Cisco just told me this:

We are seeing a bug in NX-OS with 5.0.2.N1.1 release. The issue is fixed in

5.0.2.N2.1 release.

Following is the bug id:

CSCtj71171 Nexus 5k crash boot loop during upgrade to 5.0(2)N1(1)

Symptom:

* N5K stuck in a boot loop

* The service "port-profile" is causing the reload.

Conditions:

Found Banner motd not being left justified. Certain regular expressions on the first character of the banner will also trigger this defect.

So far the break sequence hasn't actually "broke" the loop yet so lets see if the instrucions they sent me can. I'll post results soon.

As a side not - are you running a 5548? have you seen any other problems?

r.shummoogum · ‎02-16-2011

Mine was on 5520 running version 5.0(2)N1(1).

I will be deploying 5548 in March so I will keep that in mind.

Lsimancek_2 · ‎02-17-2011

For follow up. The break sequence needed to executed at the right time, "Checkeing all filesystems.... done loading system sfotware" - Crtl^R. Then I erased the config, and everything worked fine. It was the bud ID you found, CSCtj71171, that cause this. Thanks!