The link to the Launchpad entry, which also features a fix: https://bugs.launchpad.net/nexenta/+bug/347937

J.Blun: what was the fix in your case? Importing the manifest, or editing to remove the exit code from the SVC method dont seem to help.

~Anil

Anil, I did exactly what was reported by chrol in the old launchpad bugtracker:

add

"[ `zonename` = global ] || sleep 3600 & exit 0"

after after ". /lib/svc/share/smf_include.sh" in /lib/svc/method/svc-syseventd, do a

dpkg-reconfigure sunwcsd

and import the sysevent.xml again with

svccfg import /var/svc/manifest/system/sysevent.xml

That fixed it.

j. blun wrote:

Anil, I did exactly what was reported by chrol in the old launchpad bugtracker:

add

[...]

after after ". /lib/svc/share/smf_include.sh" in /lib/svc/method/svc-syseventd, do a

[...]

and import the sysevent.xml again with

[...]

That fixed it.

I have to admit I tried to do it on a RC3 without more success than Anil, while it working when on RC2 (on the same machine). So my zone is broken again. Oh my!

Adding this link only to complete the list of what need to be done to get zones working again in NCP3-RC3:

http://www.nexenta.org/issues/203#note-5

Fix should be easy. And fixing zones would be a real step forward in nexenta acceptance ;-)

Hi,

This is fixed with NCP 3.0.1

Once a zone is setup, you need to run dpkg-reconfigure sunwcsd, and reboot. The zlogin issue to zones has been fixed as well.

~Anil

This bug was reintroduced by the latest upgrade in sunwcsd Version 5.11.134-30-5-0!

We have to add this again in lib/svc/method/svc-syseventd:

[ `zonename` = global ] || sleep 3600 & exit 0"

Please fix it!