Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.


E0895: Gproxy, various problems with Alarms

Product: Gproxy
Platform: All Host Links
Status: Set of fixes available for 6.1
Last updated: 2003-08-13 08:32:53

There are various problems with Alarm processing in 6.1.

 - Alarms may not be sent if a server uses -NA with multiple IP
   addresses
 - Wrong time stamp in the HTML Alarm log
 - Missing Alarm 'anchor' in HTML index frame

Changes have been made to the following server programs due to
missing Alarm calls or changes to severity levels: Listener,
GUFTsrv, Gspool and Ggate.

Changes have been made to the alarm library (../gar/misc/alarms).
An updated library file is available.

The description of the HTML severity level parameter in the SRB
was wrong. It should read:

 There are 4 alarm severity levels:

 6 - information event
 4 - warnings/lo event
 3 - errors/high event
 2 - critical event

Gproxy takes a new argument '-ALM N' where N is the starting
severity level i.e. the lowest severity (highest number) used by
Gproxy when generating event log entries.

e.g. -ALM 3     report 'error events' and  'critical events'.
                ignore 'warning events' and 'info events'.

Avoidance procedure: None
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors
 
PARTNERS