Welcome
What's New
View new features for VOV Subsystem 2025.1.0.
Overview
Discover the workspace, licensing and installation, and training.
VOV Subsystem Tutorials
Discover VOV Subsystem functionality with interactive tutorials.
VOV Subsystem Administrator Guide
This manual provides information about managing a VOV project, including starting the server and connecting computing resources such as computers and licenses.
VOV Subsystem Reference Guide
- Command Line Interface
- Fields, Selection Rules and Formatting Strings
- VOV Metrics
  The Altair Accelerator allows users to collect arbitrary metrics, where a metric is defined as a "named time series" of values, where each value is either a floating point number or a string.
- Miscellaneous
  - Inner Loop Timers
    The vovserver tracks how the time is spent in the inner loop. The statistics are accumulated over multiple loops and are rotated every 10 seconds, so what you normally see in the stats is the overall time spent in the past 10 to 20 seconds.
  - Sequence of Firing of a Job on a Tasker
  - Error Message: "Too many notify clients for user ..."
  - Error message: "Cannot accept more connections"
  - vtk_server_config
  - Expected Duration
  - Environment Variables
  - Other Files Used by VOV
  - HTML Pages
  - Raw HTTP/VOV Interface
- VOV Security Infrastructure
- REST Application Programming Interface
  Altair Accelerator supports a RESTful API that enables a developer to submit, monitor, and control batch jobs as well as query the batch scheduler queues, jobs, and hosts in useful ways.
- All About Tcl
- VTK Procedures
EDA Tool Integration Guide
This document is a collection of techniques that have proven to be useful when applying FlowTracer in Electronic Design Automation.

Error message: "Cannot accept more connections"

This message, which can be found in the vovserver log, means that the table of connection is filling up and the vovserver refuses to accept more. This is connected to the number of file descriptors available to vovserver. This is typically around 1,000 for small compute farms or 65,000 and even more for large compute farms.

The remedy could be:

Find out if there are abusers of the system. You can do that with:
```
% vovshow -users
% vovshow -clients
```
If an abuser is identified, perhaps he or she can be educated on the socially responsible use of the computing resources.
Increase the number of file descriptors available to the vovserver. Check the Server Capacity page for more details. This will require a restart of vovserver.