I just upgraded to 2.5.0.beta6. After the successful upgrade completed, all searches fail resulting in the following message after an extended period of think time (animating circle): [Screen Shot 2020-06-06 at 15.51.08] [Screen Shot 2020-06-06 at 15.43.32] I have tried rebooting the server, an…

If the database was upgraded to Postgres 12 it might take time for things to stabilize?

Does the latest docker image use PostgreSQL 12 and @codinghorror how do you define “take time”? Should I let it be to resolve itself or do I need to fix something? UPDATE: Yes, PostgeSQL 12.

Ok, I went and read this: [imagen] PostgreSQL 12 update announcements warning WARNING! If your database is very large, you will need a lot of extra disk space (2x database size) and should be very careful with this upgrade! We just landed the long waited PostgreSQL maj…

Ok, search is working again on 2.5.0b6, but it’s really slow compared to 2.5.0b3. Any advice?

Hello @ravenzachary You might consider checking the integrity of your PostgreSQL indexes and making sure they are working properly and not corrupted.

Thank you. What commands would I use for that?

Here ya go @ravenzachary [imagen] Use amcheck to Check PostgreSQL Index Integrity (Corruption) Self-Hosting Lately, I have read a number of Discourse topics on meta about “index corruption” in both PostgreSQL 10 and 12. One of the take-a-ways from these discussions is th…

Buscar errores 502 en 2.5.0.beta6

Soporte Instalación

neounix (Dark Matter) 11 Junio, 2020 06:22 9

Aquí lo tienes, @ravenzachary

Tema		Respuestas	Vistas
502 bad gateway on specific searches Self-hosting	4	847	18 Enero 2019
Trouble with latest update Self-hosting	3	874	19 Junio 2020
Discourse on postgres 12 breaks upgrades Self-hosting	17	1062	27 Agosto 2021
Rebuild fails on db:migrate w/PG12 Self-hosting	18	2044	31 Diciembre 2022
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2014	15 Febrero 2021

Buscar errores 502 en 2.5.0.beta6

Temas relacionados