queue:work is a central but fragile element in freescout

[onderzoekspraktijk]

I am for several weeks now testing freescout and daily get al kinds of silent errors because queue:work stops at random. In the beginning the cron was not set perfect: now it is. All reproted systems settings were and are 'green'. It took hours to 'modernise' alle gsuite mail connection.
Still after all that I never know if/when e-mails are (really) sent; I never know if all incoming mail is fetched. To be sure I have to flush the cache, import mails, and wait a bit. Suddenly lots of mails appear inbound and outbound. and after that I see a green message that indicate that queue:work now 'runs'.
I see others report issues with queue:work.
I do not see any development roadmap where a better and more robust solution for this is described.

If I am the only one that finds this more or less a showstopper: please ignore this message. If not: is there a way to solve this issue?

Best regards,
Paul

[freescout-helpdesk]

Are you using Docker or Cloudron?

[onderzoekspraktijk]

Neither.
I created a subdomain on a regular webserver (hosting by Rochen) dedicatedonly to freescout, downloaded the latest freescout version from Github and installed it there.
I am not sure if something went wrong with the install. As all config settings (php extensions and setting) are reported to be ok I do not know how to check any further.

Does the software work? Yes, occasionally; but at random it stops working and never gets active again untill I flush the cache and click Fetch emails in the tools menu.

[onderzoekspraktijk]

Just now sent two emails. In Freescout they are labeled as sent inside the mailbox, but the log does not 'see' them at all; and the system status reports the as 'Queued Jobs'.
Only the queu does not run; also it doens not run after clearing cache (as advised in such cases), and seral clearances of said cache also do not solve this issue; and neither does manually executing the command to fetch mails.

Until 10 minutes later I can see (using another mailclient) they are sent.

[freescout-helpdesk]

Feel free to submit a pull request if you have some solution for this.

[onderzoekspraktijk]

I am not a coder, I can only test and describe what I see. I do not understand why and how the issue I have is there. I am sorry if the feed-back I sent does not help in any way to solve it.

Best regards,
Paul

[freescout-helpdesk]

Closing for no activity.

[onderzoekspraktijk]

Sorry to see this issue is closed for lack of activity.

The issue itself still closes the app regularly.
I kept looking for clues as to how and why.
I found that each error is mailed to the default email account of the site itself, citing a very large numer like 2982782 an reproting the cron job as killed.

best regards,
Paul

[JSM25]

Can I ask whether you got frescount to work with Rochen in the end without any issues? I have been using Sitegound, but it's far from perfect, and they keep shutting me down as I am using too many CPU/Sec a month which looks to be due to the CRON job running every minute.

I have not managed to sort out the PS(shell) not found, I would be interested to know if you have this issue with Rochen

[onderzoekspraktijk]

Well, I learned to live with the issues. I do not need to send lots of mails every hour, so in the event of a new mail that needs to be sent I check if the queue:work is running. It depends: mostly it is not, sometimes it runds for days on end. If it does not run, I flush the cache, and the run the alternative cron job for a minte. That allways triggers queue:work. After that he mail(s) will be sent. Functions are all green in my status settings (where all other settings are also in the green). I suggest you set cron to 5 minutes and see if that helps.

…

-- _QOMBO [https://www.qombo.nl/]_ Paul Kleingeld Hondiusstraat 48 3021 NM  Rotterdam _ _010 4773729 ***@***.***

----------------------------------------------------------- ## freescout-helpdesk/freescout, op Oct 31 @ 10:55 (Europe/Paris): Can I ask whether you got frescount to work with Rochen in the end without any issues? I have been using Sitegound, but it's far from perfect, and they keep shutting me down as I am using too many CPU/Sec a month which looks to be due to the CRON job running every minute. I have not managed to sort out the PS(shell) not found, I would be interested to know if you have this issue with Rochen https://user-images.githubusercontent.com/27293201/198980496-08a813ed-baf7-49a3-bd86-d289af24cdfb.jpg [https://user-images.githubusercontent.com/27293201/198980496-08a813ed-baf7-49a3-bd86-d289af24cdfb.jpg] — Reply to this email directly, view it on GitHub [#661 (comment)], or unsubscribe [https://github.com/notifications/unsubscribe-auth/ACOQNXTJLN5IZ77GQWKJDJDWF6JKHANCNFSM4OVSCTXA]. You are receiving this because you authored the thread. https://github.com/notifications/beacon/ACOQNXVKFHMWGSJS2ONJG2DWF6JKHA5CNFSM4OVSCTXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJVGF3ZQ.gifMessage ID: ***@***.***>