Very strange. Remote serial console access works for a few days and then stops working. The config is good (set up by SM tech).

(Hardware: Gigabyte SuperCeleronMarkII )

Here is what I get: (sample username and ip used)

% ssh C12345-12345@67.19.x.xx

C12345-12345@67.19.x.xx's password:
Connecting to ROD. Use ^# to escape.

Now, if the serial console is working properly once I see the ROD escape message, if I press Ctrl-D I will get a login prompt. If it isn't working properly I'm stuck at the ROD message. Escaping with ^# works, but reconnecting with enter brings me back to a stuck prompt

However, if I issue the keystrokes to login as root, I am logged in.

Jan 24 14:47:12 login: ROOT LOGIN (root) ON ttyd0

Still at a stuck prompt at the ROD message I can issue commands and they are executed like top:

root d0 - 2:47PM - top

But my prompt is still stuck at the ROD message: (no top output)

Connecting to ROD. Use ^# to escape.

(issuing the q keystroke after executing top does not terminate the top command though making it appear that top isn't getting my keystroke)

So it seems that I am connecting and logging in and "semi" able to execute commands but the reaction from the prompt is nothing.

Any other FreeBSD admins seeing anything similar to this? Could it be some odd parity setting or something weird with this hardware? If so, why would it work for a few days and then stop?

Anyway, if anyone would care to offer some guesses I'd be obliged.

Thanks.

JC

Sorry I know its bad form to respond to your own post but I have solved my problem.

Commented this line in syslog.conf:

#*.err;kern.debug;auth.notice;mail.crit /dev/console

With console output being redirected to the serial port, messages must get buffered and eventually wedge the port

As soon as I sent a HUP to syslogd the serial remote console came alive.

not bad form, if anybody else has a similar problem they now have a possible solution =)