Login Error

Question

I upgraded Cirrus this morning to version 4.  It was installed while I was logged into the server and it went without a hitch.  I am a local admin on the server as is everyone using Cirrus.  I can log in and use Cirrus fine but no one else can.  Everyone else gets a message box saying "login error" moments after they see the splash screen.

Help please...

goofyzig · Answer

Thanks so much for posting this. Our Cirrus 4.0 installation (Win2003server) is behaving the exact same way when using Telnet to devices.  We are a Cisco shop and this happens to random devices on every execution.  We noticed the problem when we set up a report to let us know which devices did NOT have the "Login OK" on the Login Status field. The goal being to report every morning on devices that dont have TACACS configured (since Cirrus uses a TACACS account).  This then includes devices with "Login failed: bad password", "Cannot login to device:  bad password", etc, but a lot of them just had the "Login Status" field blank (concerning of itself).

Just like the original poster stated,  it is always a new set of random devices that Cirrus fails to login to, even devices on the SAME LAN as Solarwinds! (thus eliminating connectivity issues, which has its own way of being reported anyhow).   Anyway, I reported this to Solarwinds Support a week ago or so.    I wont bore you with the painful thread of back and forth emails until the issue got proper recognition, but after a complete re-install of Cirrus when it was proven that the problem was randomly consistently repeatable (if such a thing exists) they created two tickets allegedly with the Developers (tickets # 1178, and 1179) to fix this issue. One ticket is for the Telnet issue, the other is for Database flickering (totally separate issue where Cirrus cycles through database connections, including a No Database one, before coming back to the database its supposed to be using).

You know, on an editorial note, I sure hope they fix this ASAP.  Support lost my templates, scheduled jobs, custom reports, now I have to do this all over again for our Non-Cisco devices.  The manpages/manual/admin guide is very vague about how to configure non-Cisco devices with different prompts, so this is going to take me HOURS, HOURS, HOURS of testing.  I followed the instructions for a device with really weird prompts, and Cirrus just kinda hung and wouldn't see the prompts.  I dont get it, and I am kinda upset that Support lost all my work.  BUT,  I just hope these efforts will help to get the Telnet/Login issue fixed for ALL DEVICES,  at least it would have been worth it. I'll keep my fingers crossed they get the right talented developer on this issue because IMHO this is a make or break issue for the Cirrus application.

Also, for everyone's reference regarding the Failed Login problem, here are at least 4 threads I found on the same topic here in Thwack of others experiencing a similar issue:

">    à "Just checked the report from last night and while there are some of the same switch that failed yesterday there are others that  were all right yesterday and have failed today."

">

">   à "If I see another 'Login failed : bad password' again, I'm liable to go postal. "

">

leemcclendon · Answer

These are steps that you can follow to provide additional information to our support team:

1) From the File menu select Settings->Logging and enable the logging for the security module

2) Close Cirrus and try to login with one of the accounts that is having the problem

3) A file named General.log will be created in the Logging subdirectory of the directory where Cirrus is installed.  Tell the support representative that you have this information when you open the support ticket.

Answers to these questions will also help with debugging the problem:

Are the accounts that you are using domain accounts or machine-local accounts?  If they are domain accounts, are they from the same domain as the computer where Cirrus is installed or from a trusted domain?  Do you know which domain and forest mode you are using (mixed, native, Windows Server 2003)?

Haley · Answer

The development team is currently looking into this issue.  I also recommend creating a support ticket at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b and reference that you spoke with Haley within Thwack.