Mailing List Archive

On Fri, Apr 02, 2004 at 12:37:57PM -0500, William P LePera wrote:
> Using conserver on AIX, v 7.2.4, one of our people noticed a huge
> conserver log file in /var/log. Most of the entries are:
>
> conserver (18370): select: Bad file number
>
> She is not having a problem opening or using any of the consoles, but is
> concerned about the message. Is there a condition here I should be worried
> about?

well, aside from a huge logfile, i suppose not. it *is* a sign of a
bug, however. conserver must not be properly removing a file descriptor
from it's list of open files (it might not have dropped a bad console
structure or client structure or something else, even). it's hard to
say for sure.

restarting conserver should "fix" it...in that it'll all start over and
hopefully the bit of code that triggered the problem won't occur again
(very soon, anyway).

but the real key is to try and get to 7.2.7 (if possible). i can't
promise that the code that's at fault has been fixed in 7.2.7, but the
chances are pretty good. i haven't heard of any major issues with
7.2.7...unless most folks have made the jump to 8.x.x and there's a lack
of use of
7.2.7.

Bryan

William,

I have been very happy with 7.2.7 running on an HP/UX 10.20 box. I checked,
and there are no problems with log files in /var/log. I am monitoring just
short of 100 consoles via Xyplex terminal servers (with a power supply
"break" fix). The sysadmins think I am some kind of genius, but I tell them
it is just a great piece of software and point to Bryan's website.

7.2.7 is a very stable product. Thanks to Bryan.

Greg Brown
CSC, San Diego Data Center


>From: Bryan Stansell <bryan@conserver.com>
>To: users@conserver.com
>Subject: Re: conserver log entry
>Date: Fri, 2 Apr 2004 10:19:16 -0800
>
>On Fri, Apr 02, 2004 at 12:37:57PM -0500, William P LePera wrote:
> > Using conserver on AIX, v 7.2.4, one of our people noticed a huge
> > conserver log file in /var/log. Most of the entries are:
> >
> > conserver (18370): select: Bad file number
> >
> > She is not having a problem opening or using any of the consoles, but is
> > concerned about the message. Is there a condition here I should be
>worried
> > about?
>
>well, aside from a huge logfile, i suppose not. it *is* a sign of a
>bug, however. conserver must not be properly removing a file descriptor
>from it's list of open files (it might not have dropped a bad console
>structure or client structure or something else, even). it's hard to
>say for sure.
>
>restarting conserver should "fix" it...in that it'll all start over and
>hopefully the bit of code that triggered the problem won't occur again
>(very soon, anyway).
>
>but the real key is to try and get to 7.2.7 (if possible). i can't
>promise that the code that's at fault has been fixed in 7.2.7, but the
>chances are pretty good. i haven't heard of any major issues with
>7.2.7...unless most folks have made the jump to 8.x.x and there's a lack
>of use of
>7.2.7.
>
>Bryan
>_______________________________________________
>users mailing list
>users@conserver.com
>https://www.conserver.com/mailman/listinfo/users

_________________________________________________________________
Get rid of annoying pop-up ads with the new MSN Toolbar – FREE!
http://toolbar.msn.com/go/onm00200414ave/direct/01/