Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

/opt/VRTSvcs/bin/Application/monitor[130]: RC: not found

Created: 13 Oct 2011 • Updated: 14 Oct 2011 | 3 comments
This issue has been solved. See solution.

 Applications being in an “unknown status”  on the other nodes in the cluster.  The VCS error logged the other nodes do not recognize the the applications because user id's associated with the applications are not recognized  /opt/VRTSvcs/bin/Application/monitor[130]: RC:  not found User "" does not exist.Even though the users exists on all the nodes, the users home directory does not. Workaround

http://www.symantec.com/business/support/index?page=content&id=TECH74832 but still getting error

Comments 3 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

Hi Sherry,

 

So what is the VCS version you are using ? 

As mentioned in the tech article, do you have home directory configured in the failover service group ?

Can you paste the resource defination of application resource from the main.cf file ?

 

Gaurav

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

Anoop_Kumar's picture

Hi,

Below messages shows that you have not defined User argument.

/opt/VRTSvcs/bin/Application/monitor[130]: RC:  not found User "" does not exist

 

type Application (
    static str ContainerType = Zone
    static i18nstr ArgList[] = { User, StartProgram, StopProgram, CleanProgram, MonitorProgram, PidFiles, MonitorProcesses }
    str User
    str StartProgram
    str StopProgram
    str CleanProgram
    str MonitorProgram
    str PidFiles[]
    str MonitorProcesses[]
    str ContainerName
)

 

As advised by Gaurav, please share configuration from main.cf.

~Anoop

Sherry T's picture

Thanks for your reply. I received information back from Support that the hotfix below is required to resolve the issue.

http://www.symantec.com/business/support/index?page=content&id=TECH74610

SOLUTION