Closed xxtim42xx closed 6 years ago
Did you always run update.sh with umask 0022?
No can you please Explain?
Try sudo -i
and then umask
. If it says 0022 you're good to go using update.sh as root via sudo -i
.
If you used update.sh without the appropriate umask before, your folders might have had inappropriate permission settings which led to a broken update path.
EDIT: You also should have come in touch with this topic in the docs: https://mailcow.github.io/mailcow-dockerized-docs/install/
It returns 0022 so I think its ok?
Well the point is: Did you run the installation and update.sh as root via sudo -i / umask 0022 before? If not, you may have borked your instance; this happened to me on two instances of which one I had to completely reinstall after some updates in the process.
EDIT: Good catch by @MAGICCC 😼.
It seems you changed some lines in docker-compose.yml. Do you know which ones?
Yes, I think MTU value from the Network bridge. Is that the problem?
It's worth a try I'd say, do you agree @MAGICCC ? You could git stash
your changes or try a git checkout
on the docker-compose.yml and then update again.
I think git stash
worked.
After the Mailcow Update with ./update.sh there are still new versions available. I check this with ./update.sh --check
I think there is a failure when I use ./update.sh. Here is the Output:
Thanks for an answer.