NetVault Plug-in for VMware 13.2 - User Guide

Common errors

This section describes some common errors and their solutions. It includes the following topics:

NetVault Service fails to start on Windows

The NetVault Service fails to start on a Windows-based NetVault Server.

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault cannot start if the PostgreSQL database that is used to store the system data does not start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Server.

NetVault Service fails to start after the machine is restarted

After restarting the machine, the NetVault Service sometimes fails to start on a Windows-based NetVault Server.

Check the Windows Event Viewer for the following message: FATAL: could not create any TCP/IP sockets " for a PostgreSQL source

NetVault cannot start if the PostgreSQL database that is used to store the system data does not start. To correct this issue, start the Task Manager, and click Show processes from all users. You can see multiple instances of postgres32.exe running on the system. To remove all instances of postgres32.exe, select any instance of this process, and click End Process. Start the NetVault Service.

NetVault Service starts, but stops immediately on Linux

On a Linux-based machine, the NetVault Service starts, and then stops immediately.

No error messages are displayed.

This issue can occur if the Postgres service cannot resolve the host name localhost, and fails to start.

Check the /etc/hosts file, and if the file does not contain an entry for localhost, add the entry.