Posted on December 14, 2017 2:38 am
 |  Asked by Rayne R
 |  2824 views
RESOLVED
0
0
Print Friendly, PDF & Email

Hi all,

I am facing the problem of not getting the “localhost >” prompt after logging in, be it via SSH or console.

After typing in my password, I get the “Last login: <date> from <IP address>” as per normal, but then it just hangs there.

This happened about 3 days ago, when I tried to login and got an error message about the “/var/core” space being used up. I also didn’t get the prompt after login for a day, and was finally able to access the switch yesterday morning to delete all the “core.XXXX.<timestamp>.Launcher.gz” files in /var/core. However, the problem resurfaced yesterday afternoon till now.

I’m not sure if the 2 are related, but I would greatly appreciate it if anyone could help me with this.

Thank you.

0
Posted by prajwala an
Answered on December 14, 2017 5:44 am

Hi Rayne,

You are not able to login into the switch because a CLI session is not being created. This very likely happens when the Root file system is full, which is not displayed on the login.

Looks like there might be an agent continuously restarting because of which the /var/core directory is getting full.

Hence we recommend you to open a case with support@arista.com so that we shall be able to analyse and root cause the issue.

Best Regards,

Prajwala

0
Posted by Rayne R
Answered on December 18, 2017 1:21 am

Thanks. Before I open a case with Arista, is there anyway I can login to delete the /var/core files now so I can access the switch?

0
Posted by Alexandru
Answered on December 18, 2017 3:46 pm
Hi Rayne, If you are running 4.18 code then you are most likely hitting bug 219202 Introduced in 4.18.0 . Fixed in 4.19.1 , 4.19.2. Release Note: When the /var/log file system is full, new SSH connections might hang until files have been deleted on /var/log. In order to recover the switch you would need to login via console if possible and clear some of the logs for the agent that is crashing from /var/log/agents. If console access is not available then a reload is required in order to recover the switch and regain access.
0
Posted by Rayne R
Answered on December 19, 2017 1:19 am

Hi Alexandru,

Thanks for the suggestion. I am using 4.18.1. However, I’m unable to get a prompt after the login, even via console, and what I’ve read about the “reload” commands require a prompt.

You mentioned “If console access is not available then a reload is required in order to recover the switch and regain access.” How do I do a reload without console access?

0
Posted by Rayne R
Answered on December 20, 2017 5:52 am

I have done a “fullrecover”, reset the switch to factory default, and reconfigured it. Thanks everyone for your suggestions.

0
Posted by prajwala an
Answered on December 20, 2017 6:54 am

Hi Rayne,

 

Since you are not able to get a prompt to run any commands, you will need to perform a hard reload ( Manually plug out the power cable and plug it back ). However please make sure to keep yourself available to login into the switch immediately ( both ssh and console ) as the /var/log directory would get filled up very soon and could cause the same issue once again.

 

Best Regards,

Prajwala

0
Posted by Alexandru
Answered on December 20, 2017 10:16 am

If no management access is available then the only way to recover/reload the switch is to power cycle the unit.

Post your Answer

You must be logged in to post an answer.