sudo not available after configuring ipmi serial over lan

Jordan Caraballo jordancaraballo87 at gmail.com
Thu Nov 8 12:40:56 UTC 2018


It hangs. No output at all. Latest testing showed that if I do:

# sudo su -

And hit Ctrl-C two times I get the password prompt, however, when I enter
the password it ignores it ( no error message).

/var/log/auth.log just records that the user executes the “su -“ command.
Just to be clear, when using normal console or kvm, this works fine.

On Thu, Nov 8, 2018 at 7:27 AM Ronald Klop <ronald-lists at klop.ws> wrote:

> On Wed, 07 Nov 2018 23:56:26 +0100, Jordan Caraballo
> <jordancaraballo87 at gmail.com> wrote:
>
> > Hi guys,
> >
> > After configuring ipmi serial over lan console, I am not being able to
> > execute any command related to sudo; not even "sudo su -". I am using
> > ttyu0
> > and COM1 on a Dell R530. Everything regarding receiving output and typing
> > at the serial console is fine; the only command not working is sudo.
>
>
> What do you mean by 'not working'? Is there an error message? Does it
> hang? Do you get logged out?
>
> Regards,
> Ronald.
>
>
> >
> > Any ideas? Below are the configurations.
> >
> > /etc/ttys
> >
> > # Serial terminals
> > # The 'dialup' keyword identifies dialin lines to login, fingerd etc.
> > #ttyu0  "/usr/libexec/getty 3wire"      vt100   onifconsole secure
> > ttyu0   "/usr/libexec/getty std.115200" vt100   on          secure
> > ttyu1   "/usr/libexec/getty 3wire"      vt100   onifconsole secure
> > ttyu2   "/usr/libexec/getty 3wire"      vt100   onifconsole secure
> > ttyu3   "/usr/libexec/getty 3wire"      vt100   onifconsole secure
> > # Dumb console
> > dcons   "/usr/libexec/getty std.9600"   vt100   off secure
> >
> > /boot/loader.conf
> >
> > # ipmi enabled
> > ipmi_load="YES"
> > # ipmi configurations
> > boot_multicons="YES"
> > boot_serial="YES"
> > # serial configurations for COM1
> > console="comconsole,vidconsole"
> > comconsole_speed="115200"
> > comconsole_port="0x3F8"
> > hint.uart.0.flags="0x00"
> > hint.uart.2.flags="0x10"
> >
>
-- 
Jordan


More information about the freebsd-questions mailing list