-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh install - Table 'mailcow.versions' doesn't exist #3265
Comments
hard to tell what is happening in case people remove deliberatly remove/delete the bug report template. |
I have the same problem. see #3285 for an issue following the bug template... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still no valid template used for tracking -> No chance to reproduce, closed |
I have the same problem with a fresh install.
root@ha01 /opt/mailcow-dockerized # docker-compose -v root@ha01 /opt/mailcow-dockerized # docker -v |
I ran into the same issue with fresh install. What worked for me was following this #2970 (comment) but I had to add
|
I had this problem too, on a fresh install on BurmillaOS. Moreover I had to manually stop all the mailcow containers besides mysql to prevent a deadlock when fording the mysql_upgrade command. |
This is still an issue with a completly fresh and new install. The sogo container is also throwing this:
When I checked the mysql container, it does have the db called "mailcow" (which is defined in the mailcow.conf) but the tables are not existing. The whole db is empty. Tried docker compose down -v --rmi all --remove-orphans then docker compose up -d nothing changed. |
Just download the entire docker stuff today for this, and I'm seeing the same error in the logs. sogo-mailcow-1 | Waiting for schema update... |
Same. I am almost at the point to just try another mail server solution. |
After a fresh install I have this line in my log :
And I can't connect : https://${MAILCOW_HOSTNAME} (Preparing ..)
Other logs seems to be ok :
docker-compose logs --tail=1000 php-fpm-mailcow
docker-compose logs --tail=1000 mysql-mailcow
I try to make docker-compose down -v and docker-compose up -d but I have the same problem
I have just launch ./generate_config.sh and make no modification.
I can connect on mysql instance with root and user ( docker-compose exec mysql-mailcow mysql -u mailcow -p)
but the table doesn't exist
Thank for your help
The text was updated successfully, but these errors were encountered: