A forum for technical support discussion related to Fogbugz.
For some reason email notifications are no longer being sent by FogBugz. It was working after our upgrade to 4.0.9 but recenlty it stopped.
I know its probably something on our end but I'm at a loss on how to debug this. Does FogBugz keep a log of errors when connecting/sending mails?
I've tried telnetting to the mail server from the FogBugz machine and that works fine so I know the server name is OK (and other internal applications are sending SMTP mail without problems).
Did you go through this knowledge base article?
If you have gone through that and found nothing, could you try running "SELECT * FROM MailQueue" against your fogbugz database and see if that turns anything up?
I checked and the maintenance service was installed but not running. I started it but still no mails.
There are 184 rows in the MailQueue table.
I tried to open the heartbeat.asp page and I got a FogBugz exception, which I just submitted to you guys as a bug.
I looked at the error you submitted and it is complaining that a column that should be there is not 'ixMailbox' which exists both in the Bug table and in the Mailbox table. Have you modified your database at all? Can you check those tables and columns?
They are there. But I should note that we have a case-sensitive database and had a previous problem with your install script (that was using 'Drop' in the full-text setup rather than 'drop'). Could that be it?
select * from Bug where 1 = 0
(0 row(s) affected)
select * from Mailbox where 1 = 0
(0 row(s) affected)
I made the change to CDailyTask.asp and heartbeat.asp now returns '+' as expected. The maintenance service is running, too.
But MailQueue still shows 184 rows and no mail is going out. Do I need to run something to actually force it to catch up on the queued notifications? Or do I just need to wait a while?
OK, I understand it now. Each get of heartbeat.asp sends one queued mail message. After hitting the F5 key 184 times, I think we are back in business.
Just a suggestion: this is the second bug I've run into due to case-sensitivity. It would be nice if you guys would build a case-sensitive database and test FogBugz on your end to flush out any more that may be there.
The above action corrected my database case sensitivity issue. But I now have an another issue with the same SELECT statement which states that 'The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.' Is this due to a US-UK date formatting comflict?
Tuesday, March 22, 2005
This topic is archived. No further replies will be accepted.Other recent topics