Network error : Connection timed out problem in putty

[newuploader]

I've just updated server using this 'yum -y update'

and then I reboot the server 'shutdown -r 0'

when I try to restart the session or new session, putty gives me this fatal error saying 'Network error : Connection timed out problem'

what to do now?

 

[XSLTel]

means your server is not booting may be a kernel panic, or your server network is down

 

[Ivan]

basically you're screwed. System doesn't boot up properly (at least ssh is not starting), and basically the only way to fix it is to go to datacentre, plug keyboard in and see what's going on. You can use KVM as well, but not many hosts offer it (none of those "hosting for 3$/month. warez allowed!" advertised at wjunction do ). Some hosts let you use netboot option, where you boot using different kernel than the one you have installed on your server....

 

[newuploader]

how will it screwed only for rebooting it?

what to do now, it just says

"Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting...
Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting...
Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting..."

but never connects to my server

 

[Ivan]

how will it screwed only for rebooting it?

what to do now, it just says

"Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting...
Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting...
Connected...

Disconnected... [Cause: Connection has timed out.]
Connecting..."

but never connects to my server

Like i said earlier - your system is not starting properly. Most likely it's something silly, like having to press enter at boot screen to choose newly installed kernel from pop-up or sth like that. This kinda gets complicated if PC you need to press enter on is thousands of kilometers away :P

 

[newuploader]

yeah! what to do now, I promised my friend our site will be up in 2-3 hours and got this shit when I tried to reboot :'(

 

[Ivan]

yeah! what to do now, I promised my friend our site will be up in 2-3 hours and got this shit when I tried to reboot :'(

Try to contact your host - they should be able to fix it if they're competent.

 

[newuploader]

yea I've put a support ticket and waiting for there reply..

It's weird, getting problem just for rebooting the server? isn't that shitty, reboot was the important process to install sborg after updating the server and it's started showing this shitty fatal error

 

[Ivan]

yea I've put a support ticket and waiting for there reply..

It's weird, getting problem just for rebooting the server? isn't that shitty, reboot was the important process to install sborg after updating the server and it's started showing this shitty fatal error

you used "-y" switch, meaning yum confirms every actions automatically - next time you should update without that switch, as it sometimes proposes very verid combinations to solve dependencies conflicts ( i still remember apt-get wanted me to uninstall gnome and install kde to solve some dependencies problem in small application) or updates stuff that shouldn't get updated (boot managers, ssh server etc.

 

[newuploader]

what should I do, I just did what they told to do, that wasn't my own

doing the exact thing as they said also giving me trouble, WTH :'(

 

[Ivan]

what should I do, I just did what they told to do, that wasn't my own

doing the exact thing as they said also giving me trouble, WTH :'(

Those instructions work...most of the time.
It's just that yum sometimes finds some crazy solutions to simple package dependency conflict, which basically throws whole system upside down...
If you don't use "-y" switch you can look what changes it is proposing and accept or deny them.

 

[newuploader]

Those instructions work...most of the time.
It's just that yum sometimes finds some crazy solutions to simple package dependency conflict, which basically throws whole system upside down...
If you don't use "-y" switch you can look what changes it is proposing and accept or deny them.

hmm,.. hope this gets done soon, am waiting my host to solve this problem :'(

 

[don19]

the sounds like your server public ip not responding either ?

 

[Sonic]

reboot

never shutdown. you can shutdown/boot your server if it have KVM

send a email to datacenter to boot the server again