Prior to placing the issue, please check following:(fill out each checkbox with an X once done)
[X] I understand, that not following or deleting the below instructions, will result in immediate closing and deletion of my issue.
[X] I have understood that answers are voluntary and community-driven, and not commercial support.
[X] I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description of the bug:
I have a cronjob that does a backup every night that pipe the backup output to a file that is archived. backup_and_restore.sh backup all > logfile.txt
A few days ago I started getting data coming to stdout instead of the file, since my backup jobs run through cron and pipe to a report I usually only see stderr in my cron emails, but that is no longer the case.
run a backup that includes sql and pipe it to a file.
System information:
Question
Answer
My operating system
Ubuntu 18.04.4 LTS
Is Apparmor, SELinux or similar active?
No
Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported
No
Server/VM specifications (Memory, CPU Cores)
16gb ram, 4 cores
Docker Version (docker version)
19.03.7
Docker-Compose Version (docker-compose version)
1.25.4
Reverse proxy (custom solution)
caddy
Output of git diff origin/master, any other changes to the code? If so, please post them.
All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat.
DNS problems? Please run docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and post the output.
Prior to placing the issue, please check following: (fill out each checkbox with an
X
once done)Description of the bug:
I have a cronjob that does a backup every night that pipe the backup output to a file that is archived.
backup_and_restore.sh backup all > logfile.txt
A few days ago I started getting data coming to stdout instead of the file, since my backup jobs run through cron and pipe to a report I usually only see stderr in my cron emails, but that is no longer the case.Seems to be related to this commit: https://github.com/mailcow/mailcow-dockerized/commit/a1156c38fc03ad454a139f0be0da446e192fc527#diff-eb10ec60ac73ac11924fa7b0e9fb6109
Thanks!
Docker container logs of affected containers:
N/A
Reproduction of said bug:
run a backup that includes sql and pipe it to a file.
System information:
docker version
)docker-compose version
)git diff origin/master
, any other changes to the code? If so, please post them.iptables -L -vn
,ip6tables -L -vn
,iptables -L -vn -t nat
andip6tables -L -vn -t nat
.docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254
(set the IP accordingly, if you changed the internal mailcow network) and post the output.