SCHANA or SCC Creator Plug-in operation fails with getpid not found

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 115

Visibility:: Public

Votes:: 0

Category:: snapcenter

Specialty:: snapx

Last Updated:

Applies to

SnapCenter Plug-in for SAP HANA (SCHANA on Linux) 4.8-4.9P2
SnapCenter Creator Plug-in (SCC on Linux) 4.8-4.9P2

Issue

The following error occurs in the hana.log or <PLUG_IN>.log (MAXDB, Sybase, etc. - from the Automation Store):

 ERROR  [pool-#-thread-#] 189 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.ExecutorImpl -Exception occured - Could not determine PID of wrapper process

After these lines setting up the wrapper process, which checks the input files:

 DEBUG  [pool-#-thread-#] 90 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.ExecutorImpl -createProcess() - Running wrapper: {[/bin/sh, -c, sudo /opt/NetApp/snapcenter/scc/bin/sccCommandExecutor 'plugins/wrapper/wrapper -wid 205 -pn MAXDB -to 3600']}

 DEBUG  [pool-#-thread-#] 90 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.WrapperHelperImpl -createRequest() - Wrote request to {/opt/NetApp/snapcenter/scc/plugins/wrapper/in/205+MAXDB+1721812634206+getpid}

 DEBUG  [pool-#-thread-#] 90 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.WrapperHelperImpl -executeRequest() - Result file: {/opt/NetApp/snapcenter/scc/plugins/wrapper/out/205+MAXDB+1721812634206+getpid}

 DEBUG  [pool-#-thread-#] 90 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.ExecutorImpl -Logger stdout/stderr running={true}/{true}

 DEBUG  [pool-#-thread-#] 90 com.netapp.plugincreator.agent.nextgen.plugin.legacyservice.ExecutorImpl -Logger stdout/stderr running={false}/{false}

The quiesce fails also due to missing output file, however it claims a Timeout has happened, which is misleading (the timing of the log lines doesn't even show the 1 hour timeout as set in agent.properties, it fails in seconds):

INFO [pool-#-thread-##] 163 com.netapp.plugincreator.workflow.task.Quiesce -Application quiesce result is empty from plugin MAXDB. skipping metaData update operation

ERROR [pool-#-thread-##] 189 com.netapp.plugincreator.workflow.util.TaskUtil -Operation failed. Reason: The watchdog killed the running operation. Verify that plugins/wrapper/wrapper binary has execute permission set. Increase the WRAPPER_TIMEOUT_IN_MSEC value in agent.properties if operations require more time to complete. ERROR [pool-#-thread-##] 270 com.netapp.plugincreator.workflow.Task -Operation failed. Reason: The watchdog killed the running operation. Verify that plugins/wrapper/wrapper binary has execute permission set. Increase the WRAPPER_TIMEOUT_IN_MSEC value in agent.properties if operations require more time to complete. ERROR [pool-#-thread-##] 118 com.netapp.plugincreator.workflow.task.Quiesce -SCC-00164: Application quiesce for the plug-in [MAXDB] failed with exit code [102] and with error :Operation failed. Reason: The watchdog killed the running operation. Verify that plugins/wrapper/wrapper binary has execute permission set. Increase the WRAPPER_TIMEOUT_IN_MSEC value in agent.properties if operations require more time to complete.

Note: When running a Discovery (Resource Refresh) or a Backup, during the process a wrapper script is started to monitor and excute wrapper-input files and generate wrapper-output files.
The first of these is to get the PID of the process, which is normally returned in a same named file under scc/plugins/wrapper/out.