On 12/8/16 12:07 , the outsider wrote: > Thanks, but i lost my patience and rebooted the whole server. > > Took some time and a forced shutdown was needed but now everything is ok. > I will keep your answer for future use!
If you do end up in this state and a need to reboot, I'd recommend forcing a crash dump if possible. This can be doing by injecting an nmi over ipmitool (ipmitool chassis power diag) or reboot -d. That way we may be able to make forward progress. Robert > -----Oorspronkelijk bericht----- > Van: Robert Mustacchi [mailto:[email protected]] > Verzonden: donderdag 8 december 2016 18:12 > Aan: [email protected] > Onderwerp: Re: [smartos-discuss] UUID is already not 'running' (currently: > shutting_down) > > On 12/8/16 9:07 , the outsider wrote: >> Hi, >> >> that didn’t work unfortunately. >> >> >> >> Also vmadm stop UUID -F did nothing. >> >> >> >> The zone is a plain SmartOS zone. No special VM. >> >> >> >> Prstat -z UUID shows: >> >> PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP >> >> 8405 root 15M 9568K sleep 1 0 0:00:28 0.0% smbd/2 >> >> 4206 root 0K 0K sleep 60 - 0:00:00 0.0% zsched/1 >> >> >> >> And cannot kill both processes. (tried pkill from global zone) > > If you can't kill them, that means that they're stuck waiting for something > to happen. Most likely zsched is blocked on smbd. What you should do next is > run the following: > > mdb -ke '0t8405::pid2proc | ::walk thread | ::findstack -v' > > Robert > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
