In trying to find out why notices aren't going out to Twitter or Facebook (or XMPP for that matter) I've come across a number of notices in my statusnet.log file:
2010-08-29 20:24:32 LOG_DEBUG: [status.smscotten.com:queuedaemon.php:16889] Waiting up to 0 seconds for socket data...
2010-08-29 20:24:32 LOG_DEBUG: [status.smscotten.com:queuedaemon.php:16889] DBQueueManager (main): Checking for notices...
2010-08-29 20:24:33 LOG_DEBUG: [status.smscotten.com:queuedaemon.php:16928] DBQueueManager (main): Checking for notices...
2010-08-29 20:24:33 LOG_INFO: [status.smscotten.com:queuedaemon.php:16889] claiming queue item id = 32282 for transport distrib
2010-08-29 20:24:33 LOG_INFO: [status.smscotten.com:queuedaemon.php:16942] claiming queue item id = 32282 for transport distrib
2010-08-29 20:24:33 LOG_INFO: [status.smscotten.com:queuedaemon.php:16942] claim failed.
2010-08-29 20:24:33 LOG_DEBUG: [status.smscotten.com:queuedaemon.php:16942] DBQueueManager (main): No notices waiting; idling.
in my queue_item table I have a number (hundreds, possibly over 1000) of rows with "pushin" as the transport and NULL for claimed
Might this indicate a problem? More specifically is it the sort of problem that might indicate why I can't get notices out to Twitter, Facebook, or XMPP?
I am actually running 0.9.4, though the created dates on many of these rows makes it clear that this was going on in 0.9.3 as well.
Comments
Thanks,