Another maintenance break..

[Undesirable]

Wooooohoooo:rolleyes:

[Kami]

STATUS


Central enterprise server is down!

Cache rmi://de-priv-14:2600/SHARED_CACHE seems to be dead!


--------------------------------------------------------------------------------

PROBLEMS


Some critical problems were found. If you just rebooted the site, wait for at least three minutes
and load this page again to check all services have started up. Cures for the problems listed below:







Enterprise server down

Because the whole site is down, best idea is to run bootall.sh-scripts on all
the servers. Remember to give the enterprise server about three minutes to start
up before checking that the site works. To reboot only enterprise-server:

ssh [email protected]
cd /home/fuse/enterprise_server
./fuse-enterpriseserver stop
./fuse-enterpriseserver start




Cache dead:

if a cache is dead, and it is peak time, please reboot all
the services. Otherwise services keep being strained.

To reboot only the cache:

ssh aapo@de-priv-14:2600
cd /home/fuse/shared_cache
./fuse-cache stop
./fuse-cache start



Apparently thats what a matience break looks like on that page that was posted on here.


----------------------------------------------------------------------------------------------------------------------


STATUS


Enterprise server ok (1) - got reference.

Enterprise server ok (2) - got units, proxies and peers.

Proxy-servers
Average proxy load: NaN


Peer-servers
Average peer load: 0.0

Peer: de-priv-14: 4053 load=0.0
Peer: de-priv-14: 4048 load=0.0
Peer: de-priv-14: 4047 load=0.0
Peer: de-priv-14: 4049 load=0.0
Peer: de-priv-14: 4050 load=0.0
Peer: de-priv-14: 4052 load=0.0
Peer: de-priv-14: 4054 load=0.0
Private room servers missing! There should be 8 but only 4 alive.

Cache rmi://de-priv-14:2600/SHARED_CACHE seems to be fine.


--------------------------------------------------------------------------------

PROBLEMS


Some critical problems were found. If you just rebooted the site, wait for at least three minutes
and load this page again to check all services have started up. Cures for the problems listed below:






Possibly misbehaving peer (de-priv-14:4053 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./ stop
./ start




Possibly misbehaving peer (de-priv-14:4048 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./fuse-peer_b.sh stop
./fuse-peer_b.sh start




Possibly misbehaving peer (de-priv-14:4047 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./fuse-peer_a.sh stop
./fuse-peer_a.sh start




Possibly misbehaving peer (de-priv-14:4049 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./fuse-peer_c.sh stop
./fuse-peer_c.sh start




Possibly misbehaving peer (de-priv-14:4050 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./fuse-peer_d.sh stop
./fuse-peer_d.sh start




Possibly misbehaving peer (de-priv-14:4052 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./fuse-peer_f.sh stop
./fuse-peer_f.sh start




Possibly misbehaving peer (de-priv-14:4054 ):

If it is short time (less than 2 hours) from last reboot of the peer,
it is probably working ok IF the symptom is "exceptionally small load".
If symptom is "exceptionally long time before bootup", you should
reboot it.

To boot:
ssh aapo@de-priv-14
cd /home/fuse/
./ stop
./ start



Private room server count does not match

If there are more than 8 servers up, it is not critical issue and better
to leave for next morning.

To keep the private room load balancing in sync, it is better to
reboot them all. So, go to following servers and run bootall.sh:
fuse-sun5.kultakalaglobal.com




Apparently that means, they got issues!

[Piipp]

Let's hope there's another new rare on the way!

[Kami]

That was a quick matinence break.

My rooms work now! \o/