mcdonald@AEDC-VAX.AF.MIL (06/29/91)
We have been having two problems on our 4D240GTX lately: 1. getting et0: transmit: no carier messages 2. NeWS server dying when we try to log in I was wondering if #2 was related to #1. I was also wondering what could be causing them. The following is an entry from my SYSLOG file. ------------------------------------------------------------------------------ Jun 28 12:28:20 ccfiris grcond[8077]: In limbo Jun 28 12:28:24 ccfiris grcond[8077]: Alive Jun 28 12:28:24 ccfiris grcond[8077]: CIO: carrier Jun 28 12:28:24 ccfiris grcond[8077]: CIO: et0: transmit: no carrier Jun 28 12:28:24 ccfiris grcond[8077]: CIO: et0: transmit: no carrier Jun 28 12:28:24 ccfiris grcond[8077]: CIO: dks0d1s0: Directory 3 is corrupted (001768) Jun 28 12:28:24 ccfiris grcond[8077]: CIO: et0: transmit: no carrier Jun 28 12:28:24 ccfiris grcond[8077]: CIO: NeWS: bus error signal received Jun 28 12:28:24 ccfiris grcond[8077]: CIO: Jun 28 12:28:24 ccfiris grcond[8077]: CIO: gm-2 (configured for IP7/9) 1.14+ Jun 28 12:28:24 ccfiris grcond[8077]: CIO: Jun 28 12:28:24 ccfiris grcond[8077]: CIO: DEBUG_NOISE at 0x9806BDB2 Jun 28 12:28:24 ccfiris grcond[8077]: Child process /bin/news_server terminated by signal 6 Jun 28 12:28:25 ccfiris grcond[8077]: Restoring PROM textport microcode ------------------------------------------------------------------------------ I previously posted a question about the transmit no carrier problem; the responses were all related to whether our ethernet cable was attached/ unplugged, etc. ; our network technicians checked our lines, and they all checked out fine. I am assuming our ethernet board has a problem. We have just placed a call in to TAC about it. Any hints as to what these mean/what the problem is? vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv | Kenneth M. McDonald * OAO Corp * Arnold Engineering Development Center | | MS 120 * Arnold AFS, TN 37389-9998 * (615) 454-3413 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNET: mcdonald@aedc-vax.af.mil LOCAL: c60244@ccfiris
mcdonald@AEDC-VAX.AF.MIL (06/29/91)
I previously posted a message stating that my window manager dies period-
ically. I was wondering if there was any way of getting it back up
without rebooting the machine?
Symptoms: Logged in working fine. Log off, the login prompt comes
up. Type in username/passwd screen blacks out, then
returns to the login prompt with the message:
the window manager (/bin/news_server) aborted (status 0x6)
Any way to restart without rebooting after this occurs?
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
| Kenneth M. McDonald * OAO Corp * Arnold Engineering Development Center |
| MS 120 * Arnold AFS, TN 37389-9998 * (615) 454-3413 |
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNET:
mcdonald@aedc-vax.af.mil
LOCAL:
c60244@ccfiris