http://defect.opensolaris.org/bz/show_bug.cgi?id=12197
Summary: nwam service not coming up due to read-only filesystem
Classification: Development
Product: nwam
Version: RC4
Platform: SPARC/sun4v
OS/Version: All
Status: NEW
Severity: major
Priority: P3
Component: ON misc
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: John.Leser at sun.com
QAContact: nwam-dev at opensolaris.org
--- Comment #0 from John Leser <John.Leser at sun.com> 2009-10-23 00:41:01 UTC
---
I just BFUed to RC4 on a SunFire T2000. I disabled network/physical-default,
enabled nwam, and rebooted. On reboot, nwam failed to come up with the
following errors:
bash-3.2# svcs -x
svc:/network/physical:default (physical network interfaces)
State: disabled since Thu Oct 22 20:15:29 2009
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: ifconfig(1M)
Impact: 51 dependent services are not running. (Use -v for list.)
svc:/network/physical:nwam (physical network interface autoconfiguration)
State: maintenance since Thu Oct 22 20:15:41 2009
Reason: Start method failed repeatedly, last exited with status 1.
See: http://sun.com/msg/SMF-8000-KS
See: nwamd(1M)
See: http://opensolaris.org/os/projects/nwam/
See: http://opensolaris.org/os/project/nwam/p1spec/
See: /etc/svc/volatile/network-physical:nwam.log
Impact: 51 dependent services are not running. (Use -v for list.)
svc:/network/rpc/smserver:default (removable media management)
State: uninitialized since Thu Oct 22 20:15:36 2009
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: rpc.smserverd(1M)
Impact: 3 dependent services are not running. (Use -v for list.)
bash-3.2# cat /etc/svc/volatile/network-physical:nwam.log
[ Oct 22 20:15:29 Enabled. ]
[ Oct 22 20:15:38 Executing start method ("/lib/svc/method/net-nwam start"). ]
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
/lib/svc/method/net-nwam: 10.8.57.3,10.8.57.1: cannot create
[ Oct 22 20:15:39 Method "start" exited with status 1. ]
[ Oct 22 20:15:39 Executing start method ("/lib/svc/method/net-nwam start"). ]
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
/lib/svc/method/net-nwam: 10.8.57.3,10.8.57.1: cannot create
[ Oct 22 20:15:40 Method "start" exited with status 1. ]
[ Oct 22 20:15:40 Executing start method ("/lib/svc/method/net-nwam start"). ]
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
mkdir: "/etc/nwam/loc/Legacy": Read-only file system
cp: cannot create /etc/nwam/loc/Legacy: Read-only file system
/lib/svc/method/net-nwam: 10.8.57.3,10.8.57.1: cannot create
[ Oct 22 20:15:41 Method "start" exited with status 1. ]
I looked at nwam's dependency set (in the xml file and using svcs -d) and I
can't see any dependency (direct or indirect) on a read/write filesystem.
The sun4v systems have so many CPU cores that service startup is likely to
happen in different sequences.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
