NetVault 13.0.3 - Administration Guide for Managed Service Providers

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 to see if it displays 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 to see if it displays 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. Select any one instance of this process, and click End Process to remove all instances of postgres32.exe. Then, start the NetVault Service.

Login fails after any change in the server IP address

Login from WebUI fails after any change in the NetVault Server IP address.

When you try to log in, the NetVault WebUI displays a message that the server is not accessible.

After any change in the IP address of the NetVault Server (for example, due to reassignment at reboot by DHCP), you must clear the browser cache before logging in to the NetVault WebUI. Otherwise, the login may fail with a message that the server is not accessible. Alternatively, you can assign a static IP address to the NetVault Server.