SnapCreator 3.5 and MaxDB plugin error

[AdvUniBS]

Hi,

one of our customers has a problem with MaxDB snaps.

The only things we see in the log and debug files are:

########## PRE APPLICATION QUIESCE COMMANDS ##########

[Thu Jul 12 10:45:26 2012] INFO: No commands defined

########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY ##########

########## Application quiesce ##########

[Thu Jul 12 10:46:26 2012] ERROR: No valid response

[Thu Jul 12 10:46:26 2012] ERROR: [scf-00053] Application quiesce for plugin maxdb failed with exit code 1, Exiting!

########## Application unquiesce ##########

[Thu Jul 12 10:47:26 2012] ERROR: No valid response

[Thu Jul 12 10:47:26 2012] ERROR: [scf-00054] Application unquiesce for plugin maxdb failed with exit code 1, Exiting!

########## PRE EXIT COMMANDS ##########

[Thu Jul 12 10:47:26 2012] INFO: No commands defined

########## PRE EXIT COMMANDS FINISHED SUCCESSFULLY ##########

Any ideas?

Thanks Bruno

[ktenzer]

This means the agent is 1) not running 2) hung / hosed / otherwise not working

I would restart your agent as first step.

This can happen if agent settings are not correct. I would also make sure you are running SC 3.5 some issues were fixed that caused agent problems. SC 3.5 also adds agent logging which provides more details about why something may have not worked. Agent logging is enabled in config and is on by default. Agent logs are locaged under logs/<profile> on agent.

Please check you should have settings like this:

SC_AGENT=myhost.mydomain.com:9090

SC_AGENT_TIMEOUT=60

SC_AGENT_UNQUIESCE_TIMEOUT=

SC_CLONE_TARGET=

SC_AGENT_WATCHDOG_ENABLE=Y

SC_AGENT_LOG_ENABLE=Y

In addition if this continues to be problem you can run without agent. Just install SC server on maxdb host directly and leave SC_AGENT blank.

Regards,

Keith

[AdvUniBS]

Hey Keith,

thanks for your reply. So it seems to be a communication problem between scServer and scAgent?

Because the backups ran now for 3 month fine, so I guess the config is fine.

Bye Bruno

[ktenzer · Accepted solution]

Yes most likely the agent isnt running or if it is something bad happened and if agent logging is enabled we can look and see what agent tried to do which caused issue.

Keith