Bugzilla Installation

[james....@gmail.com]

I have followed all the instructions within the documentation to get bugzilla set up. Every module is installed and all files are configured properly. However, I keep getting this error. I used the most up to date package.

DBD::mysql::st execute failed: Table 'bugs.flags' doesn't exist [for Statement "SHOW INDEX FROM flags"] at Bugzilla/DB/Mysql.pm line 984, <DATA> line 755.
Bugzilla::DB::Mysql::bz_index_info_real(Bugzilla::DB::Mysql=HASH(0x669aea0), "flags", "flags_bidattid_idx") called at Bugzilla/DB/Mysql.pm line 411
Bugzilla::DB::Mysql::bz_setup_database(Bugzilla::DB::Mysql=HASH(0x669aea0)) called at checksetup.pl line 123

[Emmanuel Seyman]

* james....@gmail.com [28/10/2020 07:19] :

>
> I have followed all the instructions within the documentation to get bugzilla
> set up. Every module is installed and all files are configured properly.
> However, I keep getting this error. I used the most up to date package.

Could you tell us:

* what version of Bugzilla you're using
* what version of MySQL you're using
* what tables your bugs database contains

Emmanuel

[Thorsten Schöning]

Guten Tag james....@gmail.com,
am Mittwoch, 28. Oktober 2020 um 15:19 schrieben Sie:

> DBD::mysql::st execute failed: Table 'bugs.flags' doesn't exist
> [for Statement "SHOW INDEX FROM flags"] at Bugzilla/DB/Mysql.pm line 984, <DATA> line 755.

Your version of MySQL/MariaDB is too old most likely. You need at
least 5.6, which supports FULLTEXT INDEX for tables using InnoDB,
which is the default these days by Bugzilla.

https://dev.mysql.com/doc/refman/5.6/en/innodb-fulltext-index.html

If you search the list for the following error, you will find a lot of
hints to too old or too new versions of MySQL or MariaDB.

> DBD::mysql::st execute failed: Table 'bugs.flags' doesn't exist

> https://www.google.de/search?client=opera&q=bugzilla+"DBD%3A%3Amysql%3A%3Ast+execute+failed%3A+Table+%27bugs.flags%27+doesn%27t+exist"&sourceid=opera&ie=UTF-8&oe=UTF-8

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[Leo James]

Thanks all. I have listed the mysql and bugzilla versions below. I see now that I have to update mysql to 5.6. I will do that and update this if anything else pops up.

bugzilla: 5.0.6
mysql: Ver 14.14 Distrib 5.1.73

[Leo James]

So I have updated MySQL to 5.6.5 and the Bugzilla version has remained the same. I am still getting that same error as before when running the checksetup.pl script.

[Leo James]

attach_data |
| attachments |
| audit_log |
| bug_group_map |
| bug_see_also |
| bug_severity |
| bug_status |
| bug_tag |
| bug_user_last_visit |
| bugs |
| bugs_activity |
| bugs_aliases |
| bugs_fulltext |
| bz_schema

Those are the tables that are in the database currently.

[Thorsten Schöning]

Guten Tag Leo James,
am Mittwoch, 28. Oktober 2020 um 21:42 schrieben Sie:

> So I have updated MySQL to 5.6.5 and the Bugzilla version has
> remained the same. I am still getting that same error as before when
> running the checksetup.pl script.

Either Bugzilla is still talking to the older MySQL or 5.6.5 is still
too old. Others reported 5.7.8 to be successfull.

https://groups.google.com/g/mozilla.support.bugzilla/c/s0589wtC9Vw/m/pfXIZ72xBwAJ

[Leo James]

> Either Bugzilla is still talking to the older MySQL or 5.6.5 is still
> too old. Others reported 5.7.8 to be successfull.

Yes, I completely missed the step of removing the original database and letting a new one be built. I was wondering if you'd be able to help with another issue. I have been searching for this for the past few hours and can't seem to find anything that has worked. I can run: testserver.pl http://localhost/bugzilla and will get this:

testserver.pl http://localhost/bugzillaTEST-OK Webserver is running under group id in $webservergroup.
TEST-OK Got padlock picture.
TEST-OK Webserver is executing CGIs via mod_cgi.
TEST-OK Webserver is preventing fetch of http://localhost/bugzilla/localconfig.

All seems fine there, though I thought there were more tests that would be run. When I go to the web browser (firefox) and type in that link, I get a message saying "unable to connect". If I try entering in the server IP as the address, I get a permission denied message. I have an alias set in the httpd file as well as the directory pointed in the right spot as well as FollowSymLinks for both the root directory and the bugzilla directory. Not sure what else to check.

[Thorsten Schöning]

Guten Tag Leo James,
am Donnerstag, 29. Oktober 2020 um 20:43 schrieben Sie:

> [...]When I go to the web browser (firefox) and type in

> that link, I get a message saying "unable to connect".

The important thing is to know on which host you installed Bugzilla,
from which host you tried to access it using Firefox etc. One needs to
decide what "localhost" actually is when.

Additionally keep in mind that "localhost" might be resolved
differently depending on who is trying to resolve it. Some
apps/environments might resolve it to some IPv4 address like
127.0.0.1, some might resolve it to IPv6 like ::1. Depending on the
config of your web server, requests to ::1 might simply not work when
your web server is loisteing on 127.0.0.1 only and the other way
around.

So you need to provide all those detaisl along with the web server
config you are using. And not only those parts you added specifically
for Bugzilla, but where the web server listen on etc. as well.

In general, problems like you have most likely occur when people are
NOT following the docs, but instead do what they are thinking should
work. So if you didn't use the suggested config from the docs, I
strongly suggest doing so first and customize things only afterwards.

https://bugzilla.readthedocs.io/en/5.0/installing/apache.html#apache-with-mod-cgi

> If I try
> entering in the server IP as the address, I get a permission denied
> message.

If that is correct or not heavily depends on your actual web server
config. Many of those support a concept of virtual server, so it might
easily be that Bugzilla is properly set up for a VHOST listening on
"localhost" which might be 127.0.0.1, while for your server IP some
completely different VHOST is responsible NOT properly set up for
Bugzilla. One needs to look at the config.

> I have an alias set in the httpd file as well as the
> directory pointed in the right spot as well as FollowSymLinks for
> both the root directory and the bugzilla directory. Not sure what
> else to check.

All those settings are per VHOST and therefore might easily work for
localhost, but nothing else. It heavily depends on your config.