----- Original Message ----- > From: "Andrew Colin Kissa" <[email protected]> > To: "Baruwa users list" <[email protected]> > Sent: Friday, June 21, 2013 2:17:20 PM > Subject: Re: [Baruwa] Message preview error > > You should usually pickup something in the celeryd log in /var/log/baruwa > > > I suspect the issue is hostname related. You need to have a celery process > listening to > a queue for the hostname that is logged to the database. > > When you preview a message the request gets sent to that queue and the > workers listening > to the queue do the actual processing of the message and return that back to > you. > > So check what is being logged into the db as the hostname and what is > configured in your > production.ini file under celery.queues >
Looks like celery actually wasn't running at all. Its running now and get the following output on its startup: http://pastebin.com/rqNjjvTt I've verified that what I have in the db under 'hostname' under 'messages' is what is stated in production.ini under celery.queues. The error is now different on the frontend. I instantly get (since celery is now started): "Message: 560AB97B3ED.A3776 could not be previewed" I'm not seeing any info in the celeryd.log though. Any other ideas? ps. Good to hear from you - I thought I recognized that name :D -- Garith Dugmore Senior System Administrator South African Astronomical Observatory and Southern African Large Telescope _______________________________________________ http://pledgie.com/campaigns/12056
