- Wake up @ 9:30 this morning to find a text message from my hombre PV saying that OC3D is down.
- Ping server, no response. Ping IDNet server - working fine (so unlikely its a network issue.
- Contact IDNet to see if they can get on to it via networked KVM. No Joy. Next step, get server rebooted.
- 11:30 server gets restarted. Still not wback up and running.
- 12ish, begin 90minute train journey to visit server. Take with me two bags of spare parts (more than enough to build a brand new server).
- Get to server just after 1:30 only to find that it is up and running fine! However, network status in control panel reads: "Limited or no connectivity"
- Plug server into another switch, BAM everything works again. Breathe a sigh of relief and go home.
- Get home to find that when the server was restarted earlier in the day it corrupted a whole load of databases. Fix databases and bring website back up.
- Reaslise that last nights backup didnt complete (as server crashed about midnight when they start). So started it manually.
- Website performance goes to sh*t. Strange as CPU is only 5% utilised and network is less than 10% utilised....hmm
- Spend next 2hrs reading up on network performance issues, test a load of command line stuff...no joy.
- Finally check event logs and find that network card isn't auto-detecting network speed and instead has chosen to run at slowest possible setting.
- Down several glasses of JD before finally bucking up the courage to manually change the network speed setting to full duplex at the risk of having to take another trip back up to the server again if it goes T1ts up.
I had a great Saturday...how about you guys?
- Ping server, no response. Ping IDNet server - working fine (so unlikely its a network issue.
- Contact IDNet to see if they can get on to it via networked KVM. No Joy. Next step, get server rebooted.
- 11:30 server gets restarted. Still not wback up and running.
- 12ish, begin 90minute train journey to visit server. Take with me two bags of spare parts (more than enough to build a brand new server).
- Get to server just after 1:30 only to find that it is up and running fine! However, network status in control panel reads: "Limited or no connectivity"
- Plug server into another switch, BAM everything works again. Breathe a sigh of relief and go home.
- Get home to find that when the server was restarted earlier in the day it corrupted a whole load of databases. Fix databases and bring website back up.
- Reaslise that last nights backup didnt complete (as server crashed about midnight when they start). So started it manually.
- Website performance goes to sh*t. Strange as CPU is only 5% utilised and network is less than 10% utilised....hmm
- Spend next 2hrs reading up on network performance issues, test a load of command line stuff...no joy.
- Finally check event logs and find that network card isn't auto-detecting network speed and instead has chosen to run at slowest possible setting.
- Down several glasses of JD before finally bucking up the courage to manually change the network speed setting to full duplex at the risk of having to take another trip back up to the server again if it goes T1ts up.
I had a great Saturday...how about you guys?