Bugzilla Migration to new server issue

Thorsten Schöning tschoening at am-soft.de
Tue Sep 28 14:13:55 UTC 2021

Guten Tag derek.bennett at attaininsight.com,
am Dienstag, 28. September 2021 um 13:07 schrieben Sie:

> [...]I simply cannot access Bugzilla
> from the web browser and get "This site can’t be reached172.17.10.117
> refused to connect."

Check for correct IP, wrong proxy in browser, firewall on
client/server, that the web server runs at all and listens on the
correct IP etc.

> Yes, I can ping the server and was able to browse to it
> before I ran the import and updated the params file.

Depending on your actual setup, a broken Bugzilla might easily make
your web server refuse to start at all or simply kill it on runtime.
Mostly depends on how Perl is executed, if in different processes or
the same, how worker processes vs. threads are handled etc.

> I updated those values directly in the params.json using an editor, but I
> missed the shutdownhtml field. It is however set to "" for some reason, even
> though I had set the field to "migration" using the web client.

So you either didn't save the value for "shutdownhtml" in the web-UI
at all or, more likely in my opinion, mixed up different files. I just
tested to make sure the value is written to that file instead of e.g.
being in the database and for me it was as expected.

> No I did not.

So what exactly does the following from this mail means then?

> [...]and was able to browse to it before I ran the import and
> updated the params file.

You only accessed some test site of your web server and didn't meant
Bugzilla at all? It read to me like the latter, but if it's the
former, than it's somewhat likely like I said before: Your setup of
Bugzilla might simply make your web server start fail at all, in which
case you surely have some error messages somewhere in your logs.

Otherwise I don't see how importing the database und running
checksetup.pl make your web server NOT publish its own test site
anymore. AFAIK checksetup.pl doesn't reconfigure web servers, only
cares about permissions and stuff of its own directory and might break

While I'm at setup problems: Don't use install-module.pl and empty the
Bugzilla private "lib" dir! Especially don't take the one from the old
server, as your Perl are pretty likely not binary compatible, modules
built on one system most liekly don't work on the other and stuff like
that. Those are exactly the things which might make Perl as part of
the web server process simply die in the end. Always prefer your
package manager for dependencies unless absolutely necessary!


Mit freundlichen Grüßen

Thorsten Schöning

AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Fax:   05151-  9468-88
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska

More information about the support-list mailing list