Closed Bug 821640 Opened 12 years ago Closed 12 years ago

cf_status_b2g18 is breaking sending of bugmail when enabled - invalid bug attribute cf_status_b2g18 at Bugzilla/Bug.pm line 4147

Categories

(bugzilla.mozilla.org :: General, defect)

Production
defect
Not set
major

Tracking

()

RESOLVED FIXED

People

(Reporter: emorley, Assigned: glob)

Details

I did not receive the bugmail for bug 821562 comment 1.

cjones also mentioned on #developers that he is missing bugmail too.
Last bug mail I received is exactly 1.5h ago. Since then it seems delivering emails has stopped.
jobqueue was reporting the following error:

invalid bug attribute cf_status_b2g18 at Bugzilla/Bug.pm line 4147 Bugzilla::Bug::AUTOLOAD('Bugzilla::Bug=HASH(0x6df2d40)') called at ./extensions/BMO/Extension.pm line 871 Bugzilla::Extension::BMO::mailer_before_send('Bugzilla::Extension::BMO=HASH(0x44 

But when Sheeri looked at all of the db's, the column did exist in each of the bugs tables. jobqueue supposedly runs against the master as it needs to update the ts_* tables anyway so it doesn't use the slaves. So I obsoleted the column using editfields.cgi and had ashish restart the jobqueue processes which allowed email to flow again. I would like to reenable the field once the queue is down and see if the problem returns. 

Need to get ready for a flight so will check back in later. Glob can you take a look at this when you get on?

Thanks
dkl
My email came through, thank you.
Assignee: nobody → glob
Summary: Missing bugmail from early hours GMT of 2012-12-14 → cf_status_b2g18 is breaking sending of bugmail when enabled - invalid bug attribute cf_status_b2g18 at Bugzilla/Bug.pm line 4147
very weird; the two other fields created at the same time (tracking-b2g18 and blocking-b2g) are not causing this issue.

anyhow, i've re-enabled the field, and got shyam to restart the jobdaemons, and check for stray processes.  it took about five minutes, but all messages that were throwing errors were eventually processed, and the queue is now empty.

this may be caused by the request caching being persistent within the jobqueue daemon .. i'll investigate and file a followup bug if required.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
filed bug 822547 regarding caching and jobqueue.pl.
You need to log in before you can comment on or make changes to this bug.