I replaced a bad hub with a new switch on my network. Now the unix server ke
eps giving error meesages.

/ete/getty ttya08 n (The Date Is Here), PID 7388:
Cannont open line ttya08: No such or address (error6)

The message keeps repating down the page then I can't access the system. Doe
s anyone have an idea.

Joe

[ Post a follow-up to this message ]

On Thu, 16 Dec 2004 22:47:14 GMT, Joe <joe@epix.net> wrote:
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_000C_01C4E397.212CD690
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> I replaced a bad hub with a new switch on my network. Now the unix =
> server keeps giving error meesages.
>
> /ete/getty ttya08 n (The Date Is Here), PID 7388:
> Cannont open line ttya08: No such or address (error6)

Not related.  Hire a Unix guy.  Tell him what kind of Unix you're using
so he can guess what "error6" means.

[ Post a follow-up to this message ]

In article <Sfowd.1139$925.119656@news1.epix.net>, "Joe" <joe@epix.net>
wrote:

> I replaced a bad hub with a new switch on my network. Now the unix server
> keeps giving error meesages.
>
> /ete/getty ttya08 n (The Date Is Here), PID 7388:
> Cannont open line ttya08: No such or address (error6)
>
> The message keeps repating down the page then I can't access the system. D
oes
> anyone have an idea.
>
> Joe

The message is talking about terminal lines, nothing to do with the
network.  Looks like you've screwed up some stuff in /dev.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

[ Post a follow-up to this message ]

Joe wrote:
> I replaced a bad hub with a new switch on my network. Now the unix
> server keeps giving error meesages.
>
> /ete/getty ttya08 n (The Date Is Here), PID 7388:
> Cannont open line ttya08: No such or address (error6)
>
> The message keeps repating down the page then I can't access the system.
> Does anyone have an idea.
>
> Joe

Are you positive it was an ethernet hub? It might have used RJ45 ends,
but by the sound of it, was not actually ethernet.  Very well could have
been a serial terminal muxer, or half a dozen other things that have the
same form factor as an ethernet hub.

[ Post a follow-up to this message ]

Dave Hinz wrote:
>
> Not related. Hire a Unix guy.

Agreed.  Changing network hardware should not have a direct
effect on a serial line, so something else happened.

/etc/getty does login ports that aren't necessarily on serial
lines.  Figuring out what ttya08 actually is is a good starting
point.  Then why is there chatter on it now rather than a login
session.

> Tell him what kind of Unix you're using
> so he can guess what "error6" means.

That won't help.  Error 6 is likely to be the same on any UNIX.
>From a Solaris box I happened to be on:

# grep "No such " /usr/include/sys/errno.h
#define ENOENT  2       /* No such file or directory            */
#define ESRCH   3       /* No such process                      */
#define ENXIO   6       /* No such device or address            */
#define ENODEV  19      /* No such device                       */

Rather than doing a cut-n-paste of the exact message, his
by hand transcription missed the word "device" from the name of
error 6.

[ Post a follow-up to this message ]

On 17 Dec 2004 09:27:22 -0800, Doug Freyburger <dfreybur@yahoo.com> wrote:
> Dave Hinz wrote: 
>
> Agreed.  Changing network hardware should not have a direct
> effect on a serial line, so something else happened.

As someone else mentioned, this might have been a serial device
rather than an ethernet device.  Would make more sense with it being
a tty type name.

> /etc/getty does login ports that aren't necessarily on serial
> lines.  Figuring out what ttya08 actually is is a good starting
> point.  Then why is there chatter on it now rather than a login
> session.
 
[vbcol=seagreen]
> That won't help.  Error 6 is likely to be the same on any UNIX. 
> #define ENXIO   6       /* No such device or address            */

True, but I was making a point about vague questions getting vague
answers, trying to do so gently.  I'm new at this "tact" thing, and
am just trying it out.  How'd I do?

Sounds like first step is put back in the Serial device that
looked like ethernet and hope for the best, I think.

Dave Hinz

[ Post a follow-up to this message ]

Dave Hinz wrote:
>
> True, but I was making a point about vague questions getting vague
> answers, trying to do so gently. I'm new at this "tact" thing, and
> am just trying it out. How'd I do?

No idea ;^)  Isn't a tact something used to hold a carpet in place?
>From my end, "gently" isn't something I try to do much on UseNet.
Doug the gruff drill sargeant sounding guy

[ Post a follow-up to this message ]

On 17 Dec 2004 12:48:58 -0800
"Doug Freyburger" <dfreybur@yahoo.com> wrote:

> Isn't a tact something used to hold a carpet in place?

Wouldn't that be a tack?

--
Stefaan
--
As complexity rises, precise statements lose meaning,
and meaningful statements lose precision. -- Lotfi Zadeh

[ Post a follow-up to this message ]

It was an Ethernet hub and it also had my Windows Server 2003 hooked to
it. The only change was the hub was moved because, It Was Bad. I replaced it
with a linksys 16 port switch and the Windows Server and Clients work great
but, UNIX not so great.
Just thought I could get some UNIX help here?

Thank you,


"Stefaan A Eeckels" <tengo@DELETEMEecc.lu> wrote in message
news:20041217231003.6f4bf958.tengo@DELETEMEecc.lu...
> On 17 Dec 2004 12:48:58 -0800
> "Doug Freyburger" <dfreybur@yahoo.com> wrote:
> 
>
> Wouldn't that be a tack?
>
> --
> Stefaan
> --
> As complexity rises, precise statements lose meaning,
> and meaningful statements lose precision. -- Lotfi Zadeh

[ Post a follow-up to this message ]

On Fri, 17 Dec 2004 22:54:31 GMT
"Joe" <joe@epix.net> wrote:

>    Just thought I could get some UNIX help here?

The point is that what you report is not typical
(apart from the network hardware, the machine isn't
aware of the change from a hub to a switch, and I've
never seen the error message you've seen as a result
of such a change), plus obviously not related to the
change. As far as I can tell from the info you gave,
you've got a problem with a serial line, not your
network.

Now if you me to do a better stab at diagnosing what
ails your Unix box, please provide the following
information:

1. Details on your Unix box: brand, OS, age etc.
Are you accessing it from a terminal?
2. Details on the error: does it happen when you
rebooted the machine, have you rebooted th
machine at all, what exactly do you mean with
"can't access" (from the network, from the
console, does it boot and then freeze, etc.)
3. Details on your network: do you have any special
network devices such as ethernet serial ports,
older devices that might have problems when
connected to a 10/100Mb/s switch instead of (what
I surmise to be) a 10Mb/s hub. How recent is
your cabling, have you tried other cables, etc.
4. Anything else _you_ can think of that might be
relevant to your problem. Remember I don't know
your network at all.

Just remember that the message you've shown can most
definitely not be caused by replacing a hub by a
switch, unless there's some hardware connected to
your Unix box that provides serial ports over
Ethernet.

And just one thing it could be - if the switch
can do 100Mb/s, and your Unix box can do 100Mb/s,
and your cable is not cat5, your "can't access"
might be caused by a failure to communicate, and
the tty error might be something you've been having
since a long time, it just wasn't noticed.

Take care,

--
Stefaan
--
As complexity rises, precise statements lose meaning,
and meaningful statements lose precision. -- Lotfi Zadeh

[ Post a follow-up to this message ]