mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #1355] OperationalError : could not connect to server #1079
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1079
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CooperBarrett on GitHub (Jan 13, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1355
Sorry, I'm French I'm using Deepl. com for translation...
Impacted versions
Modoboa: I don't have access to modoboa and I don't know where to find the information in the terminal. But I installed it two weeks ago.
installer used: Yes/
Webserver: Nginx
Installed on a dedicated Debian 9.3 server
Steps to reproduce
After reboot
Current behavior
"Error with : Error as occured" when I visit https://mail.mondomaine.fr
Hello,
I installed modoboa 2 weeks ago, everything worked perfectly but after a reboot, I no longer have access to webmail and I can no longer send or receive emails...
I have activated debug mode, here's what it returns to me:
I add the trace back :
Do you need the other logs displayed?
Thank you in advance for your help, I'm really annoyed...
@tonioo commented on GitHub (Jan 13, 2018):
As the log says, you're postgresql server is unreachable. Make sure it is running on the same machine than your modoboa instance.
@CooperBarrett commented on GitHub (Jan 13, 2018):
Thank you for your answer,
then postgresql and well on the same machine (installed with the script), and if I do
service postgresql status, all is ok and it's running well.Maybe a problem with the port?
This command
netstat -laputen | grep 5432doesn't return anything to me... I really don't understand !info :
log posgresql :
My server is configured with "fr_FR.UTF-8" is it related ?
@tonioo commented on GitHub (Jan 13, 2018):
Maybe you could try to run the following command:
and select fr_FR.UTF-8 and en_US.UTF-8 locales.
@CooperBarrett commented on GitHub (Jan 15, 2018):
Here's what I have now...
I finally think that the locals are not involved...
@tonioo commented on GitHub (Jan 15, 2018):
Yes it is, the message says the en_US.UTF-8 locale is missing. You need to install it.
[FR]
Il faut lancer la commande dpkg-reconfigure locales comme indiqué plus haut afin de générer cette locale. Il faut bien sélectionner les deux versions lors du processus.
@CooperBarrett commented on GitHub (Jan 15, 2018):
I finally found my problem!
Actually, it wasn't from the locales.
I didn't have to do
service postgresql startbut use this command:service postgresql@9.6-main startI'm really struggling to find it.
So I'll have two questions:
service postgresql startdoes not work?postgresqldoes not launch or encounter an error during reboot.@ghost commented on GitHub (Mar 1, 2018):
service postgresql startstarts the default version which I think is 9.2 or 9.3 on debian. Debian uses the@version-namescheme to support multiple versions of the same software.To start PostgreSQL 9.6 at boot up run
sudo systemctl enable postgresql@9.6-main.serviceThis should work, I don't use debian and I didn't have much luck finding any documentation about this.
@tonioo commented on GitHub (Mar 2, 2018):
I do use Debian and it's the first time I see this... Maybe an ubuntu issue?
@CooperBarrett commented on GitHub (Mar 4, 2018):
I use debian stretch.
I manually restart postgresql with each reboot. For the moment, that's enough...
@pubmania commented on GitHub (May 27, 2019):
This is an year old issue which is closed but impacted my installation just today. Like @CooperBarrett mine is running on Debian Stretch so I tried restarting postgresql and sure enough it worked but am not sure what caused it to begin with and how to avoid it. Any suggestions will be hugely appreciated.