Every weekend, my QA OM server will be stopped for a offline Oracle backup. This weekend, after the backup, OM never started. I tried to start and it wouldn't. On checking the log System.txt, I found these :
0: ERR: Mon Jul 28 06:01:16 2014: ovcd (23454/47264176451744): (ctrl-127) Could not write the ovcd pid to file: 'No space left on device'.
0: INF: Mon Jul 28 06:02:17 2014: ovc (23451/47221706264736): (ctrl-103) Could not start the Control daemon.
0: ERR: Mon Jul 28 06:02:19 2014: ovcd (25940/1103829312): (sec.cm.client-23) Error during CertificateClient initialization.
1: ERR: Mon Jul 28 06:02:19 2014: ovcd (25940/1103829312): (xpl-89) write(13)[19720B50] failed.
2: ERR: Mon Jul 28 06:02:19 2014: ovcd (25940/1103829312): (RTL-28) No space left on device
0: ERR: Mon Jul 28 06:02:19 2014: ovcd (25940/1103829312): (ctrl-63) Error initializing RPC server: Can not initialize RpcServer. error=(xpl-89) write(16)[19724D60] failed.
(RTL-28) No space left on device.
/var/opt/OV was 100% full.
Tracing was enabled and the trace file was almost 13GB.
I deleted the trace file, disabled tracing and tried to start opcsv.
#>>/opt/OV/support/ovtrccfg -help (used for tracing)
#>> /opt/OV/support/ovtrcadm -hosts
The following are the allowed clients for TraceServer
S. No. Client Name or IP address
-------- -------------------------
This is used to list the nodes that are configured to trace.
#>>/opt/OV/support/ovtrcadm -srvconfig TraceServer is running Application Components Categories Level Enabled ----------- ---------- ---------- ------------- com.hp.openview.OvDiscoveryServer.OvDiscoveryServer org.apache.catalina.startup.Bootstrap java.lang.Thread com.hp.ov.svcdisc.SvcDiscClient gives the list of what is being traced.
I used the following command to disable tracing.
ovtrccfg -off
This disabled the tracing and I was able to start OM using opcsv.
No comments:
Post a Comment