1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] Error on LO side this night
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Error%20on%20LO%20side%20this%20night&In-Reply-To=%3C1313659497.13416.17.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003870.html">
<LINK REL="Next" HREF="003873.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] Error on LO side this night</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Error%20on%20LO%20side%20this%20night&In-Reply-To=%3C1313659497.13416.17.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-sysadm] Error on LO side this night">misc at zarb.org
</A><BR>
<I>Thu Aug 18 11:24:57 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003870.html">[Mageia-sysadm] new partition on valstar for binrepo
</A></li>
<LI>Next message: <A HREF="003873.html">[Mageia-sysadm] Possible failure in our update process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3872">[ date ]</a>
<a href="thread.html#3872">[ thread ]</a>
<a href="subject.html#3872">[ subject ]</a>
<a href="author.html#3872">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi,
we have recevied various error messages from alamut ( webserver ) this
morning, around 7h ( CEST ).
According to lost oasis irc log, they had a problem at this moment, with
some others servers down and doing fsck. All our servers ( and those of
zarb.org too ) got rebooted at this time.
On our side, that caused :
- ryu.zarb.org failure ( it was rebooted again by guillaume rousse at
10h15 CEST ). The last error message was about "pci hotplug poweroff"
around 7h15, and that's IMHO correspond to someone pushing the button to
start it or shut it down.
- a error between alamut and valstar. I suspect that alamut being
slightly faster to boot than valstar, it got up before valstar was
ready, thus being unable to get access to it, hence the error message
with "no route to host".
So besides fixing BIOS to boot fast on all server, and getting our own
redundant power supply and datacenter, there is nothing we can do :)
Nice thing : all our server boot fine.
Another nice thing, hobbit works fine to send us alert.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003870.html">[Mageia-sysadm] new partition on valstar for binrepo
</A></li>
<LI>Next message: <A HREF="003873.html">[Mageia-sysadm] Possible failure in our update process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3872">[ date ]</a>
<a href="thread.html#3872">[ thread ]</a>
<a href="subject.html#3872">[ subject ]</a>
<a href="author.html#3872">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
