Running Global Projects
Suggested Housekeeping Guidelines for Projects
:
Global
: Daemon Log File
Daemon Log File
If the Global Daemon crashes unexpectedly there may two types of cause; 1. An unexpected problem with the databases that is not being picked up in Dice or 2. An IT infrastructure issue. To determine which, a log file can be activated via a system environment variable (evar) that will capture detail of all Daemon activity, particularly exactly what was happening leading up to the crash. The evar is DEBUG_ADMIND ‑ see chapter 4. Output from the daemon should be piped to a file.
This log file should be sent together with the Transaction db & Global and System dbs for Hub and satellites to the AVEVA support desk who can work with R&D to determine whether it is 1 or 2. If 1 then a repair can be advised on the problem database and/or a fix in code to prevent it recurring can be deduced. If 2 then further investigation in what was happening in the IT infrastructure needs to be done by the customer. Some evidence may be found in the Windows System Event Log which should also be shared with AVEVA to help isolate the issue.
The log file can grow quite large if left running for a period so it should be cleaned down daily by renaming it during a period of Daemon inactivity with a time and date stamp which means that when the Daemon restarts a new file will be created. Should holding the renamed file on disk be a problem on space it can be archived off and deleted.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
