Subject | Re: [ib-support] Re: Error 10054 |
---|---|
Author | Jason Chapman (JAC2) |
Post date | 2002-04-15T08:32:48Z |
90% of the time it is a client being switched off or a program hanging
followed by a reboot.
I support a fairly large site and they check the 10054's infact the whole
log file once a week. They divide the number of incidents by the number of
workstations expected to be using IB durign the week, they track this number
and ensure it stays pretty static. So maybe in a week 25 entries, 200
workstations, gives 12.5%, i.e. one in eight machines dies once a week.
Their favorite is hot desking call centre staff, one shift finishes (the
user doesn't log out) and the guys turn the VDU's off, the next person comes
along, thinks "Oh the machine is off" and hits the on-off button, one 10054
on its way to being logged on the server.
What is your weekly ratio?
If you get blocks within a very short time (say 20 in a minute), it normally
means that you have a localised power cut to clients, or a switch / hub has
just died / been disconnected.
It's worth monitoring, but not missing ZZZ's over.
JAC.
""csswa"" <csswa@...> wrote in message
news:a972ci+uqo6@......
followed by a reboot.
I support a fairly large site and they check the 10054's infact the whole
log file once a week. They divide the number of incidents by the number of
workstations expected to be using IB durign the week, they track this number
and ensure it stays pretty static. So maybe in a week 25 entries, 200
workstations, gives 12.5%, i.e. one in eight machines dies once a week.
Their favorite is hot desking call centre staff, one shift finishes (the
user doesn't log out) and the guys turn the VDU's off, the next person comes
along, thinks "Oh the machine is off" and hits the on-off button, one 10054
on its way to being logged on the server.
What is your weekly ratio?
If you get blocks within a very short time (say 20 in a minute), it normally
means that you have a localised power cut to clients, or a switch / hub has
just died / been disconnected.
It's worth monitoring, but not missing ZZZ's over.
JAC.
""csswa"" <csswa@...> wrote in message
news:a972ci+uqo6@......
> Roger, this from the MERS faq:
>
> -----
> >TEXUROSERVER1 (Server) Tue May 19 16:59:46 1998
> > INET/inet_error: read errno = 10054
>
> Messages of the form NAME/name come from an external service called
> NAME - the INET service in this case. The message category is name -
> inet_error. The actual message text follows. This one means
> connection lost. The cause is probably the fact that the server
> crashed. The same message also occurs when a client exits without
> closing the database connection. In any event, for messages of the
> form NAME/name: text, look in the documentation for NAME under name.
> -----
>
> So perhaps the second explanation??: "The same message also occurs
> when a client exits without closing the database connection"
>
> HTH
> Regards,
> Andrew Ferguson
>
>
>
> --- In ib-support@y..., "Roger Pullen" <pullen.roger@v...> wrote:
> > Have noticed this error occurring lots of times in the interbase
> log,
> > what does it mean? - is it anything to worry about?
> >
> > MARKINSDB (Server) Fri Apr 12 11:50:17 2002
> > INET/inet_error: read errno = 10054
> >
> > MARKINSDB (Server) Fri Apr 12 11:50:38 2002
> > INET/inet_error: read errno = 10054
> >
> > MARKINSDB (Server) Fri Apr 12 13:36:19 2002
> > INET/inet_error: read errno = 10054
> >
> > Everything is running OK though
> >
> > W2K server, IB6 original
> >
> > Regards
> >
> > Roger
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>