I’ll give that a go and report back. I’m thinking I don’t know enough about the Smartos internals to make immediate progress so I’ll need to do some ferreting before reporting back.
Gareth On 30 May 2018 at 13:58:31, Mike Gerdts ([email protected]) wrote: > I'm not sure what is going on. What I can offer now are some hints about > how you can debug this. > > "nictagadm list" can be used to show which nic tags the global zone knows > about. You should verify that it shows the "dmz" tag. > > The zone's vnics are created by the code in > /usr/lib/brand/jcommon/statechange. A brand hook executed by zoneadmd will > run the code in statechange. I see that this script writes some info to > stdout and some to syslog. Commands that fail may write to stderr. If you > are running a platform image with the fix for OS-6834 stdout will be logged > to /zones/$uuid/logs/platform.log. The fix for OS-6802 will also cause > stderr to be logged to the same file. Everything that was logged via > "logger" should be found in /var/adm/messages. > > You can use 'zoneadm -z $uuid boot -X' to cause the brand scripts to be > executed in debug mode. This may offer additional hints as to what is > going wrong. If you want to add more debugging statements or try to fix > problems you find, a common way to do this is: > > # cp -r /usr/lib/brand /tmp > # mount -F lofs -O /tmp/brand /usr/lib/brand > > At this point, you will be able to edit everything under /usr/lib/brand. > Since the files you are editing are really on /tmp, they will be lost when > the global zone is rebooted. The original files stored in the platform > image will be present on reboot or when you utter "umount /usr/lib/brand". > > HTH, > Mike > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: http://www.listbox.com
