Open NormanBaechtold opened 2 years ago
Update: The issue appears to be related to an ungraceful stop of the docker-container by restarting the host machine. When executing docker restart freescout-app freescout-db freescout-db-backup
no errors appear in the log.
Leaving this open for developers to respond to this bug.
I have seen similar results with systems that restart but not anything related to MariaDB in the past. Since there are alot of things going on in the images, I have a script that actually restarts all of my docker containers upon host reboot for precisely this. To keep state during a reboot sometimes does not work as expected due to the complex initialization routines. Let's keep this open to understand if this is related to the freescout application container or the mariadb container.
Summary
After having set-up Freescout using the Docker-Image, Freescout seems to be up and running smoothly. I can configure a mailbox and send test-mails to my personal email-account through freescout. However, I cannot fetch mails, although the connection test for fetching mails sends a positive response. I don't run into fetch-errors. It is simply saying: "Fetched 0 new mails", when there are in fact unread mails in the mailbox.
After rebooting the VM (Debian 11 "Bullseye") and logging into Freescout again, I get several Errors in Manage > Logs > App Logs > Laravel 2022-04-11. It seems like the fetching issue is not related to incorrect cron jobs but incorrect database parameters at this point.
Steps to reproduce
git clone https://github.com/tiredofit/docker-freescout.git
from root. New directory /docker-freescout appears in root.docker pull tiredofit/freescout:latest
docker-compose up -d
What is the expected correct behavior?
That the DB is set up correctly when building the containers so that e-mails are successfully fetched.
Relevant logs and/or screenshots
Environment