[OpenIndiana-discuss] zone install hangs/never completes
Milan Jurik
milan.jurik at xylab.cz
Mon Jun 11 06:32:53 UTC 2012
Hi Ryan,
On 11.06.2012 06:22, Ryan Cunningham wrote:
> Hello,
>
> I've tried Googling but haven't had any luck thus far--I'm attempting
> to install a zone on my oi_151-a4 system but it looks to be hanging
> for some reason. fwiw the system was initially installed using oi_147
> media, upgraded to oi_148 and then recently upgraded to oi_151-a4.
>
> The output to my terminal isn't especially informative:
>
> # zoneadm -z azone install
> Publisher: Using openindiana.org (http://pkg.openindiana.org/dev/
> ).
> Image: Preparing at /zone/azone/root.
>
> ptree shows:
>
> 1469 screen
> 1470 /bin/bash
> 1474 sudo su -
> 1475 -bash
> 1493 zoneadm -z azone install
> 1494 /bin/ksh -p /usr/lib/brand/ipkg/pkgcreatezone -z
> azone
> -R /zone/azone
> 1652 /usr/bin/python2.6 /usr/bin/pkg image-create -f
> --no-refresh --zone --full -p o
>
> pfiles doesn't reveal anything I find to be particularly
> illuminating:
>
> # pfiles 1652
> 1652: /usr/bin/python2.6 /usr/bin/pkg image-create -f --no-refresh
> --zone --
> Current rlimit: 65536 file descriptors
> 0: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7
> rdev:27,4
> O_RDWR
> /dev/pts/4
> offset:14832
> 1: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7
> rdev:27,4
> O_RDWR
> /dev/pts/4
> offset:14832
> 2: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7
> rdev:27,4
> O_RDWR
> /dev/pts/4
> offset:14832
> 3: S_IFDOOR mode:0444 dev:560,0 ino:49 uid:0 gid:0 size:0
> O_RDONLY|O_LARGEFILE FD_CLOEXEC door to nscd[616]
> /var/run/name_service_door
> 4: S_IFCHR mode:0666 dev:550,0 ino:19398660 uid:0 gid:3 rdev:37,0
> O_RDWR
> /devices/pseudo/zfs at 0:zfs
> offset:0
> 5: S_IFREG mode:0444 dev:555,1 ino:2 uid:0 gid:0 size:3520
> O_RDONLY
> /etc/mnttab
> offset:0
> 6: S_IFREG mode:0444 dev:558,1 ino:128 uid:0 gid:0 size:233
> O_RDONLY
> /etc/dfs/sharetab
> offset:0
> 7: S_IFREG mode:0600 dev:556,3 ino:1000972048 uid:0 gid:0 size:0
> O_RDWR|O_CREAT
> advisory write lock set by process 1493
> /var/run/zones/azone.zoneadm.lock
> offset:0
>
> truss shows that the Python process isn't actually doing much of
> anything:
>
> # truss -p 1652
> lwp_mutex_timedlock(0xFCF10000, 0x00000000, 0xFEE22A40) (sleeping...)
>
truss shows only the current call in the active thread. Try pstack to
see what it is doing.
Best regards,
Milan
> Is there something really obvious I'm missing with this?
>
> Thanks in advance for any insights,
> Ryan
>
More information about the OpenIndiana-discuss
mailing list