I just created 9 whole root local zones across 4 physical boxes. On 3
of them /var/adm/messages was never created and syslogd doesn't start.
Then on some nfs client was never started and svcadm doesn't seem to
start the service...no error in svc log.
This has only happened with s10u3. Are t
Michael Barrett wrote:
I just created 9 whole root local zones across 4 physical boxes. On 3
of them /var/adm/messages was never created and syslogd doesn't start.
Does svcs -x say anything about system-log service ?
Then on some nfs client was never started and svcadm doesn't seem to
star
Just your normal stuff but no nfs or syslog. I do see that
sysidtool:net is offline. I'm guessing this is my issue.
svc:/system/sysidtool:net (sysidtool)
State: offline since Thu May 03 06:39:14 2007
Reason: Start method is running.
See: http://sun.com/msg/SMF-8000-C4
See: sysidtool(1M)
Did you apply the packaging and patching patches and the KU patch?
Michael Barrett wrote:
I just created 9 whole root local zones across 4 physical boxes. On 3
of them /var/adm/messages was never created and syslogd doesn't start.
Then on some nfs client was never started and svcadm doesn't s
* Michael Barrett <[EMAIL PROTECTED]> [2007-05-09 08:43]:
> Just your normal stuff but no nfs or syslog. I do see that
> sysidtool:net is offline. I'm guessing this is my issue.
>
> svc:/system/sysidtool:net (sysidtool)
> State: offline since Thu May 03 06:39:14 2007
> Reason: Start method is
That was it. zlogin -C and there I was at the system id questions.
Interesting that a zone will boot up to running status, allow you to
login and tell you it's in run level 3 without sysid completed.
Stephen Hahn wrote:
* Michael Barrett <[EMAIL PROTECTED]> [2007-05-09 08:43]:
Just your nor
On Wed 09 May 2007 at 09:55AM, Stephen Hahn wrote:
> * Michael Barrett <[EMAIL PROTECTED]> [2007-05-09 08:43]:
> > Just your normal stuff but no nfs or syslog. I do see that
> > sysidtool:net is offline. I'm guessing this is my issue.
> >
> > svc:/system/sysidtool:net (sysidtool)
> > State: of
The first thing I would comment on is :
- If the sysidcfg has failed due to some reason, just fail that zone
and make zlogin -C mandatory. Maybe give a new state "unsysconfigured"
or something to such zones.
The second thing is "prevalidation" of the sysidcfg inputs given.
- If there are so
Another idea: print a message to the global zone's console:
[WARNING: Zone has booted but lacks system identity. Log into the
zone's console to complete configuration]
Dan Price wrote:
On Wed 09 May 2007 at 09:55AM, Stephen Hahn wrote:
* Michael Barrett <[EMAIL PROTECTED]> [2007-05-09 08:4
For the archives: See the FAQ:
Q: I created a zone and booted it, but it doesn't work. What should I do?
http://opensolaris.org/os/community/zones/faq/#ts_sysid
Michael Barrett wrote:
Just your normal stuff but no nfs or syslog. I do see that
sysidtool:net is offline. I'm guessing this is my
These are perfect and would have solved my use cases.
The only thing I would add is if you do still allow a zone to boot
without system identication, re-direct the zlogin. I'm grablling if I
would ever want to login to a zone that has not completed it's system
identification. To that point,
11 matches
Mail list logo
