508491 - Set up QMO Bugzilla cron for QMO stage

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Paul Craciunoiu [:paulc]]

As per bug 499361, the QMO Bugzilla module is now enabled and working on QMO stage. Next step is setting up its cron to run.
The file should be in the website root, named cron-qmo_bugzilla.php

Comment 1

[Paul Craciunoiu [:paulc]]

A great frequency would be 10 minutes. Is that too often?

Comment 2

[Shyam Mani [:fox2mike]]

No really major is it? :p

10 is cool, I'll set it up.

Comment 3

[Shyam Mani [:fox2mike]]

Done and running.

Comment 4

[Paul Craciunoiu [:paulc]]

Just to check, the output is something like "QMO Bugzilla ran successfully"?
The chart doesn't seem to be getting updated...

Comment 5

[Shyam Mani [:fox2mike]]

No output.

[root@mrapp-stage02 quality.mozilla.org]# php -f cron-qmo_bugzilla.php 
[root@mrapp-stage02 quality.mozilla.org]#

Maybe something wrong with the php script?

Comment 6

[Shyam Mani [:fox2mike]]

Okay, so here's your issue :

On Khan, where things work - 

[root@khan qmo]# php -a
Interactive shell

php > include_once './includes/bootstrap.inc';
php > drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
php >

On mrapp-stage02 where things don't work - 

[root@mrapp-stage02 quality.mozilla.org]# php -a
Interactive shell

php > include_once './includes/bootstrap.inc';
php > drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
[root@mrapp-stage02 quality.mozilla.org]#

So basically, drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL); bails out on stage02, without any error whatsoever. 

Hence your cron never gets to run...on stage02. Any thoughts on what's causing this?

Comment 7

[Paul Craciunoiu [:paulc]]

Haven't found much. I'm thinking you should go into drupal_bootstrap() to figure out where it dies.

Comment 8

[Shyam Mani [:fox2mike]]

Hahaha. This is where I'm starting to not like Drupal ;)

I'll see if I can find more info.

Comment 9

[Paul Craciunoiu [:paulc]]

Sorry man :( I'm willing to do the work but I'd need access :P

Comment 10

[Shyam Mani [:fox2mike]]

Okay, poked around a bit more and got nowhere.

mrz, I'm wondering if we can give paul access to staging to debug this issue further? Don't know our policies on that.

Comment 12

[Paul Craciunoiu [:paulc]]

Another good way to try and debug this is by disabling all modules on stage except for the core modules and running cron again. If it runs, trace back to see which module makes it die out.

Comment 13

[Shyam Mani [:fox2mike]]

How would I go about disabling modules? Comment out stuff in the drupal_bootstrap function?

Comment 14

[Paul Craciunoiu [:paulc]]

1. Make sure the email fields of users are "cleared up" (shoulda mentioned this for staging), i.e. in users table, clear up the emails column for non-admin users. This is so we don't spam people if emails get sent out... And i'm not sure that stage is cleaned up.

2. You need an admin user which I think I created for you. The best way to disable modules is through the UI at https://quality.authstage.mozilla.com/admin/build/modules
However, you can also do this from the db by going to the system table and setting status = 0 to various modules (careful not to disable core modules!)

Let me know if you need any help.

Comment 15

[Paul Craciunoiu [:paulc]]

So, after a bunch of investigation from buchanae, kourge and fox2mike, we learned that Drupal is special and requires cron.php to be run through http://

Hence, the actual set up requires using ./scripts/drupal.sh (which probably uses wget).

This worked for me on khan:
/home/pcraciunoiu/public_html/qmo/scripts/drupal.sh --root /home/pcraciunoiu/public_html/qmo/ http://default/cron.php
Generic:
/full/path/to/site/scripts/drupal.sh --root /full/path/to/site/ http://default/cron.php

Comment 16

[Shyam Mani [:fox2mike]]

[root@mrapp-stage02 ~]# /data/www/quality.mozilla.org/scripts/drupal.sh --root /data/www/quality.mozilla.org/ http://default/cron.php
[root@mrapp-stage02 ~]# /data/www/quality.mozilla.org/scripts/drupal.sh --root /data/www/quality.mozilla.org/ http://default/cron-qmo_bugzilla.php

Didn't really do much. the Admin page showed cron wasn't run and when I clicked on run cron manually seemed to work fine.

Bah. Replacing default with quality.mozilla.org doesn't help either.

Comment 17

[Shyam Mani [:fox2mike]]

oooh, but replacing default with quality.authstage.mozilla.com seems to work, I'm shoving this into cron, let's watch it.

Comment 18

[Shyam Mani [:fox2mike]]

w00t! Works. 

Re-open if you see any issues. Boy am I glad we got this one closed down :)

Comment 19

[Paul Craciunoiu [:paulc]]

Woot! Amazing!!
Aakash, Tomcat: please QA stage for various things, including the QMO Bugzilla stuff (although you can leave that for later).

There are two cron jobs set up (as you can see in comment 16): general cron + QMO Bugzilla cron, hence we can enable cron on prod first (helps with spam control, commentcloser, etc), and once QMO Bugzilla is tested better, we can do that one too.