Log messages in the range 400-499 are errors. Error messages are issued when normal gateway operation cannot complete successfully. The security of your gateway is still ensured, however you should attempt to correct any error that occurred. The message number, the message text, and a description of these messages follow:
This message indicates a severe internal error in the Eagle software. Functionality has probably been degraded. Please report all such errors to Raptor Systems.
Gwcontrol can't find its configuration file. This could mean that the Authorization machine may have crashed, or the private link between them broken.
Gwcontrol couldn't open its config file for reading.
While reading the config file, gwcontrol came across a serious error in the configuration file. The line number and error is reported. The entire line is ignored.
Gwcontrol received the command to reconfigure itself from its configuration file, but errors made it unable to do so. The old file is retained.
The audio file used in the notifyd configuration file notify.cf doesn't exist. This just means it can't ring the audio alarm.
The traceroute program cannot lock a file it needs to run.
The audio file mentioned in the notifyd daemon's config file is not one it can use.
The notifyd daemon wasn't able to open its configuration file.
The transport must be one of: Mail, Pager, Audio, or Fax.
Gwcontrol, when it has no previous configuration information to fall back on, will continue as well as possible.
A date/time authorization string in the notifyd daemon's config file was badly formed. The point at which the error occurred is given in string.
An expression string in the notifyd daemon's config file was badly formed. The point at which the error occurred is given in string.
The passer program tried to connect to a server as given in its config file but failed. The reason is given in error.
While reading its configuration file, passer failed looking up the host.
While reading its configuration file, passer wasn't allowed to use a port.
Passer couldn't open its configuration file to read it.
The server host was left off on a line in passer's config file.
The port was not within the limits for port numbers.
Proto was not UDP or TCP.
Passer is not allowed to use the FTP or Telnet ports.
Passer couldn't look up the symbolic name service in the /etc/services file.
An Eaglet couldn't look up the host name of its controlling Eagle.
An Eaglet couldn't read the location of its controlling Eagle.
An Eaglet couldn't read anything from the file that holds the name of its controlling Eagle.
An attempt to contact the machine host failed.
An error occurred while reading the Eagle's configuration file.
An attempt to run the program failed.
The Eagle attempted to contact one of its Eaglets, but failed.