Troubleshooting

While adding a tag, LicenseMonitor shows the error: "Cannot HUP"

If you see this error, it means that the vovlmd daemon is not running and it needs to be started. 1. To restart it, go to the Admin tab and select the Daemon option. 2. Find vovlmd and click start. 3. You'...

Read Article

LicenseMonitor shows an unexpectedly large Hiwater Mark (Admin Only)

When using LicenseMonitor, you may have an unexpectedly large hiwater mark, meaning the number of LM users exceeds expectations. This can be viewed, by going to the Admin tab and selecting the Licensing Option....

Read Article

Can't Install LM As a Service on Windows (LicenseMonitor)

To install License Monitor files, lmagent.64.exe and lm-win64.exe, as a service on Windows, you must run them as an administrator. To do so, right-click on the downloaded file (lmagent.64.exe and lm-win64.exe)...

Read Article

What to Do When a Job Fails with a Bad X11 Display? (NetworkComputer & FlowTracer)

Sometimes jobs fail and show the following error: Bad X11 Display VOV_JOB_XTERM: Cannot use DISPLAY=vl-c-abpate-gridsdca:12.0 with XTERM=/usr/bin/xterm: child process exited abnormally This is not a tool er...

Read Article

VOV: Resolve the Error "exec: vtclsh: not found"

If you see the error, "exec: vtclsh: not found" while attempting to run a script from within a cron job, it is likely because the PATH is not properly set in the cron job. See the following example: /path...

Read Article

What to do when a Job fails to Start (NetworkComputer)

Rarely, a job may not start, but if so, you can run the following tests to find the source of the issue. You may receive a message similar to the following: Job killed because it failed to start within 1m00s....

Read Article

vovslaves are showing NOLIC status (NetworkComputer)

If vovslaves are showing NOLIC status, verify that you have set up your RLM license server and verified it through the log file. If it seems to be working correctly, then run: % rlmstat -avail If the cpu_e...

Read Article

What does vovslave SICK status mean & how do I correct it? (NetworkComputer)

Usually, the status of NC vovslaves is FULL, WRKNG, READY, and occasionally BUSY. These are normal and indicate that vovslave is running one or more jobs or is available to run jobs. The status is attached to a...

Read Article

What Do I Do In the Event Of A Server Failover Or Crash?

Use a checklist for system recovery at http://nc-host:nc-port/cgi/sysrecovery.cgi. You can find this address with the following command: nc cmd vovbrowser -url /cgi/sysrecovery.cgi

Read Article

Troubleshoot a slow vovserver response (NetworkComputer)

Usually, the NC vovserver response time is very fast and is unnoticeable, even when handling hundreds to thousands of clients and with millions of jobs queued. But you may encounter a noticeable lag when submi...

Read Article