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.


E1039: Gproxy, redirection failed on UNIX/Linux

Product: Gproxy
Platform: UNIX/Linux (Lin
Status: Fixed in 6.3, fix available for 6.2 and 6.1.1
Last updated: 2005-04-20 12:14:58

Gproxy needs to be able to identify a broadcast from it's own
network (IP) address. In particular, Gproxy needs to be able to
recognize broadcast duplicates in cases where the system has
several interfaces configured, since broadcasts will be sent out
on all configured interfaces and may appear as coming from
several different systems.

Gproxy used standard OS function calls, i.e. gethostname() and
gethostbyname(), to find the local IP-address. If these
functions for some reason failed, e.g. if the 'hostname' did not
resolve into to a valid IP-address, or the OS for some other
reason returned a bad status, the Gproxy redirector and/or
license server would not work correctly.

The external symptoms were typically:

 - Gproxy license server process did not start and no local
   license were granted. This could be seen in the logfile or
   because there were not 2 Gproxy processes running.

 - Gproxy was unable to identify the systems correctly and only
   redirected clients to the local system. The HTML reports or
   the logfiles showed that Gproxy did not receive server load
   and license statistics from all involved servers.

This problem has only been observed on Linux systems.

Avoidance procedure:

If the system host name does not resolve correctly, fix the
configuration.

If the configuration is apparently correct, but the name
functions still fail, override the system configuration with
the Gproxy parameter:

   -myip IP-address (e.g. -myip 181.282.16.5)




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

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