Bug #849

email is not being generated by the scheduler

Added by Mark Donohoe over 1 year ago. Updated about 1 year ago.

Status:Closed Start date:02/07/2012
Priority:High Due date:
Assignee:Alex Norton % Done:

0%
Category:Scheduler
Target version:2.0.0
Rank: Tester:

Description

On snape.ostt using svn rev 5473, a user was created with email notification enabled. The email will be delivered to the local system. Trying various scenarios, I could not get email generated.

Using the command line and mailx I could send mail to markd, markd@snape and . Watching the mail.log I could see email being sent and delivered on the local system and could read it with mutt.

I tried all of the above addresses in the user account, no email was sent nor did the log show any being sent/delivered. I also tried fossy, and used the above address for fossy as well. Fossy never got any email and the mail.log did not show any activity.

History

#1
Updated by Alex Norton over 1 year ago

  • Status changed from New to Resolved

There was a check in the email_notification function of database.c that was checking to make sure the jobs status was correct for sending an email notfication. This check was already being done elsewhere, so the offending code was removed and the scheduler should now be correctly sending emails.

This should be fixed with svn 5530

#2
Updated by Mark Donohoe over 1 year ago

  • Status changed from Resolved to In Progress

Alex, using svn 5531 on snape.ostt I can't get email notification working. Mary could also not get it working on fluffy as well. On both snape and fluffy, one can send mail to markd or markd@snape or fossy via mailx and it works.I tried 4 different uploads as fossy with email notification checked. I tried these for the email:
fossy, markd, markd@snape, , nothing worked. Since neither Mary nor I can get this to work can you please take another look? Feel free to use snape or fluffy if you need to. Thanks.

#3
Updated by Bob Gobeille about 1 year ago

  • Priority changed from Normal to High

#4
Updated by Alex Norton about 1 year ago

  • Status changed from In Progress to Resolved

Hopefully this has been fixed with svn 5596

#5
Updated by larry shi about 1 year ago

#1551 is related with this issue. I am not sure if we can say this defect has been fixed.

#6
Updated by Mary Laser about 1 year ago

  • Status changed from Resolved to Closed

closing this issue as email is now being generated. Another issue #1551 will address email content.

Also available in: Atom PDF