Always wrong password.

[thecircuitbox]

I have FreeBSD 6.2 and i installed eggdrop from the ports. I configured everything.

Code: Select all

[02:27:08:05:49:57] >> TCBot: Hi Fubar! I'm TCBot, an eggdrop bot.
[02:27:08:05:49:59] >> TCBot: I'll recognize you by hostmask '*!Laughing@thecircuitbox.com' from now on.
[02:27:08:05:50:01] >> TCBot: YOU ARE THE OWNER ON THIS BOT NOW
[02:27:08:05:50:03] >> TCBot: As master you really need to set a password: with /MSG TCBot pass <your-chosen-password>.
[02:27:08:05:50:05] >> TCBot: All major commands are used from DCC chat. From now on, you don't need to use the -m option when starting the bot. Enjoy !!!
[02:27:08:05:50:11] -> *TCBot* pass password
[02:27:08:05:50:12] >> TCBot: The password you supplies was wrong.

I deleted the user file pid file and chan file over and over and over. Still when I try to set the password it tells me I supplied the wrong one.

When I search for the files to see if there are old ones, I get:

Code: Select all

fubar@thecircuitbox$ locate tcbot
/usr/home/fubar/.eggdrop/.scripts/tcbot
/usr/home/fubar/.eggdrop/tcbot.user
/usr/home/fubar/.eggdrop/tcbot.user~bak

Code: Select all

fubar@thecircuitbox$ cd .eggdrop
fubar@thecircuitbox$ pwd
/usr/home/fubar/.eggdrop
fubar@thecircuitbox$ ls
3478-4-0-0-1.htm        eggdrop.conf            scripts                 thecircuitbox.chan
fubar@thecircuitbox$ ls -al
total 94
drwxr-xr-x  4 fubar  fubar    512 Feb 27 17:49 .
drwxr-xr-x  7 fubar  fubar    512 Feb 27 17:49 ..
drwxr-xr-x  2 fubar  fubar    512 Feb  8 03:15 .scripts
-rw-r--r--  1 fubar  fubar  31709 Feb  8 03:47 3478-4-0-0-1.htm
-rwx--x--x  1 fubar  wheel  51624 Feb 27 17:45 eggdrop.conf
drwxr-xr-x  2 fubar  fubar    512 Feb 14 22:40 scripts
-rw-------  1 fubar  fubar   1473 Feb 27 17:49 thecircuitbox.chan

I really do not see wtf is going on.

[strikelight]

Eggdrop doesn't show the message "The password you supplies was wrong", so that leads me to believe you have a 3rd party script loaded on your eggdrop. Remove all scripts from being loaded in your config, and restart your bot with -m.