After SFHA upgrade to 6.0 on Solaris, vxfsldlic service fails to start in local zone.<br><br>
Article ID: 100007500
Updated On:
Description
Error Message
svcs -a shows system booted to only single-user
# svcs -a | grep mile
online Dec_02 svc:/milestone/name-services:default
online Dec_02 svc:/milestone/devices:default
online Dec_02 svc:/milestone/network:default
online Dec_02 svc:/milestone/single-user:default
online Dec_02 svc:/milestone/sysconfig:default
offline Dec_02 svc:/milestone/multi-user:default << offline
offline Dec_02 svc:/milestone/multi-user-server:default << offline
# svcs -x (from local zone shows vxfsldlic is not starting.)
svc:/system/vxfs/vxfsldlic:default (VERITAS File System (VxFS) licensed feature enablement.)
State: maintenance since Mon Dec 05 07:14:10 2011
Reason: Start method failed repeatedly, last exited with status 1.
See: http://sun.com/msg/SMF-8000-KS
See: vxenablef(1M)
See: /var/svc/log/system-vxfs-vxfsldlic:default.log
Impact: 6 dependent services are not running. (Use -v for list.)
log for vxfsldlic:
[ Dec 5 06:47:55 Executing start method ("/lib/svc/method/vxfsldlic") ]
vxfsldlic: service configured
vxfs: loading vxportal...
Insufficient privileges to load a module
vxfs: enabling licenses...
UX:vxfs vxenablef: ERROR: V-3-22168: Cannot open portal device: No such file or directory
UX:vxfs vxenablef: ERROR: V-3-22158: Unable to enable VxFS feature VXFS. errno -1
[ Dec 5 06:47:56 Method "start" exited with status 1 ]
Cause
vxfsldlic service unable to open portal device.
Solaris 10 with local zones, vxfsldlic fails when opening missing /dev/vxportal device:
open64("/dev/vxportal", O_RDONLY) Err#2 ENOENT
The loopback device from the previous 5.1 workaround is now preventing the service from starting.
Resolution
1. Verify that the zone is up to date with global zone packages:
# zoneadm -z qzone detach
# zoneadm -z qzone attach -U
Getting the list of files to remove
Removing 4 files
Remove 8 of 8 packages
Installing 6 files
Add 8 of 8 packages
Updating editable files
The svcs log for the service will show that the /dev/vxportal device needs to first exist in the local zone before the service can startjj.
2. If the 5.1 SP1 RPx loopback filesystem workaround was implemented, remove it now from ALL nodes in the cluster:
zonecfg:qzone> info
zonename: qzone
zonepath: /zones/qzone
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
fs:
dir: /etc/vx/licenses/lic
special: /etc/vx/licenses/lic
raw not specified
type: lofs
options: []
net:
address: 10.167.18.131
physical: bge0
defrouter not specified
zonecfg:qzone> remove fs dir=/etc/vx/licenses/lic
zonecfg:qzone> verify
zonecfg:qzone> commit
zonecfg:qzone> info
zonename: qzone
zonepath: /zones/qzone
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address: 10.167.18.131
physical: bge0
defrouter not specified
zonecfg:qzone> exit
3. Attach and boot the zone:
# zoneadm -z qzone attach
zoneadm -z qzone boot
From within the zone:
# svcs -v vxfsldlic
STATE NSTATE STIME CTID FMRI
online - 10:06:23 - svc:/system/vxfs/vxfsldlic:default
4. if vxodm fails to start in the local zone:
Review the log:
Starting ODM...
mount: Mount point /dev/odm does not exist.
[ Dec 5 10:14:34 Method "start" exited with status 1 ]
While the zone is running, create the odm directory in the global zone:
# mkdir /zones/qzone/dev/odm
maintenance 10:14:34 svc:/system/vxodm:default
Stop and restart the vxodm service from within the zone:
# svcadm disable vxodm
# svcsadm enable vxodm
# svcs -v vxodm
STATE NSTATE STIME CTID FMRI
online - 10:31:51 - svc:/system/vxodm:default
Applies To
Solaris 10 with local zones.
SF / SFHA 6.0.
Issue/Introduction
