For the record, the problem was caused by inconsistent
configuration of 'nv' install service (we haven't really
nailed down what caused that state).
Creating another 144 install service from scratch succeeded.
Jan
On 07/28/10 06:39 PM, [email protected] wrote:
Hi Jan,
Restarting the install service did not help.
a...@solerator:~# installadm disable nv
Install Service was not running: nv
a...@solerator:~# installadm enable nv
The service nv._OSInstall._tcp.local is running.
On deleting the service I get the following message:
a...@solerator:/tftpboot# installadm delete-service nv
Unable to find dns-sd process.
Unable to find ai-webserver process.
Unable to find path /var/ai/46501
Not removing boot archive
/I86PC.OpenSolaris-5/platform/i86pc/$ISADIR/boot_archive. Boot archive is
in-use by service/clients:
ol_nxt
Not removing boot archive
/I86PC.OpenSolaris-5/platform/i86pc/$ISADIR/boot_archive. Boot archive is
in-use by service/clients:
ol_nxt
Detected that DHCP is not set up on this machine. To delete the DHCP macro, run
the following on your DHCP server:
/usr/sbin/dhtadm -D -m dhcp_macro_nv
I do not have any service / clients called ol_nxt. Could this be
because a previous service that I had (sol_nxt) did not get deleted
completely?
Thanks
Anna
On 7/28/2010 3:17 AM, Jan Damborsky wrote:
Hi Anna,
To be honest, I am not sure why webserver was not launched for
'nv' service. Could you please try if 'restarting' install service help ?
# installadm disable nv
# installadm enable nv
Jan
On 07/28/10 12:00 AM, [email protected] wrote:
I just realized that the webserver for the new service is not
running. The services on my server are:
a...@solerator:/# installadm list
Service Name Status Arch Port Image Path
------------ ------ ---- ---- ----------
nv on x86 46501 /export/aiserver/osol-dev-144-ai-x86
nv-1 on x86 46502 /export/aiserver/osol-dev-137-ai-x86-1
nv-2 on x86 46503 /export/aiserver/osol-dev-137-ai-x86-2
a...@solerator:/# pargs `pgrep webserver`
25035: /usr/bin/python2.6 /usr/lib/installadm/webserver -p 46502 /var/ai/46502
argv[0]: /usr/bin/python2.6
argv[1]: /usr/lib/installadm/webserver
argv[2]: -p
argv[3]: 46502
argv[4]: /var/ai/46502
27148: /usr/bin/python2.6 /usr/lib/installadm/webserver -p 46503 /var/ai/46503
argv[0]: /usr/bin/python2.6
argv[1]: /usr/lib/installadm/webserver
argv[2]: -p
argv[3]: 46503
argv[4]: /var/ai/46503
How do I manually start the webserver for the new service? I tried
the below command but it did not help.
# nohup /usr/bin/python2.6 /usr/lib/installadm/webserver -p 46501 /var/ai/46501&
Thanks
Anna
On 7/27/2010 1:28 PM, [email protected] wrote:
Thanks Jan,
I tried using the 144 AI image, but now the install fails for a
different reason. The log files show that the install fails to get
the manifest.xml file (Pls. see screenshots). Do you know what
could be causing this?
Thanks
Anna
On 7/27/2010 12:26 AM, Jan Damborsky wrote:
Hi Anna,
yep, it seems you are hitting 16478 - see install log attached to
16563
(one of duplicates of 16478):
https://defect.opensolaris.org/bz/attachment.cgi?id=4193
Since that problem was fixed in build 144, could you please retry
the installation with 144 AI image ?
Perhaps not related to this particular issue, but worth to mention -
AI image should always match the bits to be installed, since
this is the only guaranteed-to-work configuration.
Thank you,
Jan
On 07/27/10 01:59 AM, [email protected] wrote:
Hi,
I get the following error when I try to to install build 144 on
an x86 machine.
<ICT_E Jul 26 22:14:54> Unexpected error when updating boot
property. file=/a/boot/solaris/bootenv.rc
property=keyboard-layout value=Unknown
<ICT_E Jul 26 22:14:54> Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/osol_install/ict.py",
line 544, in _update_bootprop
fp = open(self.bootenvrc)
IOError: [Errno 2] No such file or directory:
'/a/boot/solaris/bootenv.rc'
<ICT_E Jul 26 22:14:54> Failure. Returning:
ICT_UPDATE_BOOTPROP_FAILED
<ICT Jul 26 22:14:54> current task:set_boot_device_property
<OM Jul 26 22:14:54> The install-finish script reported failures.
<OM Jul 26 22:14:54> The install finish script reported failures
<ICT Jul 26 22:14:54> current task: ict_snapshot
<ICT Jul 26 22:14:54> ict_snapshot Succeeded
<OM Jul 26 22:14:54> Marking root pool as 'ready'
<ICT Jul 26 22:14:54> current task: ict_mark_root_pool_ready
<ICT Jul 26 22:14:54> ict_mark_root_pool_ready Succeeded
<OM Jul 26 22:14:55> Installer build version: FMRI:
pkg://opensolaris.org/[email protected],5.11-0.137:20100409T144905Z
<OM Jul 26 22:14:55> Target build version: FMRI:
pkg://opensolaris.org/[email protected],5.11-0.144:20100717T032027Z
<OM Jul 26 22:14:55> Unmounting shared BE filesystems
<OM Jul 26 22:14:55> /usr/sbin/zfs unmount rpool/export/home/jack
<OM Jul 26 22:14:55> /usr/sbin/zfs set
mountpoint=/export/home/jack rpool/export/home/jack
<OM Jul 26 22:14:55> /usr/sbin/zfs unmount rpool/export/home
<OM Jul 26 22:14:56> /usr/sbin/zfs set mountpoint=/export/home
rpool/export/home
<OM Jul 26 22:14:56> /usr/sbin/zfs unmount rpool/export
<OM Jul 26 22:14:56> /usr/sbin/zfs set mountpoint=/export
rpool/export
<ICT Jul 26 22:14:56> current task: ict_transfer_logs
<ICT Jul 26 22:14:56> ict_transfer_logs Succeeded
<AI Jul 26 22:15:06> Automated Installation failed in
Installation Completion module
<AI Jul 26 22:15:06> One or more installation completion tasks
failed. Please see previous messages for more details
Would this be the same as bug 16478 or something different?
Thanks
Anna
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
