ipmitool: how to deal with frozen SOL session

7,723

ipmitool sol deactivate is supposed to solve this. But from your question it looks like you have some problems with serial console on the host.

Share:
7,723

Related videos on Youtube

Rohanil
Author by

Rohanil

I am a self-taught Backend developer. My educational background is in Electrical Engineering. I did my specialization in Signal Processing which is equivalent to Data Processing. And from there, I got interest in software development. I have been working as a software developer for the more than 6 years. I worked with Python for the first 2 years. Then I got into Golang for 2 years. I have experience using various tools and frameworks. I have worked professionally using flask, postgresql, mongodb, docker, celery, kafka, influxdb, elasticsearch, git, jenkins, php, javascript, vuejs.

Updated on September 18, 2022

Comments

  • Rohanil
    Rohanil almost 2 years

    I use ipmitool SOL session to get console logs from remote server. Initially session is responsive. If I hit enter, I can see login message to remote server like below.

    [SOL Session operational.  Use ~? for help]                                                                                                                               
    
    <hostname> login:
    

    But if I don't hit enter after activating session and try to press enter or any key, it does not do anything. I can see only this line:

    [SOL Session operational.  Use ~? for help]
    

    I am not sure if the session becomes frozen or not. I can see help after pressing ~? but it is not helpful to resolve the issue. I don't see that login message again.

    I create SOL sessions by using this command:

    ipmitool -I lanplus -U <ipmi-username> -P <ipmi-password> -H <ipmi-ip> sol activate
    

    Is there way to generate some logs on this session without shutting off remote server ? And what are the ways to deal with frozen sol sessions ?

    • rajaganesh87
      rajaganesh87 almost 7 years
      I don't think it is frozen. The terminal displays characters only when it receives a text from the client. Since login screen is not sending any data, it appears to be frozen.