RE: How to get Web Polygraph working under Linux with 1500 IP add ress es

From: Tash Hepting (
Date: Mon Dec 06 1999 - 14:31:43 MST

        Thanks for clarifying those aspects - I'll update my document.

> I am not sure, but it seem to me you are creating "permanent" aliases
> here (i.e., the aliases will be preserved across restarts).
> If you need
> temporary aliases or are changing aliases a lot, you may want to use
> "aka" tool instead. For example,
> root> src/aka eth0 10.1.1-3.1-250
> I am not 100% sure if "aka" works on Linux; I thought it used to.

        Yes, I am creating permanent aliases. Aka does not seem to work
under Linux, I get this message if I run "src/aka eth0":

eth0: resetting aliases to
eth0: primary address is broadcast
eth0: found 0 old aliases
eth0: deleted 0 old aliases (22) Invalid argument

        If I run "src/aka --if eth0 --aliases" the command does
not return any error messages, but no aliases as created. <shrug>

> The above can be shortened to '1.1.1-3.1-250'.

        Right. I think that was a little toooo obvious for me. Thanks for
the tip!
> Hmm.. This smells like a Linux limitation or a bug in Polygraph.
> Polygraph server side should run equally well with any number
> of IPs. If
> you have a test case where fewer IPs on the server side do not work,
> please report it to polygraph-bugs.

        Running a modified (lowered the content size to 1Byte to
maximize connections/sec) with 1500 client robots and one server IP, I get
the following error messages:

On the client: error: 1/1 (273) client ran out of new public oids

On the server:
SrvHistory:51: error: 1/127 (271) a server-advertised oid has not been
requested for a while
SrvHistory:59: error: 1/165 (274) server received too many requests for new

        I'll be sending this to polygraph-bugs also.

> Polygraph does not emit "dst cache overflow" messages. The
> messages you
> are seeing must be coming from the kernel or libraries. I do not know
> what the message means either. Anything interesting in kernel/system
> logs?

        About the only thing I could find in the logs is the message
repeating dozens of times (I left running for about 36hours or
so), and an indication that it is indeed a kernel error message. Not sure
where to look for more details beyond /var/log - anybody else have any


This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:10 MDT