projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] Services' segfault | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%27%20segfault&In-Reply-To="> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="000223.html"> | |
| 11 | <LINK REL="Next" HREF="000224.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] Services' segfault</H1> | |
| 15 | <B>Andrew Church</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%27%20segfault&In-Reply-To=" | |
| 17 | TITLE="[IRCServices Coding] Services' segfault">achurch at achurch.org | |
| 18 | </A><BR> | |
| 19 | <I>Fri Feb 8 01:45:48 PST 2002</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="000223.html">[IRCServices Coding] Services' segfault | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="000224.html">[IRCServices Coding] Services' segfault | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#222">[ date ]</a> | |
| 27 | <a href="thread.html#222">[ thread ]</a> | |
| 28 | <a href="subject.html#222">[ subject ]</a> | |
| 29 | <a href="author.html#222">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>>><i> This is bizarre, and looks like memory corruption; can you | |
| 35 | </I>>><i> reproduce | |
| 36 | </I>>><i> it consistently? | |
| 37 | </I>><i> | |
| 38 | </I>><i>Not really. As I said, I suppose the machine on which the services are | |
| 39 | </I>><i>running (which also is our main hub server) was probably under attack - | |
| 40 | </I>><i>just like yesterday, *sigh*. | |
| 41 | </I>><i>The whole network froze and other servers (including mine) splitted, and | |
| 42 | </I>><i>when we came back there was no sign of services, just that core file. I | |
| 43 | </I>><i>didn't find anything strange in the logs either. | |
| 44 | </I>><i>I didn't check the cpu load when I logged onto the machine, but I've | |
| 45 | </I>><i>heard of some attacks that manage to rise the load to 100%. Could that | |
| 46 | </I>><i>be the case? | |
| 47 | </I> | |
| 48 | Such attacks are possible, but I doubt those are related to the crash. | |
| 49 | It's more likely the flood triggered a bug somewhere in Services that | |
| 50 | corrupted memory--I've heard reports of such but have never managed to | |
| 51 | track it down. Version 5.0 should be more stable in that regard, I hope. | |
| 52 | ||
| 53 | --Andrew Church | |
| 54 | <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org</A> | |
| 55 | <A HREF="http://achurch.org/">http://achurch.org/</A> | |
| 56 | ||
| 57 | </PRE> | |
| 58 | ||
| 59 | <!--endarticle--> | |
| 60 | <HR> | |
| 61 | <P><UL> | |
| 62 | <!--threads--> | |
| 63 | <LI>Previous message: <A HREF="000223.html">[IRCServices Coding] Services' segfault | |
| 64 | </A></li> | |
| 65 | <LI>Next message: <A HREF="000224.html">[IRCServices Coding] Services' segfault | |
| 66 | </A></li> | |
| 67 | <LI> <B>Messages sorted by:</B> | |
| 68 | <a href="date.html#222">[ date ]</a> | |
| 69 | <a href="thread.html#222">[ thread ]</a> | |
| 70 | <a href="subject.html#222">[ subject ]</a> | |
| 71 | <a href="author.html#222">[ author ]</a> | |
| 72 | </LI> | |
| 73 | </UL> | |
| 74 | ||
| 75 | </body></html> |