The script ran fine, I only caught this error:

Fetching new images, if any...
ERROR: Named volume "xmpp-vol-1:/home/ejabberd/database:z" is used in service "ejabberd-mailcow" but no declaration was found in the volumes section.
Checking IPv6 settings...
Starting mailcow...
ERROR: Named volume "xmpp-vol-1:/home/ejabberd/database:z" is used in service "ejabberd-mailcow" but no declaration was found in the volumes section.
Collecting garbage...

after the update was finished no contaienr was running. trying t docker-compose up -d resulted in this error:

ERROR: Named volume "xmpp-vol-1:/home/ejabberd/database:z" is used in service "ejabberd-mailcow" but no declaration was found in the volumes section.

I need some advice please. i don’t use ejabberd at all - waht to do?

  • sorry I dropped the ball but I must have missed the email notification about your reply. Unfortunately its too long ago and I can’t remember, lets drop this issue for now.

to get mailcow up and running again I have added the volumes at the end of the docker-compose.yml file but how did this happen? as far as I know the upgrade.sh script also updates docker-compose.yml so how come?

volumes:
  vmail-vol-1:
  vmail-index-vol-1:
  mysql-vol-1:
  mysql-socket-vol-1:
  redis-vol-1:
  rspamd-vol-1:
  solr-vol-1:
  postfix-vol-1:
  crypt-vol-1:
  sogo-web-vol-1:
  sogo-userdata-backup-vol-1:
  xmpp-vol-1:
  xmpp-upload-vol-1:

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

ovizii changed the title to Problems after running update.sh .

  • MAGIC

    • Forum Staff
    • volunteer
    Moolevel 48
  • Post #4

Hm that’s odd yes. Do you know when you did the last update?

13 days later

sorry I dropped the ball but I must have missed the email notification about your reply. Unfortunately its too long ago and I can’t remember, lets drop this issue for now.

No one is typing