Creating a new field in email entity times out

[Emmker]

I try to create a field in email entity and it times out in around 40-50 seconds

The email records are around 200.000 or more

I do not have the same problem with any other entity.

I have tried boolean and enum type of fields with no luck.

Any ideas about why?


My server has 16gb ram dedicated to the espo, 8 cpus and the optimizations o mysql are
innodb_buffer_pool_size = 8G
innodb_buffer_pool_instances = 8
innodb_log_file_size = 2G
innodb_flush_log_at_trx_commit = 2
sort_buffer_size = 4M

[Vadym]

Hi Emmker,

Please provide the EspoCRM error log, web server error log, and a screenshot of Administration -> System Requirements to get more details about this issue.

[Emmker]

The error log:

[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] ERROR: Workflow [66471ab5ee10769a1]: Action failed, [executeFormula] [0], SQLSTATE[42S22]: Column not found: 1054 Unknown column 'email.c_test' in 'field list'.
[2024-09-15 21:00:36] CRITICAL: (HY000) Failed job 66e744065c6ef54c8. SQLSTATE[HY000]: General error: 2006 MySQL server has gone away :: /var/www/espocrm/application/Espo/ORM/Executor/DefaultSqlExecutor.php(77)
[2024-09-15 21:00:36] ERROR: (0) Uncaught Exception LogicException: "SQLSTATE[HY000]: General error: 2006 MySQL server has gone away" at /var/www/espocrm/application/Espo/Core/Job/JobRunner.php line 63 :: /var/www/espocrm/application/Espo/Core/Job/JobRunner.php(63)​ 

No errors on apache

[yuri]

Maybe the 'email' table is constantly read and written while you are creating the field. Maybe try to disable cron, set the maintenance mode (Administration > Settings), wait for a minute and then try to create your field.

Also check whether there's enough disk space on the server. MySQL may go away when it's not enough.

[yuri]

BTW. Does the email's list view load fast for you?

[Emmker]

Yes, as fast as always.

[Emmker]

Maybe the 'email' table is constantly read and written while you are creating the field. Maybe try to disable cron, set the maintenance mode (Administration > Settings), wait for a minute and then try to create your field.

Also check whether there's enough disk space on the server. MySQL may go away when it's not enough.

In maintenance mode same result.
The disk space is more than ok.

I will disable cron tonight to check, and get back.

Edit: same behaviour with disabled cron.
Should I try with disabled workflows too?

[Emmker]

I have new data for the problem.
First of all it still persists.

Second, I found out that every email workflow that I have created, still works, but when I get in the workflow, without clicking the edit button, after some 20-30 seconds it throws a timeout error on the top.

Mind , that the error is not visible in the /data/logs file.

The other workflows (case, task etc) are working and have logs just fine, except from a scheduled workflow that has this script as action:

$lastEmail = record\findOne(
'Email',
'createdAt', 'desc',
'parentId', id,
'isReplied', false,
'createdAt>', '2024-04-01',
'fromEmailAddressId!=', '658578db1ea46a67b'
);

ifThen($lastEmail != null,
record\update('Case', id, 'status', 'Needs Reply')
);

Edit:
Just found out that I have many reports that give the timeout error and do not have logs either. Regardless of entity.

[shalmaxb]

from the error log, I guess you have some orphan data from a field called email_ctest. It can happen, that you delete a field in the GUI, but it is kept in database and/or json file. As you use workflow, maybe there this field is called also, but does not exist anymore.

[Emmker]

I did remove the chest field.
It was one of my tries to add a field.
When it fails, it leaves a broken field as residue.

But the problem is still there

[shalmaxb]

Did you delete that field from MySQL database also?

[Emmker]

It seems that the "timeout error" that I got for the other workflows was because of the backing up procedure of my server.
The thing is that the problem that prevents me from adding a filed to the email entity is still present.

I have tried so far:
- Disabling the cron waiting 10 minutes and trying again. (no luck)
- Disabling the cron, set maintenance mode waiting 10 minutes and trying again. (no luck)
- Enlarge the disk space, now having more than 120gb free space (no luck)

Any ideas what to try next?