Dead Men Walking

Old Server Admin Section => Archived Topics => CS Admins => Topic started by: Hippy on August 13, 2006, 10:41:11 PM

Title: Server reboot.
Post by: Hippy on August 13, 2006, 10:41:11 PM
Can one of the senior admins give the servers a reboot please? It's a tad laggy.
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 09:21:04 AM
I'll do it once I get home today.
Title: Server reboot.
Post by: JB on August 14, 2006, 10:54:46 AM
Rcon exit?
Title: Server reboot.
Post by: Hippy on August 14, 2006, 04:47:26 PM
Doesn't that just turn the server off?
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 04:59:26 PM
All servers rebooted.
Title: Server reboot.
Post by: MAD_ness on August 14, 2006, 05:00:40 PM
Quote from: JBRcon exit?

we did that before... and yes..it DOES just turn the server off .....
 
it was only rebooted after a phone call to Oldie ... :blush2:
Title: Server reboot.
Post by: Hippy on August 14, 2006, 06:10:04 PM
Quote from: BlueBallAll servers rebooted.

Thanks it doesn't seemed to have helped. Im getting 50-60 ping, sadako gets a quicker connection than i do. <_<
Title: Server reboot.
Post by: JB on August 14, 2006, 06:11:04 PM
Both Exit and Quit should automatically restart servers.  Least it used to for years and years.  Sure it wasn't a different command?  Or you didn't wait long enough for it to come back up ?
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 07:23:38 PM
Quote from: HippyThanks it doesn't seemed to have helped. Im getting 50-60 ping, sadako gets a quicker connection than i do. <_<
Doris had poor pings on Fri night. I think you have a connection issue between yourselves and the servers. Can you do a tracert to 87.240.138.21 and paste it here to see if we can see any issues?

My tracert gives:
=============

C:\>tracert -d 87.240.138.21

Tracing route to 87.240.138.21 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms     9 ms     9 ms  10.125.64.1
  3    10 ms     9 ms     9 ms  80.195.0.6
  4    22 ms    21 ms    22 ms  62.30.251.18
  5    21 ms    23 ms    20 ms  194.117.136.209
  6    24 ms    23 ms    22 ms  194.117.136.178
  7    21 ms    21 ms    22 ms  194.117.136.158
  8    21 ms    23 ms    22 ms  194.117.136.146
  9    22 ms    22 ms    23 ms  195.66.224.151
 10    24 ms    22 ms    23 ms  87.240.128.2
 11    22 ms    28 ms    24 ms  87.240.128.50
 12    24 ms    24 ms    26 ms  87.240.138.21

Trace complete.

C:\>
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 07:27:36 PM
Quote from: JBBoth Exit and Quit should automatically restart servers.  Least it used to for years and years.  Sure it wasn't a different command?  Or you didn't wait long enough for it to come back up ?
I just did an "rcon exit" on Meathook. It shutdown the server and I had to manually restart it after 2 mins.
Title: Server reboot.
Post by: Hippy on August 14, 2006, 07:46:22 PM
How do i do that trace thing that you did?
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 08:34:43 PM
Quote from: HippyHow do i do that trace thing that you did?
Open a "Command Window/DOS Prompt" whatever you prefer to call it.

Type "tracert -d 87.240.138.21" without the quotes and press ENTER

Use your mouse to draw a "box" around the resulting data then press ENTER which will copy it to the clipboard for pasting in the forum.
Title: Server reboot.
Post by: Hippy on August 14, 2006, 10:25:57 PM
QuoteOpen a "Command Window/DOS Prompt

Thats the black box? ok how do i open that?
Title: Server reboot.
Post by: Anonymous on August 14, 2006, 10:49:13 PM
Quote from: HippyThats the black box? ok how do i open that?
Press the "window" key on bottom left of keyboard between Ctrl and ALt and while pressing it press the "r" key as well. This will open a "Run" dialog (r for run see).

Type "cms" without the quotes then follow previous instructions when the (cough) black box appears ;)
Title: Server reboot.
Post by: OldBloke on August 15, 2006, 12:07:45 AM
Quote from: BlueBall... Type "cms" without the quotes then follow previous instructions when the (cough) black box appears ;)

Small but important typo ... "cmd" is what you should type - no quotes.
Title: Server reboot.
Post by: Anonymous on August 15, 2006, 09:17:56 AM
Quote from: OldBlokeSmall but important typo ... "cmd" is what you should type - no quotes.
Good point well presented :blush2:
Title: Server reboot.
Post by: TeaLeaf on August 15, 2006, 10:05:48 AM
...and there was I thinking "oh, I've been using 'cmd' and doing it wrong all these years" and was off to try 'cms' :norty:

TL.
Title: Server reboot.
Post by: Anonymous on August 15, 2006, 10:44:00 AM
Quote from: TeaLeaf...and there was I thinking "oh, I've been using 'cmd' and doing it wrong all these years" and was off to try 'cms' :norty:
 
TL.
Let me know how you get on :unsure:
Title: Server reboot.
Post by: MAD_ness on August 15, 2006, 10:48:31 AM
How do ya stop it from doing 5 jumps then closing the window ?
Title: Server reboot.
Post by: Hippy on August 15, 2006, 02:43:01 PM
C:\>tracert -d 87.240.138.21

Tracing route to 87.240.138.21 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    19 ms    20 ms    20 ms  195.93.23.169
  3    20 ms     *        *     195.93.17.190
  4    21 ms    19 ms    19 ms  172.17.169.92
  5    20 ms    20 ms    50 ms  195.93.31.30
  6    21 ms    20 ms    19 ms  66.185.143.197
  7    21 ms    20 ms    20 ms  213.206.157.153
  8    49 ms    49 ms    50 ms  82.195.191.26
  9    50 ms    51 ms    50 ms  217.118.119.57
 10    50 ms    50 ms    50 ms  84.233.152.162
 11    50 ms    49 ms    49 ms  217.118.119.34
 12    50 ms    50 ms    49 ms  84.233.186.90
 13    55 ms    56 ms    56 ms  87.240.128.50
 14    54 ms    53 ms    54 ms  87.240.138.21

Trace complete.
Title: Server reboot.
Post by: Anonymous on August 15, 2006, 05:56:38 PM
Your problem seems to relate to the jump from node 7 to node 8. The IP Addresses resolve as:

sl-gw23-lon-12-0.sprintlink.net [213.206.157.153] <- Node 7
sle-intercom-3-0.sprintlink.net [82.195.191.26] <- Node 8

which suggests to me that the problem lies within Sprintlink

Interestingly, I cannot tracert to either of the above IP addresses as it keeps timing out!