Next: Alert Messages [severity Up: No Title Previous: Warning Messages [severity

Error Messages [severity Error]

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:

401
Internal error: error

This message indicates a severe internal error in the Eagle software. Functionality has probably been degraded. Please report all such errors to Raptor Systems.

402
Can't get config file; Authorization machine may be down

Gwcontrol can't find its configuration file. This could mean that the Authorization machine may have crashed, or the private link between them broken.

403
Can't read config file /usr/adm/sg/gateway.cf

Gwcontrol couldn't open its config file for reading.

404
error in config file (line N: error)

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.

405
re-read of config file FAILED! Using previous config file

Gwcontrol received the command to reconfigure itself from its configuration file, but errors made it unable to do so. The old file is retained.

406
notifyd: cannot open audio file file

The audio file used in the notifyd configuration file notify.cf doesn't exist. This just means it can't ring the audio alarm.

407
traceroute: can't open lock file /usr/adm/sg/traceroute

The traceroute program cannot lock a file it needs to run.

408
notifyd: file is not a valid audio file In the Audio transport, the given audio file to play was not in Sun's u-law format.

409
notifyd: file sample rate rate not available In the Audio transport, the given audio file had a rate that the audio hardware can't play.

410
notifyd: file encoding not available: type

The audio file mentioned in the notifyd daemon's config file is not one it can use.

411
notifyd: unable to open notify schedule /usr/adm/sg/notify.cf

The notifyd daemon wasn't able to open its configuration file.

412
notifyd: unrecognized transport in /usr/adm/sg/notify.cf (transport)

The transport must be one of: Mail, Pager, Audio, or Fax.

413
Have config file errors, but continuing

Gwcontrol, when it has no previous configuration information to fall back on, will continue as well as possible.

415
notifyd: syntax error in date/time string: string

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.

416
notifyd: syntax error in expression string 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.

417
passer: can't connect to host port port (error)

The passer program tried to connect to a server as given in its config file but failed. The reason is given in error.

418
passer: Line N: can't lookup host host

While reading its configuration file, passer failed looking up the host.

419
passer: Line N: bad server port port

While reading its configuration file, passer wasn't allowed to use a port.

420
passer: can't open config file /usr/adm/sg/passer.cf

Passer couldn't open its configuration file to read it.

421
passer: Line N: missing server host for service

The server host was left off on a line in passer's config file.

422
passer: Line N: bad port number port

The port was not within the limits for port numbers.

423
passer: Line N: bad protocol proto

Proto was not UDP or TCP.

424
passer: Line N: can't use TCP port port

Passer is not allowed to use the FTP or Telnet ports.

425
passer: Line N: can't lookup service service

Passer couldn't look up the symbolic name service in the /etc/services file.

430
Can't lookup Eagle hostname host

An Eaglet couldn't look up the host name of its controlling Eagle.

431
Can't open /usr/adm/sg/eagle.eyrie (error)

An Eaglet couldn't read the location of its controlling Eagle.

432
Bad hostname in /usr/adm/sg/eagle.eyrie

An Eaglet couldn't read anything from the file that holds the name of its controlling Eagle.

433
Can't connect to host (error)

An attempt to contact the machine host failed.

434
Error reading config file

An error occurred while reading the Eagle's configuration file.

435
Can't execute program to read config file (error)

An attempt to run the program failed.

440
readeagle-eaglet: Config load of Eaglet

The Eagle attempted to contact one of its Eaglets, but failed.



Next: Alert Messages [severity Up: No Title Previous: Warning Messages [severity


tkevans@delmarva.com