[Info-Ingres] Unable to make outbound connections all of a sudden

[Jim Gramling]

Sorry ... I just noticed that, in your post, you said "unable to make
outbound connections" ... so I misunderstood your post: your problem
is on the client machine?  What kind of machine is it? running AIX
also?  Have you tried rebooting your client machine?

Still could be a ticket issue on the server side if you are using
installation passwords.  Try bypassing the name server as Karl
suggested; also, take a look at "show comsvr *" in iinamu to see if
all five gcc's are actually registered.

Regards,

Jim Gramling
Rio de Janeiro

On Feb 8, 8:13 pm, "Jim Gramling" <jimwgraml... at gmail.com> wrote:
> Steve said:
>
> > We has a live production installation with 250+ clients connected via
> > an openroad 4.1 application, the b/e is AIX 5.2 .
> <snip>
> >We  have load balancing with 5 iigcc's starting (one interesting point is
> > the fact we now only appear to have one of them clocking up CPU time
> > when looking at a ps -ef output).
>
> '
> Steve, what does the client netutil look like? do you have merged
> vnode entries on each client (II0, II1, II2, etc.)?  Is each client
> netutil configured seperately or do you use some kind of funky, shared
> network client installation?  I know you say that nothing has changed,
> but if that is the case, if one user changed the netutil installation,
> it might have affected all clients.
>
> If you do have merged netutil entries, can you do a test connection to
> each gcc within netutil from a remote client?
>
> Another thing ... this is a longshot, but, are you by any chance using
> installation passwords?  If so, check the following file: $II_SYSTEM/
> ingres/files/name/IILTICKET_*.  Does it seem really large and
> growing?  Is the iigcn process consuming an inordinate amount of cpu?
> If so, do this :
>
> ingstop -iigcn
> rm $II_SYSTEM/ingres/files/name/IILTICKET_*
> ingstart -iigcn
>
> Then get back in touch with me:  There is a known Ingres bug that can
> bring the name server to a screeching halt when you have frequent
> connections and use installation passwords; used installation password
> "tickets" aren't correctly "cleaned up", causing the IILTICKET file to
> grow forever.  When it reaches "critical mass" (in my case, that was a
> couple-hundred Mb), iigcn cpu use soars and the gcn no longer can
> respond adequately to remote connection requests.  I wouldn't think
> that 250 users would be enough to cause you problems (actually, I
> wouldn't even think that you would need five iigcc's), but  anything
> is possible.
>
> These are the only things that come to mind.  If you are desperate and
> really adventurous, you can activate GCN tracing, which might shed
> some additional light on what's going on.
>
> export II_GCA_LOG="mytracefile.out"
> export II_GCN_TRACE=5
>
> ingstop -iigcn
> ingstart -iigcn
>
> Good luck!
>
> Jim Gramling
> Rio de Janeiro