Sol_9 => Sol_10/08 Upgrade svc startup issue. Post: 302266739

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Sol_9 => Sol_10/08 Upgrade svc startup issue. Post 302266739 by ShawnLua on Thursday 11th of December 2008 12:54:06 AM

12-11-2008

Registered User

Sol_9 => Sol_10/08 Upgrade svc startup issue.

Dear all,

Recently I did an upgrade from Solaris 9 to Solaris 10 on a V440 System, after the initial reboot after the auto-reboot from the OS upgrade, the service: svc:/system/webconsole:console transitions into maintenance and cannot be manually brought online.

Below are a list of things I did to try resolve the issue:
#/usr/share/webconsole/private/bin/wcremove -i console
#svcadm restart svc:/system/webconsole:console
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# svcs -xv
svc:/application/print/server:default (LP print server)
State: disabled since Fri Dec 05 15:44:02 2008
Reason: Disabled by an administrator.
See: Sun Message ID: SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default

svc:/system/webconsole:console (java web console)
State: maintenance since Fri Dec 05 16:05:13 2008
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: Sun Message ID: SMF-8000-KS
See: man -M /usr/share/man -s 1M smcwebserver
See: /var/svc/log/system-webconsole:console.log
Impact: This service is not running.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# svcs -l webconsole
fmri svc:/system/webconsole:console
name java web console
enabled true
state maintenance
next_state none
state_time Fri Dec 05 20:06:02 2008
logfile /var/svc/log/system-webconsole:console.log
restarter svc:/system/svc/restarter:default
contract_id
dependency require_all/none svc:/milestone/network (online)
dependency require_all/refresh svc:/milestone/name-services (online)
dependency require_all/none svc:/system/filesystem/local (online)
dependency optional_all/none svc:/system/filesystem/autofs (online) svc:/netwo
rk/nfs/client (online)
dependency require_all/none svc:/system/system-log (online)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Previous Sun Java Web Console version was 2.2.4 before OS Upgrade, after OS Upgrade it was automatically upgraded to 3.1.

Current JRE is 1.5.0.16.

CAM version is 5.1.0.10

Funny thing is, after the upgrade I still see things like:
application SUNWcmcon Simplified Chinese Sun Java(TM) Web Console 2.2.4 (Core)
application SUNWcmctg Simplified Chinese Sun Java(TM) Web Console 2.2.4 (Tags & Components)
in the pkginfo -i output.

also:
application SUNWemcon Spanish Sun Java(TM) Web Console 3.1 (Core)
application SUNWemctg Spanish Sun Java(TM) Web Console 3.1 (Tags & Components)
but no English Sun Java(TM) Web Console 3.1

also:
application SUNWmcon Sun Java(TM) Web Console 3.0.2 (Core)
system SUNWmconr Sun Java(TM) Web Console 3.0.2 (Root)

This is causing CAM not to function..

I am thinking it maybe that the OS upgrade did not successfully upgrade the webconsole.

Anyone can provide any input or experienced similar issues?

Greatly appreciated.

ShawnLua

View Public Profile for ShawnLua

Find all posts by ShawnLua

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

init issue on startup

Hi, I modified my inittab file in the /etc directory. When I started up my machine, system hangs on initialization. I'm trying to remove what I added in the inittab file so that everything is back to normal. I'm using AIX 5 and I would like to boot up so I can get back into a regular...

2. Solaris

Live upgrade Issue

Hi, I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7

3. Shell Programming and Scripting

StartUp script Environmental Issue

Hi There, I have created a StartUp script which will create all alias's and export my path to GLOBAL so that i will be have some handy commands for simplifying my work My script code is like below ------------------------------------ #!/usr/bin/ksh set -o vi #Display the CURRENT USER...

4. Solaris

svc Errors on OS startup

I'm having these weird errors. svc.configd: Fatal error: Backend copy failed: fails to read from /etc/svc/repository.db at offset 106496: Bad file number svc.configd: Fatal error: unable to create "boot" backup of "/etc/svc/repository.db" Mar 10 13:04:23 svc.startd:...

5. Solaris

svc:/network/physical:default: Method "/lib/svc/method/net-physical" failed with exit status 96. [ n

After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks. ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface # ifconfig eg1000g0:2 plumb ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface # ifconfig...

6. Solaris

Live Upgrade Issue

I tried a live upgrade for one my solaris 10u8 server which didnt go sucessfull and after that i now have following mounts in memory. df: cannot statvfs /.alt.sol10u8_2/var: No such file or directory df: cannot statvfs /.alt.sol10u8_2/var/run: No such file or directory df: cannot statvfs...

7. AIX

Weird nfs issue after TL upgrade

We recently upgraded 2 of our AIX 6.1 servers from TL4 to TL5. Both servers are on the same p7 780 frame, installed at the same time from the same image. Both servers are mounting the same nfs share after reboot what worked perfectly fine until the upgrade. Since the patching, one of the two...

8. Solaris

Solaris 10 Live Upgrade Issue

Hi Guys, having an issue with running Live Upgrade on a t5240 runiing Solaris 10 5/08. The system has the required patches 121430, and Live upgrade was updated from the install media sol-10-u10-ga2-sparc-dvd.iso The following boot environments were created solenv1 and solenv2 with the...

9. Solaris

Solaris patching issue with Live Upgrade

I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade. Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less...

10. Red Hat

Hadoop - Upgrade Issue

Hi All, I was recently trying to upgrade Hadoop from CDH4 to CDH5 ,however after upgrade found below issue , Looks like this is a known issue but unable to find a proper solution for it . log4j:ERROR Could not find value for key log4j.appender.EventCounter log4j:ERROR Could not instantiate...

LEARN ABOUT V7

dh_systemd_start

DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME

       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS

       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION

       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS

       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO

       debhelper(7)

AUTHORS

       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)