Bugzilla

[vphmubkc]

Has anyone had any success installing Bugzilla? I know that a perl script, checksetup.pl, has to be run in order to verify all perl modules are installed, and to generate the localconfig file. If TCH does not offer shell access, how is this accomplished?

 

I'd appreciate any tips on how to get Bugzilla installed and running.

 

Thanks!

Jonathan

[vphmubkc]

Has anyone had any success installing Bugzilla on a TCH hosted account? I know a perl script, checksetup.pl, has to be run to verify all perl modules are installed and to create the localconfig file. How is this accomplished if TCH does not offer shell access?

 

I'd appreciate any tips on how to get Bugzilla installed and running.

 

Thanks!

Jonathan

[TweezerMan]

Duplicate topics merged and moved to appropriate forum.

 

Please do not post topics in multiple forums (cross-posting) - it is against the Forum Guidelines.

[TweezerMan]

I am not aware of anyone who has successfully installed and used Bugzilla on a shared hosting account.

 

You should be able to run the checksetup.pl script from a cron job, which you can set up in CPanel -> Cron Jobs. Be sure to configure a valid e-mail address in cron, as cron will e-mail the output from the script to you. Once cron has run the script, delete the cron job so the script won't be run again.

 

I don't see anything in the Bugzilla documentation to indicate whether there would be any problems running Bugzilla on a TCH virtual hosting (shared) account. I will note though, that if Bugzilla consumes excessive server resources, or if Bugzilla is not properly secured and is subsequently compromised (hacked), your account could be suspended.

[TCH-Dick]

I was only testing it and never put it into use so I don't know how it will affect the server. However you do not need shell access or a cron job. checksetup.pl can be run directly from your browser. The only problem I ran into was I had to have a few modules installed to get it to work (just put in a ticket to the help desk).

 

Find the following in your installation: /docs/txt/Bugzilla-Guide.txt

 

Just follow these directions and you should have no problem.

[vphmubkc]

I was only testing it and never put it into use so I don't know how it will affect the server. However you do not need shell access or a cron job. checksetup.pl can be run directly from your browser. The only problem I ran into was I had to have a few modules installed to get it to work (just put in a ticket to the help desk).

 

Find the following in your installation: /docs/txt/Bugzilla-Guide.txt

 

Just follow these directions and you should have no problem.

<{POST_SNAPBACK}>

 

Dick,

 

Thanks for your comments. I'm not sure how to run the checksetup.pl script from a web browser. Does this have to be done using the cpanel? Perhaps the best way is to use cron...

 

Thanks again.

[TCH-Dick]

Assuming you have your files in a directory named bugzilla just go to

 

http://your-TCH-site.com/bugzilla/checksetup.pl

[vphmubkc]

Assuming you have your files in a directory named bugzilla just go to

 

http://your-TCH-site.com/bugzilla/checksetup.pl

<{POST_SNAPBACK}>

I was able to run the checksetup.pl script, and there are some perl modules missing. I'll send a help desk request to install these.

[vphmubkc]

Got most of the Perl modules installed. There is one remaining called "Template". We seem to have trouble with this one. There are a large number of modules with the name "Template". Any clue as to which one we need to install?

 

Thanks.

[vphmubkc]

Assuming you have your files in a directory named bugzilla just go to

 

http://your-TCH-site.com/bugzilla/checksetup.pl

<{POST_SNAPBACK}>

 

Good news. All of the Perl modules are installed. Next problem: the checksetup.pl script asks for an administrator's e-mail address and password. Obviously, I can't enter it via a WebBrowser. Any ideas on how to do it?

 

Thanks.

[TweezerMan]

The instructions for how to run checksetup.pl non-interactively are contained within the checksetup.pl script (beginning at line 94):

# To operate checksetup non-interactively, run it with a single argument

# specifying a filename with the information usually obtained by

# prompting the user or by editing localconfig. Only information

# superceding defaults from LocalVar() function calls needs to be

# specified.

#

# The format of that file is....

#

# $answer{'db_host'} = '$db_host = "localhost";

# $db_port = 3306;

# $db_name = "mydbname";

# $db_user = "mydbuser";';

#

# $answer{'db_pass'} = q[$db_pass = 'mydbpass';];

#

# $answer{'ADMIN_OK'} = 'Y';

# $answer{'ADMIN_EMAIL'} = 'myadmin@mydomain.net';

# $answer{'ADMIN_PASSWORD'} = 'fooey';

# $answer{'ADMIN_REALNAME'} = 'Joel Peshkin';

#

#

After creating the file with the above information in it, you could call it in your browser like this (assuming the above file is created as 'answers.pl' in the bugzilla directory):

>http://www.my-TCH-domain.com/bugzilla/checksetup.pl
?/home/cpanelName/public_html/bugzilla/answers.pl

(Line break added for readability only.)

[vphmubkc]

The instructions for how to run checksetup.pl non-interactively are contained within the checksetup.pl script (beginning at line 94):

 

After creating the file with the above information in it, you could call it in your browser like this (assuming the above file is created as 'answers.pl' in the bugzilla directory):

>http://www.my-TCH-domain.com/bugzilla/checksetup.pl
?/home/cpanelName/public_html/bugzilla/answers.pl

(Line break added for readability only.)

<{POST_SNAPBACK}>

David,

 

Thanks for taking a look and finding the way to run checksetup.pl non-interactively. I can run checksetup.pl one time, which generates the localconfig file. But when I try to run checksetup.pl a second time, I get a 403 Forbidden error. I checked the file permissions and they are correct. Why else would I get this error?

 

Thanks again.

[TweezerMan]

The checksetup.pl script writes an .htaccess file in the main Bugzilla directory to prevent others from doing what you're trying to do - run the script in a browser. From what I can tell, this is what would prevent you from running the script a second time in your browser:

><FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$>
 deny from all
</FilesMatch>

Among other things, it prevents any file ending in .pl from being called in a browser (including checksetup.pl).

[vphmubkc]

The checksetup.pl script writes an .htaccess file in the main Bugzilla directory to prevent others from doing what you're trying to do - run the script in a browser.  From what I can tell, this is what would prevent you from running the script a second time in your browser:

><FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$>
 deny from all
</FilesMatch>

Among other things, it prevents any file ending in .pl from being called in a browser (including checksetup.pl).

<{POST_SNAPBACK}>

So, is the answer to delete the .htaccess file?

[vphmubkc]

The checksetup.pl script writes an .htaccess file in the main Bugzilla directory to prevent others from doing what you're trying to do - run the script in a browser.  From what I can tell, this is what would prevent you from running the script a second time in your browser:

><FilesMatch ^(.*\.pl|.*localconfig.*|runtests.sh)$>
 deny from all
</FilesMatch>

Among other things, it prevents any file ending in .pl from being called in a browser (including checksetup.pl).

<{POST_SNAPBACK}>

 

David,

 

Is it possible for a TCH administrator to execute the checksetup.pl script and setup the bugzilla admin user account using my e-mail address and a default password? This seems like the easiest solution, and it would probably take a whole 30 seconds to perform.

 

Should I submit a help desk ticket?

 

Thanks...

[TweezerMan]

So, is the answer to delete the .htaccess file?

<{POST_SNAPBACK}>

I would suggest examining the .htaccess file and see if the code I posted above is in the file, and if it is, the easiest solution would be to delete the .htaccess file. It should be recreated when you run checksetup.pl again.

 

Is it possible for a TCH administrator to execute the checksetup.pl script and setup the bugzilla admin user account using my e-mail address and a default password?  This seems like the easiest solution, and it would probably take a whole 30 seconds to perform.

<{POST_SNAPBACK}>

Is it possible? Yes. Would I recommend it? Probably not.

 

Anyone from the Help Desk who runs the checksetup.pl script for you will be running it as 'root'. Running as 'root', the script can set things that you may be prevented from changing or even accessing. One example is the .htaccess file discussed above. When you run checksetup.pl, the .htaccess file created will be owned by you, and you will have permission to edit it. Running as 'root', the .htaccess file will be owned by 'root' and you will not be able to modify it at all.

 

I don't know what all the script does, but I would not be comfortable executing that script as 'root', knowing that I'm supposed to subsequently run Bugzilla without root privileges at all.

[vphmubkc]

I would suggest examining the .htaccess file and see if the code I posted above is in the file, and if it is, the easiest solution would be to delete the .htaccess file.  It should be recreated when you run checksetup.pl again.

Is it possible? Yes.  Would I recommend it? Probably not.

 

Anyone from the Help Desk who runs the checksetup.pl script for you will be running it as 'root'.  Running as 'root', the script can set things that you may be prevented from changing or even accessing.  One example is the .htaccess file discussed above.  When you run checksetup.pl, the .htaccess file created will be owned by you, and you will have permission to edit it.  Running as 'root', the .htaccess file will be owned by 'root' and you will not be able to modify it at all.

 

I don't know what all the script does, but I would not be comfortable executing that script as 'root', knowing that I'm supposed to subsequently run Bugzilla without root privileges at all. 

<{POST_SNAPBACK}>

 

I submitted the help desk ticket. They will not run the script for good reasons. Guess it's back to the drawing board.

[vphmubkc]

After much pain and suffering, I'm pleased to say I have Bugzilla installed and running. I had to hack at the checksetup.pl script to include the "answer" variable assignments instead of passing the answers.pl as an argument. I'm not at all familiar with Perl, so this proved to be a challenge (personally, I prefer Python and PHP).

 

I also had to change all of the file permissions for all files to allow others read access. I probably had some "group" variable not defined correctly in "localconfig".

 

This includes the .htaccess file. I was only able to discover this by reading the server error logs, which indicated the .htaccess file could not be read. Not at all obvious.

 

And, for some reason, the executable flag was not set for the css/ directory, the web pages looked really bad without the styling. Another chmod, and everything is functional and looks great.

 

Thanks for all the help.

[TCH-Bruce]

Glad you have it working