cancel
Showing results for 
Search instead for 
Did you mean: 

vcs resources monitoring time out

manishrajput
Level 2

Hi All,

Yesterday I faced issue with Application resource which was getting monitoring time outs multiple times. it's IState showing waiting to go online and flags was showing Monitoring time out.

After multiple attempts of Agent Application resource came  in not waiting state and with normal flags.

I want to ensure that is that issue with application or with VCS .

Can anyone suggest that we can tune any parameter to prevent this situtation .

 

Please have a look into attached file.

PFB below few lines of error segment output:-

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1405]: Client: UT_ER_PROCESS_INIT:  Process initialization failed  at line 1966 (Success)

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1405]: nodename=main-prd-meth05-db dbname=meth05 usrname=meth05 release=8.0.2

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1383]: Client: UT_ER_PROCESS_INIT:  Process initialization failed  at line 1966 (Success)

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1383]: nodename=main-prd-meth05-db dbname=meth05 usrname=meth05 release=8.0.2

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1398]: Client: UT_ER_PROCESS_INIT:  Process initialization failed  at line 1966 (Success)

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1398]: nodename=main-prd-meth05-db dbname=meth05 usrname=meth05 release=8.0.2

Jan 12 16:30:01 HTNDPUEDSVC09 ss.d[1388]: Client: UT_ER_PROCESS_INIT:  Process initialization failed  at line 1966 (Success)

Jan 12 16:30:45 HTNDPUEDSVC09 AgentFramework[14071]: VCS ERROR V-16-2-13074 Thread(4125064048) The monitoring program for resource(main-prd-meth05-db_versant) has consistently failed to determine the resource status within the expected time. Agent is restarting (attempt number 1 of 2) the resource.

Jan 12 16:30:45 HTNDPUEDSVC09 Had[14006]: VCS ERROR V-16-2-13074 (HTNDPUEDSVC09) The monitoring program for resource(main-prd-meth05-db_versant) has consistently failed to determine the resource status within the expected time. Agent is restarting (attempt number 1 of 2) the resource.

Jan 12 16:30:50 HTNDPUEDSVC09 ss.d[6076]: Client: VSL_SHM_ELOCAT:  can't locate shared memory with OS err #$(oserr)  at line 1921 (No such file or directory)

 

2 REPLIES 2

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

What kind of application is this and what type of resources in VCS?

You can stop VCS (hastop) and then manually start each resource in the correct dependancy order, using the same commands/scripts that are configured in VCS.

This looks like a script error:

Process initialization failed  at line 1966 (Success)

And this looks like a config error:

Client: UT_SS_IMPLICIT_STARTDB:  Starting database implicitly is prohibited by profile.be.  at line 1785 (Success).

 

 

Hi