Forum Discussion

g_lee's avatar
g_lee
Level 6
12 years ago

Solaris 11.1 SFHA 6.0.3 - svc:/system/VRTSperl-runonce:default in maintenance

On fresh install of SFHA 6.0.3 on Solaris 11.1 SPARC (per instructions, ie: install 6.0.1 w/out configuration, install 6.0.3, then configure) - the following service is showing in maintenance state:

# svcs -xv
svc:/system/VRTSperl-runonce:default (?)
 State: maintenance since Mon Feb 11 14:11:28 2013
Reason: Start method failed repeatedly, last exited with status 127.
   See: http://support.oracle.com/msg/SMF-8000-KS
   See: /var/svc/log/system-VRTSperl-runonce:default.log
Impact: This service is not running.

Looking at the log, the start method fails as the file it's trying to run ( /opt/VRTSperl/bin/runonce ) is missing / does not exist:

# tail /var/svc/log/system-VRTSperl-runonce:default.log
[ Feb 11 14:11:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
/usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
[ Feb 11 14:11:28 Method "start" exited with status 127. ]
[ Feb 11 14:11:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
/usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
[ Feb 11 14:11:28 Method "start" exited with status 127. ]
[ Feb 11 14:11:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
/usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
[ Feb 11 14:11:28 Method "start" exited with status 127. ]

Has anyone else seen this in SF 6.0.3?

The file name implies it's something that only needs to be run once (and was possibly deleted after it was run) - should this service be disabled/removed as part of the installation so it doesn't come up in maintenance every time?

Please advise if further details are required.

thanks,
Grace

  • Hi Grace,

    Our Dev team came up with a workaround (see below)

    After SFHA upgrade (to 6.0.3) is complete, if you find svc:/system/VRTSperl-runonce:default SMF service in maintenance state, perform the following steps.

    1.#svcadm disable svc:/system/VRTSperl-runonce:default

    2.#svccfg delete -f svc:/system/VRTSperl-runonce:default

    Also you can ignore any such message that may come on the console. svc.startd[11]: svc:/system/VRTSperl-runonce:default: Method

    "/opt/VRTSperl/bin/runonce" failed with exit status 127

    We will produce a technote for this shortly

    thanks

    tony

  • Possibly this is residue, will need to dig further.

    So to recap - this was a fresh install on Sol11.1. 6.0.1 installed (but not configured), then 6.0.3 installed and configured.

    Which product what chosen as part of the configuration ? SF, SFHA, SFCFS

     

    thanks

  • Tony,

    Yes, it was a newly installed Solaris 11.1 system; 6.0.1 was installed (not configured), then installed 6.0.3 and configured with installsfha601 -configure

    SFHA was chosen for the install & configuration.(recommended packages, not all).

    regards,

    Grace

  • Hi Grace,

    Our Dev team came up with a workaround (see below)

    After SFHA upgrade (to 6.0.3) is complete, if you find svc:/system/VRTSperl-runonce:default SMF service in maintenance state, perform the following steps.

    1.#svcadm disable svc:/system/VRTSperl-runonce:default

    2.#svccfg delete -f svc:/system/VRTSperl-runonce:default

    Also you can ignore any such message that may come on the console. svc.startd[11]: svc:/system/VRTSperl-runonce:default: Method

    "/opt/VRTSperl/bin/runonce" failed with exit status 127

    We will produce a technote for this shortly

    thanks

    tony

  • Tony,

    Thanks for following this up - I knew the technical procedure to disable/delete the service; my question was more around whether or not it was something that was supposed to be running / if it indicated there was an issue/failure earlier that needed to be corrected.

    Having a technote available will help - thanks again.

    Grace

  • We had the same problem.  I also understand the technical procedure to disable/delete the service.   I also searched for the "runonce" script/executable but didn't find anything...

    My question is how do we confirm that whatever needed to "runonce" actually ran and succeeded or if nothing really needed to run? and this really is just residue

     

    here is the log output I have:

     

    svc:/system/VRTSperl-runonce:default (?)
     State: maintenance since March  6, 2013 12:14:28 PM CST
    Reason: Start method failed repeatedly, last exited with status 127.
       See: http://support.oracle.com/msg/SMF-8000-KS
       See: /var/svc/log/system-VRTSperl-runonce:default.log
    Impact: This service is not running.


    root@host:/var/adm# cat /var/svc/log/system-VRTSperl-runonce:default.log
    [ Mar  6 11:21:30 Enabled. ]
    [ Mar  6 11:21:30 Rereading configuration. ]
    [ Mar  6 11:21:30 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 11:21:30 Method "start" exited with status 127. ]
    [ Mar  6 11:21:30 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 11:21:30 Method "start" exited with status 127. ]
    [ Mar  6 11:21:30 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 11:21:30 Method "start" exited with status 127. ]
    [ Mar  6 12:14:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 12:14:28 Method "start" exited with status 127. ]
    [ Mar  6 12:14:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 12:14:28 Method "start" exited with status 127. ]
    [ Mar  6 12:14:28 Executing start method ("/opt/VRTSperl/bin/runonce"). ]
    /usr/sbin/sh[1]: exec: /opt/VRTSperl/bin/runonce: not found
    [ Mar  6 12:14:28 Method "start" exited with status 127. ]
     

     

    Thanks-

     

    -John

  • For reference - relevant technote: http://www.symantec.com/docs/TECH203162