1016696 - pbx1.voip.par1 ttyS1 serial console is broken

Status: RESOLVED FIXED

(Infrastructure & Operations :: MOC: Service Requests, task)

Description

[:Atoll]

May 27 22:57:43 pbx1 init: serial (ttyS1) main process (24974) terminated with status 1
May 27 22:57:43 pbx1 init: serial (ttyS1) main process ended, respawning

This is repeating every few seconds ongoing, which will probably complicate any future desire to use a serial console.

Not sure what the usual fix is for this, since I've never seen it before.

Comment 1

[Peter Radcliffe [:pir]]

:justdave, is there anything special about the serial ports on pbx machines? Anything connected there ir is it all through dedicated cards?

I can't think of any reason to use the serial port, since we'd normally use iLO or similar, can we not just disable that tty if this is still an issue?

Comment 2

[Dave Miller [:justdave]]

The iLo card runs console over the serial port instead of creating a virtual display, so yes, it needs to work.  It's just iLo talking to it though.

Comment 3

[Peter Radcliffe [:pir]]

That's not how I understand it, iLO via java or .net gives the same as the screen, not a serial port.

However I can't check this right now because I can't actually get to the remote console. ssh to it says it's in a graphics mode that's unsupported, java won't work with my Linux box with Firefox and since the network isn't routed even if I forward socks with ssh to get my windows VM to the admin hosts in par1 the .net app won't download.

Comment 4

[Dave Miller [:justdave]]

The older iLos used a "VSP" command instead of "REMCONS" for console from the shell version of the iLo management.  The ones with a VSP command connect to a serial port instead of emulating the display.

Comment 5

[Dave Miller [:justdave]]

If it uses REMCONS then this is all moot and I'm not sure what this was all about.

Comment 6

[Peter Radcliffe [:pir]]

It uses remcons. I connected to it, then got the error about the unsupported graphics mode.

Comment 7

[Peter Radcliffe [:pir]]

:justdave - should asterisk be configured to use /dev/ttyS1?
/etc/asterisk/smdi.conf:;smdiport=/dev/ttyS1

/etc/securettys had it listed twice, as ttyS1 and /dev/ttyS1. I've removed the second entry.

/boot/grub/grub.conf has: console=ttyS1,230400 which I don't think is appropriate for a modern HP box, along with /etc/init/ttyS1.conf and other serial console setup.


Looks like that machine was set up for serial console when it isn't actually doing serial console.

Comment 8

[Dave Miller [:justdave]]

The Paris box had a lot of config (way too much config) cloned from the original pbx1 box in sfo1.  I'm willing to bet a bunch of this stuff is carryover from that which didn't get cleaned up.  I know the hardware in Paris also got replaced when the office moved, it could be stuff left over from the machine in the old Paris office.

Asterisk does not have sdmi configured, so the sdmi.conf file doesn't really matter.  That's to let asterisk be put in embedded devices and allow you to have a console, we've never used it.

Comment 9

[Peter Radcliffe [:pir]]

Is any of it in puppet? If not can I clean up what I can find to turn that stuff off? If so I can do that and the next time it is rebooted we can see if that fixes it.

Comment 10

[Peter Radcliffe [:pir]]

Cleaned up serial console references on all current pbx machines. They just need a reboot to reconfigure init and the kernel.

:justdave do the pbx machines get regular reboots?

Affected machines were in par1, yvr1 and akl1

Comment 11

[Dave Miller [:justdave]]

Not really. They're way overdue. Except for Paris and Berlin because they both just had power maintenance.

Comment 12

[Peter Radcliffe [:pir]]

My timing sucks, then :)

Well, when they get rebooted the problem should go away.