Closed KarstenHahn closed 6 years ago
@KarstenHahn What errors appeared? Can you get use a dump of docker-compose logs
?
@Daniel133 Which missing images? Best thing is to create a new issue and dont hijack another one!
ERROR: for dovecot-mailcow manifest for mailcow/dovecot:1.23 not found ERROR: for clamd-mailcow manifest for mailcow/clamd:1.9 not found ERROR: manifest for mailcow/dovecot:1.23 not found manifest for mailcow/clamd:1.9 not found
It works now.
thats all after update.sh
root@mailcow:/opt/mailcow-dockerized# ./update.sh
Checking internet connection... OK
Checking for newer update script...
From https://github.com/mailcow/mailcow-dockerized
* branch master -> FETCH_HEAD
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Stopping mailcow...
Removing network mailcowdockerized_mailcow-network
WARNING: Network mailcowdockerized_mailcow-network not found.
Committing current status...
root@mailcow:/opt/mailcow-dockerized#
Try to start the containers again and rerun the update script.
after docker-compose up -d the system run. after ./update.sh
./update.sh
Checking internet connection... OK
Checking for newer update script...
From https://github.com/mailcow/mailcow-dockerized
* branch master -> FETCH_HEAD
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N] y
Stopping mailcow...
Stopping mailcowdockerized_rspamd-mailcow_1 ... done
Stopping mailcowdockerized_acme-mailcow_1 ... done
Stopping mailcowdockerized_netfilter-mailcow_1 ... done
Stopping mailcowdockerized_nginx-mailcow_1 ... done
Stopping mailcowdockerized_php-fpm-mailcow_1 ... done
Stopping mailcowdockerized_portainer-mailcow_1 ... done
Stopping mailcowdockerized_postfix-mailcow_1 ... done
Stopping mailcowdockerized_watchdog-mailcow_1 ... done
Stopping mailcowdockerized_memcached-mailcow_1 ... done
Stopping mailcowdockerized_clamd-mailcow_1 ... done
Stopping mailcowdockerized_ipv6nat_1 ... done
Stopping mailcowdockerized_dockerapi-mailcow_1 ... done
Stopping mailcowdockerized_mysql-mailcow_1 ... done
Stopping mailcowdockerized_sogo-mailcow_1 ... done
Stopping mailcowdockerized_redis-mailcow_1 ... done
Stopping mailcowdockerized_unbound-mailcow_1 ... done
Stopping mailcowdockerized_dovecot-mailcow_1 ... done
Removing mailcowdockerized_rspamd-mailcow_1 ... done
Removing mailcowdockerized_acme-mailcow_1 ... done
Removing mailcowdockerized_netfilter-mailcow_1 ... done
Removing mailcowdockerized_nginx-mailcow_1 ... done
Removing mailcowdockerized_php-fpm-mailcow_1 ... done
Removing mailcowdockerized_portainer-mailcow_1 ... done
Removing mailcowdockerized_postfix-mailcow_1 ... done
Removing mailcowdockerized_watchdog-mailcow_1 ... done
Removing mailcowdockerized_memcached-mailcow_1 ... done
Removing mailcowdockerized_clamd-mailcow_1 ... done
Removing mailcowdockerized_ipv6nat_1 ... done
Removing mailcowdockerized_dockerapi-mailcow_1 ... done
Removing mailcowdockerized_mysql-mailcow_1 ... done
Removing mailcowdockerized_sogo-mailcow_1 ... done
Removing mailcowdockerized_redis-mailcow_1 ... done
Removing mailcowdockerized_unbound-mailcow_1 ... done
Removing mailcowdockerized_dovecot-mailcow_1 ... done
Removing network mailcowdockerized_mailcow-network
Committing current status...
root@mailcow:/opt/mailcow-dockerized#
Why would it quit after Committing current status...
? Seems more like your system is broken.
Yes, sorry.
Hmm. Setup a new instance (debian 9) according to the install docs with that result:
Have you any ideas? Thx, Karsten
Why is that? Did you run docker-compose up without a -d
?
Can you please run docker-compose down; systemctl restart docker; ./update.sh
? 👍
@andryyy : no, docker-compose logs>e2.txt
just done the update.sh.
It seems that the mail-server is started somehow -- Thinderbird gives an certificate error because it is accessing with the "old" credentials. But i can't access the admin UI. And so I can not configure the system.
In the logs I found these error msgs: nginx-mailcow_1 | nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2018/02/28 19:44:54 [emerg] 10#10: could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2018/02/28 19:44:55 [emerg] 10#10: could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2018/02/28 19:44:57 [emerg] 10#10: could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed nginx-mailcow_1 | 2018/02/28 19:45:00 [emerg] 10#10: could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 nginx-mailcow_1 | nginx: configuration file /etc/nginx/nginx.conf test failed
Can this be a hint?
Karsten
Hi,
I've started the update.sh script (not-customized installation). After updating the update script and restart update.sh. errors appeared (pulls failed)
While starting docker-compose up (without -d) a compilation task (!!!) was started. I've never seen this on previus updates.
To analyse it: what logs do you need? I'm not a docker guru so it is the best to guilde me through the necessary commands.
Thanks, Karsten