Description of problem: prompt proper message when start bugzilla service with html disabled text set Version-Release number of selected component (if applicable): 4.4.9037-5 How reproducible: Always Steps to Reproduce: 1.Set data into 'shutdownhtml' in data/params 2.Then try to start up bugzilla service like: service bugzilla-queue-1 start 3. Actual results: [root@bzweb01-qe redhat]# service bugzilla-queue-1 start Starting bugzilla-queue-1: Use of uninitialized value in subtraction (-) at /usr/lib64/perl5/Time/HiRes.pm line 73. Use of uninitialized value in subtraction (-) at /usr/lib64/perl5/Time/HiRes.pm line 73. Log4perl: Seems like no initialization happened. Forgot to call init()? bash: line 1: 18529 Segmentation fault /var/www/html/bugzilla/jobqueue.pl -p '/var/run/bugzilla-queue-1.pid' -n bugzilla-queue-1 start > /dev/null [FAILED] Expected results: it should exit with polite message not seg fault Additional info:
This is triggered by loading the user in init_page, there needs to be a new class of script that exits(1) or dies with the appropriate message before that code.
> Steps to Reproduce: > 1.Set data into 'shutdownhtml' in data/params > 2.Then try to start up bugzilla service like: This doesn't make sense really. The job queue should not be running when the site is in shutdown mode.
After retest in build 4.4.9039-2, QE think it is better that it could print out the shutdown content when start bugzill-queue failed in the case set some string into shutdown param Actual Results: [root@bzperfweb01 redhat]# service bugzilla-queue-1 status This Web Server Shutdown temporal [root@bzperfweb01 redhat]# service bugzilla-queue-1 start Starting bugzilla-queue-1: [FAILED] Expected results: [root@bzperfweb01 redhat]# service bugzilla-queue-1 status This Web Server Shutdown temporal [root@bzperfweb01 redhat]# service bugzilla-queue-1 start Starting bugzilla-queue-1: [FAILED] This Web Server Shutdown temporal
Tested on QA environment(bzweb01-qe) with version(4.4.9039-3, DB: mysql) QA environment(bzperfweb01.app.qa) with version(4.4.9039-3, DB: psql ) Result: Pass
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.