Oracle Solaris System Administration (MOSC)

MOSC Banner

Why isn't svc:/system/zones:default starting all my non-global zones that have autoboot=true?

edited Oct 30, 2015 5:27PM in Oracle Solaris System Administration (MOSC) 2 commentsAnswered ✓

I have a Solaris 11.2.15.4.0 system, with 6 non-global zones configured, and all of them have autoboot=true. However, 2 of the 6 zones don't boot automatically, and stay in the "installed" state until I boot them manually.

In /var/adm/messages, shortly after boot, I get these messages:

Oct 27 19:51:36 <hostname> svc.startd[13]: [ID 122153 daemon.warning] svc:/system/zones:default: Method or service exit timed out.  Killing contract 159.

Oct 27 19:51:36 <hostname> svc.startd[13]: [ID 636263 daemon.warning] svc:/system/zones:default: Method "/lib/svc/method/svc-zones start" failed due to signal KILL.

Upon investigation, the /var/svc/log/system-zones:default.log file shows the following errors as well:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center