-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Solved. I got into the situation by accidentally trying to ftp ~xml files onto the same server rather that the other cluster node. I've been lucky to this point as I haven't botched a zone install. Typical implementation environment: networks not ready, not all ip addresses and host names not assigned; server hosts files and naming services incomplete; and we are the ones on the hooks for delivery on schedule. Just deleting the (now 0-sized) ~.xml files and their entries in the index did not work. Zoneadm would still report that the zone existed and they were in a poor state. A global search of *zone* from ./* pointed out some lock files in /tmp and zone-specific references under /var/...../OLD/ Don't which were the key, but deleting these files and a reboot of the server solved the issue.
Thanks for the reply, Mike Jerry Jelinek wrote: > > Could you tell us how your system state got corrupted? At this > point, since your system state is corrupted, you would have to > manually try to clean things up. The zone commands don't have any > built-in support for dealing with a corrupt system. If these file > got messed up because of manual editing maybe you could look at a > good system and try to manually edit the data back into a valid > configuration. Otherwise you probably need to delete everything > and start over. > > Good luck, Jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHKcnOLpC9yYHEK2ARAku7AJsGG5kD+xCf5uxfDmWSnzZc/i6mhwCgrIOB PmErOVfKADpWpeWA16l4x2c= =dhHo -----END PGP SIGNATURE-----
begin:vcard fn:Michael Webb n:Webb;Michael email;internet:[EMAIL PROTECTED] tel;work:210.387.1519 x-mozilla-html:TRUE version:2.1 end:vcard
_______________________________________________ zones-discuss mailing list email@example.com