Bugzilla Migration to new server issue

[derek.bennett at attaininsight.com]

Morning,

I actually thought my email was pretty clear. I'm not getting any errors
with Apache or when I run the checksetup.pl. I simply cannot access Bugzilla
from the web browser and get "This site can’t be reached172.17.10.117
refused to connect." Yes, I can ping the server and was able to browse to it
before I ran the import and updated the params file.

> How did you update those settings without being able to browse the site?
If you needed to change "data/params.json", that contains a key for
"shutdownhtml" as well:

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.

> Which is exactly the wrong thing I spoke about before: This means you ran
checksetup.pl on an empty database

No I did not. If you re-read my original email I stated that I was able to
recreate and import a new pg_dump which imported without any errors and then
I ran checksetup which gives me the Ok.

There 

-----Original Message-----
From: support-list <support-list-bounces at bugzilla.org> On Behalf Of Thorsten
Schöning
Sent: September 28, 2021 3:54 AM
To: support-list at bugzilla.org
Subject: Re: Bugzilla Migration to new server issue

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

> [...]Checksetup.pl now
> gives me a green complete (see below). However, I can't browse the 
> site to remove the text from the shutdownhtml parameter.

Some details about what that actually means, which errors you get, what
doesn't work etc. would have been helpful.

> I did update the sslbase
> and urlbase entries with the ip of the host as well and also tried 
> rebooting the server.

How did you update those settings without being able to browse the site? If
you needed to change "data/params.json", that contains a key for
"shutdownhtml" as well:

> "shutdownhtml" : "",

> I was able to browse the site before I imported the database though.

Which is exactly the wrong thing I spoke about before: This means you ran
checksetup.pl on an empty database, which resulted in a fresh new Bugzilla
installation. Otherwise Bugzilla wouldn't have been able to work at all.
Importing a backup over that fresh new installation is wrong and can lead to
all kinds of errors. The import needs to be done with an empty database and
checksetup.pl needs to be run afterwards.

Being able to access the site properly afterwards should then only depend on
the web server config and the files "localconfig" and "data/params.json" of
Bugzilla itself. Both need to be the ones from the old Bugzilla, possibly
adjusted to the new host using some text editor.

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




_______________________________________________
support-list mailing list
support-list at bugzilla.org
https://lists.bugzilla.org/listinfo/support-list


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus