Hi Mich,
I must admit I don't understand your problem at all. There are probably some cases not covered in the documentation. Since you're in the community and don't have support, you can contribute by researching what's wrong in your case and submitting a pull request to the online documentation on GitHub. This could help others. Basically, the pg_upgrade script is supposed to transfer the database from version 9.6 to version 11, shut down version 9.6, and move the listening port for version 11 to 5432.
Regards,
Denis
Bad gateway suite Debian update
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello, I also tried updating Debian 9 to 10, then wapt server from 1.7.4 to 1.8.1 (Community), but I'm still getting the "502 Bad Gateway" error on the wapt interface. The only issue I noticed during the updates is the message:
"Error: target cluster 11/main already exists" after running the command: pg_upgradecluster -v 11 9.6 main
"Error: target cluster 11/main already exists" after running the command: pg_upgradecluster -v 11 9.6 main
Starting from scratch, I read that the solution appears during the update installation:
You just need to run the command "pg_dropcluster --stop 11 main" before "pg_upgradecluster -v 11 9.6 main".
Could you add this to your update procedure if you'd like?
You just need to run the command "pg_dropcluster --stop 11 main" before "pg_upgradecluster -v 11 9.6 main".
Could you add this to your update procedure if you'd like?
Done, to be published in a new version of the documentation coming very soon.
By default the PostgreSQL is not upgraded to PostgreSQL 11.
One needs to manually request the upgrade.
After upgrading, it is possible to remove the old PostgreSQL 9.6 database.
.. code-block:: bash
sed -i 's/stretch/buster/g' /etc/apt/sources.list
sed -i 's/stretch/buster/g' /etc/apt/sources.list.d/wapt.list
apt-get update
apt-get update && apt-get dist-upgrade
pg_dropcluster --stop 11 main
pg_upgradecluster -v 11 9.6 main
apt-get remove postgresql*-9.6
apt-get autoremove
/opt/wapt/waptserver/scripts/postconf.sh
Vincent CARDON
Tranquil IT
Tranquil IT
