Global Daemon Messages
- Last UpdatedJan 31, 2025
- 3 minute read
When a project is first made Global, or when a new location is created, the daemon must be started up at each on-line location as described in Running the Global Daemon. The daemon should be started up on the workstation that will be connected to the remote locations.
This chapter explains some of the messages that may be output by the daemon if there is a problem. The messages, with brief explanations and suggestions about what to do, are given below.
|
Message |
Meaning/action |
|---|---|
|
Wrong number of arguments |
The start or stop command line argument is missing. |
|
Invalid argument |
Attempt to use a command line argument other than start or stop. |
|
Project name should be 3 characters long |
A project code should be exactly three characters long. It is case insensitive. |
|
Project environment variable not set |
The environment variable (in the form ABC000) is not set. Set the environment variable and then retry. |
|
Project directory not found |
The environment variable (in the form ABC000) is set but it does not appear to point to a valid directory. |
|
RPC communication problem |
You cannot communicate with other locations. There appears to be a problem with the installation of the underlying communications software. Refer to the Knowledge and Support Center. |
|
admind daemon already started |
The Global daemon is already running on the local workstation. Only one version of the Global daemon may be started on a workstation. |
|
Message |
Meaning/action |
|
Cannot find/open System database for project |
The daemon has been unable to find and to then open the System database in the project directory. Check that the environment variable is pointing to the correct directory and that the directory contains a project. |
|
Cannot find/open Global database for project |
The daemon has been unable to find and to then open the Global database in the project directory. Check that the environment variable is pointing to the correct directory and that the directory contains a project. If the project does not contain the files glbvir.dat and abcglb (for project ABC), then it is not a Global project. |
|
Cannot find/open Comms database for project |
The daemon has been unable to find and to then open the comms database in the project directory. Check that the environment variable is pointing to the correct directory and that the directory contains a project. |
|
Unable to find the reference to the current location |
The STAT element in the System database contains a reference attribute LOCRF. If the Global project has been created properly, then the LOCRF attribute will correctly point to a Location element in the Global database. This problem could arise if the wrong System database had been copied manually to a location. |
|
Unable to find the name of the current location Incorrect System DB |
The STAT element in the System database contains a reference attribute LOCRF. If the Global project has been created properly, then the LOCRF attribute will correctly point to a Location element in the Global database. |
|
Hostname has not been set for this location |
The Location element contains an attribute RHOST that does not appear to have been set. |
|
Attempt to run daemon on processor ¼ Hostname for this location should be ¼ |
The Location element contains an attribute RHOST that does not appear to match the hostname of the current workstation. |
|
Cannot start database thread |
One of the main sub-systems of the Global daemon has not started. Try to restart the daemon; if it continues to fail then please report the problem to AVEVA Customer Services. |
|
Cannot start timer thread |
One of the main sub-systems of the Global daemon has not started. Try to restart the daemon; if it continues to fail then please report the problem to AVEVA Customer Services. |