Eggdrop doesn't show up on IRC

ljesh · Post by **ljesh** » Sat Apr 21, 2007 12:31 am

Hello everyone.

I just installed Fedora Core 6 and eggdrop (latest version).
I tryed to start it with ./eggdrop -m eggdrop.conf but although the process stays active and it says the eggdrop has started, he doesn't show up on IRC.
I killed that process and tryed again, but this time the same command only -n added in the end. I can see the things getting activated, I can see the eggdrop connectin... and I check on IRC, he is there. EVERYTIME I start it with -n option, he shows up on IRC. Without it never shows up.

What is the cause of my problem and how can I fix it please?

Thanks in advance for your kind help.

DragnLord · Post by **DragnLord** » Sat Apr 21, 2007 1:50 am

You should have a logfile set for the bot in the conf file

Code: Select all

logfile mcoxsb * "logs/eggdrop.log"

Hopefully this will give you some useful information.

StarteR2 · Post by **StarteR2** » Sun Apr 22, 2007 1:15 pm

This is actually is a serious problem that I have too and I do have a log file and it says:

Writting Userfile
Writting Channel File

and than when i kill it it add something with TERMSIGNAL.

as ljesh already says in -n it shows up. There is a solution with the -n option you can run it with -n in background but its a very crappy solution. This is how i do it

Code: Select all

./eggdrop -n YTTRIUM.conf 2>&1 &

Now. i found another solution
RPM:
http://download.fedora.redhat.com/pub/e ... l5.ppc.rpm
Problem with it is:

Code: Select all

   1.
      *** glibc detected *** ./eggdrop: free(): invalid pointer: 0x089e1060 ***
   2.
      ======= Backtrace: =========
   3.
      /lib/libc.so.6[0x9ab09d]
   4.
      /lib/libc.so.6(cfree+0x90)[0x9ae6f0]
   5.
      ./eggdrop[0x8066c42]
   6.
      ./eggdrop[0x807069a]
   7.
      /lib/libc.so.6(__libc_start_main+0xdc)[0x95af2c]
   8.
      ./eggdrop[0x804a3e1]
   9.
      ======= Memory map: ========
  10.
      *** glibc detected *** ./eggdrop: double free or corruption (!prev): 0x088704e8 ***
  11.
      ======= Backtrace: =========
  12.
      /lib/libc.so.6[0x54a09d]
  13.
      /lib/libc.so.6(cfree+0x90)[0x54d6f0]
  14.
      ./eggdrop[0x8065844]
  15.
      /eggdrop.old/modules/share.so[0x18941a]
  16.
      ./eggdrop[0x80687f9]
  17.
      ./eggdrop[0x8065566]
  18.
      ./eggdrop[0x80707df]
  19.
      /lib/libc.so.6(__libc_start_main+0xdc)[0x4f9f2c]
  20.
      ./eggdrop[0x804a3e1]
  21.
      ======= Memory map: ========
  22.
      *** glibc detected *** ./eggdrop: double free or corruption (!prev): 0x09669400 ***
  23.
      ======= Backtrace: =========
  24.
      /lib/libc.so.6[0x9ab09d]
  25.
      /lib/libc.so.6(cfree+0x90)[0x9ae6f0]
  26.
      ./eggdrop[0x8065844]
  27.
      /eggdrop.old/modules/share.so[0xdbf41a]
  28.
      ./eggdrop[0x80687f9]
  29.
      ./eggdrop[0x8065566]
  30.
      ./eggdrop[0x80707df]
  31.
      /lib/libc.so.6(__libc_start_main+0xdc)[0x95af2c]
  32.
      ./eggdrop[0x804a3e1]
  33.
      ======= Memory map: ========

I will try the RPM for 1.6.17 now.

What I have realised is that nothing blocks the eggdrop. It just wont open a proper port. You CANT even TELNET to it.[/code]

StarteR2 · Post by **StarteR2** » Sun Apr 22, 2007 1:19 pm

Follow up.

Same problem with 1.6.16

Code: Select all

======= Backtrace: =========
/lib/libc.so.6[0x9ab09d]
/lib/libc.so.6(cfree+0x90)[0x9ae6f0]
./eggdrop[0x8079d8e]
/usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x2fb)[0x255f3b]
/usr/lib/libtcl8.4.so(Tcl_EvalEx+0x40f)[0x2564cf]
/usr/lib/libtcl8.4.so(Tcl_Eval+0x3c)[0x2567dc]
/usr/lib/libtcl8.4.so(Tcl_VarEvalVA+0x7c)[0x25690c]
/usr/lib/libtcl8.4.so(Tcl_VarEval+0x27)[0x256967]
./eggdrop[0x807e714]
./eggdrop[0x807e9a0]
/eggdrop.old/modules/server.so[0xcce47c]
./eggdrop[0x807040e]
/lib/libc.so.6(__libc_start_main+0xdc)[0x95af2c]
./eggdrop[0x804a371]
======= Memory map: ========
*** glibc detected *** ./eggdrop: free(): invalid pointer: 0x09a53cf8 ***
======= Backtrace: =========
/lib/libc.so.6[0x9ab09d]
/lib/libc.so.6(cfree+0x90)[0x9ae6f0]
./eggdrop[0x8054cc2]
./eggdrop[0x80656d8]
/eggdrop.old/modules/share.so[0x40641a]
./eggdrop[0x80685a9]
./eggdrop[0x80653c6]
./eggdrop[0x807052b]
/lib/libc.so.6(__libc_start_main+0xdc)[0x95af2c]
./eggdrop[0x804a371]
======= Memory map: ========

StarteR2 · Post by **StarteR2** » Sun Apr 22, 2007 2:37 pm

I think this dude:
http://forum.egghelp.org/viewtopic.php?t=13399

has same problem

Alchera · Post by **Alchera** » Sun Apr 22, 2007 8:52 pm

Code: Select all

wget ftp://ftp.eggheads.org/pub/eggdrop/source/1.6/eggdrop1.6.18.tar.gz

StarteR2 · Post by **StarteR2** » Mon Apr 23, 2007 7:21 am

did you not read what i said? source doesnt work. Anyways i already figuered out the problem.

TCL needs to be compiled/recompiled from source with disabled threads and then eggdrop must be recompilled.

DragnLord · Post by **DragnLord** » Mon Apr 23, 2007 8:07 am

It seems like these problems are happening on Fedora, so far only Fedora has been mentioned as the operating system.
If so, you may want to look at using a different operating system.

Post by **nml375** » Mon Apr 23, 2007 8:44 am

I'm running 1.6.18 without any issues under FC4 (Stentz) using tcl8.4.9-3.
This version (of tcl), however, is not threaded or linked against libpthread.

Code: Select all

$ ldd -v /usr/lib/libtcl8.4.so
        linux-gate.so.1 =>  (0x00457000)
        libdl.so.2 => /lib/libdl.so.2 (0x005bc000)
        libm.so.6 => /lib/libm.so.6 (0x00594000)
        libc.so.6 => /lib/libc.so.6 (0x00475000)
        /lib/ld-linux.so.2 (0x00458000)

        Version information:
        /usr/lib/libtcl8.4.so:
                libdl.so.2 (GLIBC_2.1) => /lib/libdl.so.2
                libdl.so.2 (GLIBC_2.0) => /lib/libdl.so.2
                libm.so.6 (GLIBC_2.0) => /lib/libm.so.6
                libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.2) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.3.4) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
        /lib/libdl.so.2:
                libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
                libc.so.6 (GLIBC_PRIVATE) => /lib/libc.so.6
                ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
        /lib/libm.so.6:
                ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2
                libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
                libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
        /lib/libc.so.6:
                ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2
                ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2
                ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2

Also, downloaded the .srpm's for FC5 and FC6, and it would seem from the changelog that threads was enabled as of 8.4.12-4.

One option on these systems would be to download the source-rpm, modify the .spec-file (look for a line containing --enable-threads), and rebuild the rpm-package.

DragnLord · Post by **DragnLord** » Mon Apr 23, 2007 9:11 am

Threaded TCL works fine on all my FreeBSD machines, so this problem with threaded TCL may just be with Fedora (and derivatives)?
Or is this a problem with most GNU systems?

Post by **nml375** » Mon Apr 23, 2007 9:32 am

After digging through the source abit, it would seem it might be an issue where the configure-scripts fail to properly detect that the tcl-libraries are thread-enabled on these platforms.

DragnLord · Post by **DragnLord** » Mon Apr 23, 2007 10:32 am

If TCL is built from source, instead of RPM, would it install correctly?

Post by **nml375** » Mon Apr 23, 2007 11:22 am

Downloading the source and compiling manually would work just fine, with the only exception/issue that rpm might have some issues solving dependancies (which can be overridden).
There is still the option of building your own rpm's using a custom .spec-file, which allows you to compile it to your likes while preserving rpm-dependancies.

DragnLord · Post by **DragnLord** » Mon Apr 23, 2007 1:41 pm

And this makes a great example of why I love FreeBSD's ports.
"To each their own." as the saying goes. Hopefully the RPM makers will fix it for the GNU communities that use them.