Hello everyone.
First off, cheers for this community. Eggdrop is truly the mother of all bots.
Ive been using eggdrop succesfuly for a few years now, but lately i have come across a strange annoying issue. Its nothing serious, but just a little bit annoying.
I use '/ctcp <nick> chat' to connect to it. It works fine, the bot asks me for my nick, then for my pass and i am able to logon. However.... the next day in the morning when i try to do so, it will ask me for my nick, but will NOT ask me for my pass in order to proceed. It will just sit there after i entered my nick until the ctcp times out. The bot continues to function normally except this glitch. The only way for me to access it with ctcp is to issue a .restart to it, then after that, i can for this day ctcp normally to it. The next morning.. same issue again.
Am i maybe missing something here?
My host is static, so is my ident when i enter the channel. It still regognizes me as its owner, hence i am able to issue .die or .restart to it. Its just that small issue with the ctcp chat that i am having. Any help would be appreciated.
Cheers everyone.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
Strange ctcp chat problem
Hi, thanks for your reply.
No, after i enter my nickname, i get no reply at all. When i ctcp bot chat, it will pop up a ctcp acknowledge window (x-chat) and i accept it. Then it asks me for my nickname. I enter it, after that.. it will just sit until it timesout. The strange thing though is... if i .restart it, it will work perfectly, until the next morning.
Due to the bot's hosting shell (external), i am not able to telnet, or access the partyline in any other manner (not even with ssh to the host, and telnet locallly), so i cannot really see the problems. I have not yet checked the logs, but will do so now.
//edit:
I logged in with ssh and performed a tail on the logs:
[10:15] 14<chanstats> saving data (14schedule) --> saved (1422), discarded (140)
[10:16] CTCP CHAT: from LoKii (~Tux@L2Reaper.user.gamesurge)
[10:16] Telnet connection: ppp-xxx.xxx.xxx/10660
[10:17] Timeout/EOF ident connection
[10:20] Ident timeout on telnet: telnet@ppp-xxx.xxx.xxx.gr
[10:25] 14<chanstats> saving data (14schedule) --> saved (1422), discarded (140)
No, after i enter my nickname, i get no reply at all. When i ctcp bot chat, it will pop up a ctcp acknowledge window (x-chat) and i accept it. Then it asks me for my nickname. I enter it, after that.. it will just sit until it timesout. The strange thing though is... if i .restart it, it will work perfectly, until the next morning.
Due to the bot's hosting shell (external), i am not able to telnet, or access the partyline in any other manner (not even with ssh to the host, and telnet locallly), so i cannot really see the problems. I have not yet checked the logs, but will do so now.
//edit:
I logged in with ssh and performed a tail on the logs:
[10:15] 14<chanstats> saving data (14schedule) --> saved (1422), discarded (140)
[10:16] CTCP CHAT: from LoKii (~Tux@L2Reaper.user.gamesurge)
[10:16] Telnet connection: ppp-xxx.xxx.xxx/10660
[10:17] Timeout/EOF ident connection
[10:20] Ident timeout on telnet: telnet@ppp-xxx.xxx.xxx.gr
[10:25] 14<chanstats> saving data (14schedule) --> saved (1422), discarded (140)
I'm not at all sure I can offer any help with your problem but something from your logs got my attention. You are using a script I wrote a long time ago 'chanstats' and your logs would indicate that it is saving and discarding events as appropriate. However, I don't believe in coincidences and I don't see how it can save and discard the exact same number of events in two consecutive scans 10 minutes apart. The script is broken and/or the data is not being saved. I will check it out as soon as I get the time.
Certainly it would be one idea to temporarily comment out all the source lines for any addon Tcl's you have and run the bot for a day or two without scripts to see if the issue still exists. Eliminating possible causes one by one is sometimes the only way to eventually resolve problems. The fact that all is well after you restart the bot is a strong clue.
I have not yet experienced an external shell that does not allow telnet access. However, since Eggdrop bots use non-standard telnet ports (set in the .conf file) it is possible that your shell provider blocks the telnet port you are using. I presume you were aware that the Eggdrop telnet port is set in the .conf file and is not port 23 as you would normally expect?
DCC chat is sometimes difficult to set up, particularly if you are behind a router. Generally you would have to create a virtual server on your router with the same port range as those set in your IRC client for DCC chat and directed at the internal PC's IP address that you use for IRC.
Certainly it would be one idea to temporarily comment out all the source lines for any addon Tcl's you have and run the bot for a day or two without scripts to see if the issue still exists. Eliminating possible causes one by one is sometimes the only way to eventually resolve problems. The fact that all is well after you restart the bot is a strong clue.
I have not yet experienced an external shell that does not allow telnet access. However, since Eggdrop bots use non-standard telnet ports (set in the .conf file) it is possible that your shell provider blocks the telnet port you are using. I presume you were aware that the Eggdrop telnet port is set in the .conf file and is not port 23 as you would normally expect?
DCC chat is sometimes difficult to set up, particularly if you are behind a router. Generally you would have to create a virtual server on your router with the same port range as those set in your IRC client for DCC chat and directed at the internal PC's IP address that you use for IRC.
I must have had nothing to do
Yes, it might be a script problem. I will disable the scripts for a day and see the next morning. I dont think its a router/ctcp/firewall problem, otherwise it would not work at all. Its only the first time each new day that it doesnt work. After the first .restart of the bot, it will work fine for the entire day.
Cheers.
Cheers.