ERROR: JobManager: Failed job running, Job CheckInboundEmails

[thanh]

Hi to all, I'm having some issues with my emails:

​ERROR: JobManager: Failed job running, job '673d4049cdb0275f7'. Job CheckInboundEmails 66e00254b9f4c50dd: [0] cannot read - connection closed?; at /data/apps/application/Espo/Classes/Jobs/CheckInboundEmails.php:60. [] []

Any ideas?

Thank you!

[victor]

- Do you have Crontab set up: https://docs.espocrm.com/administrat...ng-up-crontab?
- When you click "Test Connection" in IMAP settings of your Email Account what result do you get?

[thanh]

yes, I have setup cronjab setting, and when I click Test connection: Connection is Ok
In my case, sometime is failed with error above, sometime is success. I don't know why?

[victor]

Perhaps a similar solution will help you: https://forum.espocrm.com/forum/gene...5836#post95836
If no, please send a screenshot of your IMAP settings

[thanh]

Hi Victor, here my IMAP settings

[victor]

You are using the Outlook Integration extension: https://docs.espocrm.com/extensions/...n/setting-up/?
If not, then Outlook will definitely not work correctly.

[thanh]

Hello Victor,
I have enabled it, too. But some time have failed

[victor]

- Which version of EspoCRM and Outlook Integration extension are you using (recommend using current versions of EspoCRM 8.4.2 and Outlook Integration extension 1.3.5)?
- Does your Email Account always show Connected?
- In the browser you use when working with EspoCRM, go to you Personal or Group Email Account and click Disconnect.

- Then open an incognito tab of your browser (or another browser not used for working with EspoCRM) > log in > go to Personal or Group Email Account and click Connect.
These steps should eliminate the problem of the influence of your browser's cache on the connection process.
- Try changing Fetch Since.
- It will not be superfluous to send the full Espo error log after testing. Maybe there will be some more information that will help to understand the problem.

[thanh]

Hi Victor,
my Espocrm version: Version 7.2.7
and Outlook Integration extension 1.3.5, I have disonnect and Connect success againt.
But sometime I still get failed

[victor]

You didn't pay attention to https://forum.espocrm.com/forum/gene...rver#post95836. Judging by the old version of EspoCRM, you also have an old version of PHP. If it is older than php 8.1, this is already a problem. Since PHP 8.0 and lower is not compatible with OpenSSL 3.0.2.

Use the command in the CLI to check the version of PHP:

php -v

Use the command in the CLI to check the version of OpenSSL:

openssl version -v

The best solution in this case would be to update PHP to at least 8.1, and preferably to 8.3. After that you can update your instance to the current version (8.4.2 for today). And then continue testing.

____________________

The following recommendations make sense if you've checked the previous ones (about PHP and OpenSSL versions) and you're fine.

Please send the following screenshots:
- Screenshot Administration > Scheduled Jobs > Check Group Email Accounts.
- Screenshot Administration > Scheduled Jobs > Check Personal Email Accounts.
- Screenshot Administration > Job Settings.

Additionally in Check Personal Email Accounts or Check Group Email Accounts, you can make Inactive Status > Save changes > Active Status again.

Do you have a similar problem with all Email Accounts or just one? This can be detected in the following way:
1. Go to Administration > Scheduled Jobs > Jobs and filter Failed Jobs for Personal or Group Email Account.
2. Inside each of them there is a Target ID.
If the Target ID is always the same, then the problem is with only one Email Account.

[thanh]

Hi Victor,
My php verion:

PHP 8.0.28 (cli) (built: Feb 14 2023 18:32:57) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.28, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.28, Copyright (c), by Zend Technologies
​

and openssl version:

openssl version -v
OpenSSL 1.1.1f  31 Mar 2020​

and my ubuntu serrver version is: 20.04
my espocrm verrsion 7.2.7 is running good with this php version, right?

[victor]

I have already given a detailed answer and solution to your question:

"The best solution in this case would be to update PHP to at least 8.1, and preferably to 8.3. After that you can update your instance to the current version (8.4.2 for today). And then continue testing."