Topic: Cannot access console after update

[AndySabo]

I often log into my server from firefox and do the suggested updates.  After my last update the server crashed and I have been unable to access it from any computer on the network.  Today I hooked a monitor and keyboard to it and booted it up to see if I could fix the problem.  Well,, it is asking for a log in and password.  when I put it in there it just goes back to "first login"  if I put in anything else it says "login incorrect" and asks for it again, so I put in the right info and it just goes straight back to "first login".   I have never had this issue before.

[uniqsys]

I have never had this issue before.

As a usual response: please report all bugs via the bug tracker.  Include more details on the installation and which packages were upgraded too.

I have never seen this response either.  You are cold booting and trying to login as "root" with the root password right?  Sounds like signal-event post-upgrade and/or signal-event reboot didn't work as expected.

If you can login as root, I suggest that you try to manually invoke them with

Code: [Select]

signal-event post-upgradeand

Code: [Select]

signal-event reboot

[AndySabo]

if the bug tracker was not such a convoluted process I would go there.  I cannot log in as root, admin, me or anything else. from what I understand root only takes you to the linux running under the console anyway.  I need to access the console and get the server running again.

[Stefano]

if the bug tracker was not such a convoluted process I would go there.  I cannot log in as root, admin, me or anything else. from what I understand root only takes you to the linux running under the console anyway.  I need to access the console and get the server running again.

then you are alone.. if you wish help you have to be more collaborative.. start with raising a bug..

then boot your server with SME's cd in rescue mode, try to mount your installation and start looking in /var/log/messages for something..

ciao
Stefano

[uniqsys]

if the bug tracker was not such a convoluted process I would go there.

Oh contraire mon ami, it is not a convoluted process.  I agree with Stefano. 

  I cannot log in as root, admin, me or anything else. from what I understand root only takes you to the linux running under the console anyway.   I need to access the console and get the server running again.

I don't know what you mean by "running under the console". Nothing that I know of runs under a console. SME console accesses certain functions that enable you to configure and manage some features of the OS. Please follow Stefano's suggestions and we will try to help.  His advice is the next step I would follow.

[AndySabo]

Thank you for your assistance.  I do not have any cd's, I downloaded my SME server.  I will sign up an account on the bug place and see if I can get through it.  I had tried to search it for an answer but it is an amazing maze of tangled up data that I could not interpret.

[CharlieBrady]

I had tried to search it for an answer but it is an amazing maze of tangled up data that I could not interpret.

You do not need to interpret anything in the bug tracker. You just need to describe exactly what you did, and exactly what you are seeing. And you will be asked to do various things, and to report back what you see. We developers will attempt to determine what went wrong and how it can be fixed.

[CharlieBrady]

I do not have any cd's, I downloaded my SME server.

I'm quite curious about that. The most usual way to create an SME server is to download an iso image, burn it to a CD, and boot from a CD in order to install the software on a computer. So it is quite usual that everyone with an SME server will have a CD.

[cactus]

I will sign up an account on the bug place and see if I can get through it.  I had tried

After you have created your bug report please post a reference to that bug here for future readers. Thanks.

[Stefano]

I do not have any cd's, I downloaded my SME server. 

exactly, what did you download? an iso? a vmware/virtualbox/whatever virtual machine image?

Stefano

[SmartSteve]

Hmm this has happened to me twice on two different machines. Once on 7.3 and recently when I ran up a new 7.4 fresh install. It seemed like the root/admin password is overwritten. I had to manually boot single and go in and recreate the root password then reboot then I could get in and recreate the admin password. Now the 7.3 it happened out of the blue BUT I think it was during a yum update. On the 7.4 I was busy updating and installing packages and only after I had done a heap of updates did I do the sig-event post-upg -> sig-event reboot. So as for what exactly caused it I'm not sure. Once I recreated the root password it hasn't happened since. I haven't bugzilla'd it as I was not sure what caused it thus very hard to pinpoint.

Hope that either helps or gives encouragement.

For the record I have 3 x 7.4 and 2 x 7.3 CDs because I keep misplacing them.

Steve B

[Stefano]

I haven't bugzilla'd it as I was not sure what caused it thus very hard to pinpoint.

you have not to think if it is a bug or how to explain it.. open a bug, and If you feel scared by bugzilla, read this

Ciao
Stefano

[CharlieBrady]

I have never seen this response either.  You are cold booting and trying to login as "root" with the root password right?  Sounds like signal-event post-upgrade and/or signal-event reboot didn't work as expected.

The signal-event reconfigurations don't do anything with root or admin passwords, or change anything which would affect ability to log on.

[AndySabo]

Can you please explain how you did the "manual boot single" and how you changed the password ?

[janet]

AndySabo

There is alot of useful info here
http://wiki.contribs.org/Category:Howto

Please read the Howtos particularly
http://wiki.contribs.org/Booting
and look for Rescue mode