On Fri, 2005-06-03 at 09:18 -0500, Rob W. wrote: > I have just installed ircu2.10.11.07 on both of my servers. Both are running > FreeBSD 4.11-STABLE. I have setup one as a hub and one as a leaf. I got the > config from the /doc/ircd.conf.sample and edited it to meet my specs for my > network. I can connect to each ircd once they are up and running with no > problems. I can oper up on both also. The problem that I am having is when I > go to connect the 2 ircds together, the hub ircd core's and a > ircd.(somenumbers).core show's up in my /lib dir. I have re-compiled several > times, changed the configs, tried running it with the bare bone > configuration and yet it still cores on me. Any help is appreciated.
(As a reminder, please CC coder-com@undernet.org on your responses, so that everyone can be kept in the loop...) I'm afraid this doesn't give us enough information about what your problem might be. It might be related to this note: http://sourceforge.net/forum/forum.php?forum_id=249864 (Certain malformed configuration lines may result in server crashes) If the information given there doesn't help you fix your ircd, you should send a stack trace of your cores to [EMAIL PROTECTED] or open a bug tracker item (http://sourceforge.net/tracker/? func=add&group_id=63470&atid=504080) and include the stack traces there. I have included a short how-to on generating stack traces: Most bugs manifest themselves as server crashes. When the server crashes, a core file is placed into the server's data directory--generally the directory containing the server's configuration file. On most systems, this file is named "core", but some systems--notably FreeBSD and perhaps other BSDs--give it a name that ends with ".core". This file contains an enormous amount of potentially useful information. When a server crashes, the first, most important piece of data to include with a bug report is the server version. The next most important piece of data is what you did (if anything) to cause the server to crash. The remaining critical information is a stack trace, which can be extracted from the core file through the procedure given here. *Never* send the core file around--it will contain sensitive information such as passwords, and isn't useful on any system other than the one which generated it anyway. Instead, rename the file and save it until the developers are finished with it. To extract a stack trace from a core file, you must have gdb on your system. Other debuggers are acceptable, if you already know how to use them, but it is my experience that gdb is the easiest to use. The first step is to start gdb with the command "gdb <binary> <core>"--where <binary> is the path to the server binary and <core> is the path to the saved core file. For instance, if your server binary is /home/irc/bin/ircd and the core file is /home/irc/conf/core.1, then you would execute the command "gdb /home/irc/bin/ircd /home/irc/conf/core.1". The debugger will start up and print out a short summary of information, then present you with a prompt that looks like "(gdb)". To generate a stack trace, give gdb the command "bt full" (short for "backtrace full"). When the trace is completed, simply type "quit" to exit the debugger, then include *all* of the information that gdb printed out in your bug report. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Coder-com mailing list Coder-com@undernet.org http://undernet.sbg.org/mailman/listinfo/coder-com
