Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Bot won't start on a BOA (barracuda-octopus-aegir) webserver.
The error is:
# drush bot-start
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: require_once(): Failed opening required 'Net/SmartIRC.php'
(include_path='.:/opt/local/lib/php:/usr/lib/php5') in
/data/disk/o1/distro/001/drupal-7.24.1-prod/sites/bot.example.com/modules/bot/bot.smartirc.inc, line 12
Steps:
- I installed a BOA server (on Debian7)
- Created a site name bot.example.com
- Installed PEAR
- Installed NET_SmartIRC
- Got 'bot' with git
- Enabled bot in Drupal
And then tried to start it with drush.
I am not sure, but it seems like it searches for files on a different path than they exist.
Some info from locate:
locate SmartIRC.php
/usr/share/php/Net/SmartIRC.php
Any help is most welcomed,
Bill
Comments
Comment #1
bserem CreditAttribution: bserem commentedComment #2
Morbus IffAt this point, it's not an error with Bot so much as Net_SmartIRC not being in your PHP library path. You'd have to find out where it was installed to, then ensure the library is in your path first, before it becomes a problem truly related to the bot codebase.
Comment #3
Morbus IffComment #4
bserem CreditAttribution: bserem commentedI had to copy the "Net" folder manually under php and I managed to get to the next step:
I can ping irc.freenode.net.
I suppose that the issue here is with SmartIRC? I do not think that BOA would like me to change the php build.
Comment #5
bserem CreditAttribution: bserem commentedComment #6
Morbus IffAccording to that log, your server can't connect to Freenode:
Feb 02 17:53:02 SmartIRC.php(1052) DEBUG_NOTICE: couldn't connect to "irc.freenode.net" reason: "Connection timed out (110)"
You might want to ensure that your server doesn't have a firewall blocking the IRC ports, you might want to ensure that you can even run an IRC bot on your server (most web hosts won't allow it), and alternatively, you could try to toggle the "Use real sockets for IRC server communication" checkbox on admin/config/bot/core.
Comment #7
Dave ReidFreenode has also been under attack today with lots of servers down, so there's a chance it might be that as well.
Comment #8
bserem CreditAttribution: bserem commentedConsidering that I can't connect from my desktop at the moment, I believe it is better to wait a few hours and try again later. Thanks for the heads up, I'll post back when I have more info!
Comment #9
bserem CreditAttribution: bserem commentedI can't manage to make it work. It has probably nothing to do with the module, I'll digg into it later this week.
Thanks for your support :)
Comment #10
bserem CreditAttribution: bserem commentedSteps to make bot connect:
as root in the BOA server:
Add port 6667 on line #54 on /etc/csf/csf.conf and restart csf (csf -r)
Start the bot.
I do not yet know the security implications of this. I'm still digging.
Comment #11
bserem CreditAttribution: bserem commentedInstead of allowing port 6667 on the whole server, I went enabling it for one user only.
This user is the one starts-stops the bot, and has only one drupal-site under his control (the bot site).
To do that, I edited
/etc/csf/csf.allow
and added the following line:tcp|out|d=6667||u=UID
where UID is the user ID on the operating system (linux debian since we talk about BOA).
Hope this info helps :)