Calendar notifications slow or freeze GUI

[Gregory]

Hello,
I’m using egroupware since a long time now and that is why I am very surprised by this problem.

• When I click on “Save” button on new calendar event window, the GUI freeze. (10 minutes sometimes)

After investigation, I realized it’s related to notifications, if I turn on the checkbox “don’t send notifications”, the problem doesn’t appear.
Apparently the GUI wait until all email notifications are sent, I watched my mail server log and egroupware send all emails just right after the button is clicked and don’t wait the next cronjob.

• Egroupware 17.1.20190529
• Notifications are enable (egroupware “popup” and email), on invitation for the calendar.
• Asynchrone jobs runs fine (ex : calendar alarms)

additional information :
When an event is saved, the call that stuck the GUI is : json.php?menuaction=notifications.notifications_ajax.get_notifications

No one 's having this problem?
Please don’t hesitate to give me informations.
Thanks !

[StefanU]

Hi Gregory.

You should first look at the web server error log. Usually there is a hint there.

No one 's having this problem?

Think no.

Egroupware 17.1.20190529

Then it is time for an update!

Stefan

[Gregory]

Hi, thanks for your response. Unfortunately nothing is relevant in my web server log, no error.
If no one has this problem, then that means that the normal behavior of EgroupWare is to send invitations emails async, and not while the calendar event is registered…

For the update yes, I know, but docker slow me down a little bit.

[StefanU]

the normal behavior of EgroupWare is to send invitations emails async, and not while the calendar event is registered…

No. At that moment you are sending through your active account.

What has changed?
Does that happen to other users?

For the update yes, I know, but docker slow me down a little bit.

Why?

Stefan

[Gregory]

“Nothing” has changed, or I don’t know what…I just recently added some users, but no change on configuration point of view.

And yes it happen for all my users, for information I use only one global SMTP, specific users emailq configurations are not set.

For the update, I tried once but I have an nginx error “502 BAD GATEWAY”, and
docker logs -f egroupware-nginx 2>&1 | sed 's/PHP message/\nPHP return me :
2020/06/12 13:22:58 [error] 6#6: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.0.1, server: _, request: “GET /egroupware/ HTTP/1.1”, upstream: “fastcgi://172.20.0.3:9000”, host: “192.168.100.59”

I haven’t investigate further, moreover I don’t know docker well.

[Gregory]

Ok ! I found something !

Thanks for your question “What has changed?”

Effectively, recently, one month ago I think, I reinstalled my SMTP server, so I tried something : send a message with telnet and this smtp.I noticed that it was taking a few seconds to accept sender and recipient address : The first DNS server on this machine was invalid.

Once the DNS server has been corrected, new calendar event are saved in “few” seconds, instead of minutes…

GREAT !

BUT, I’m really surprised…this emails should be sent async, many problems can occur and shouldn’t block the GUI .
Furthermore, the freeze is directly dependent of the number of participants,even if emails are sent quickly.

However thank you for this program, it’s a beautiful work.

[RalfBecker]

For the update, I tried once but I have an nginx error “502 BAD GATEWAY”

In that case it makes sense to look in the log of the egroupware container itself, as only once EGroupware runs and you no longer get a 502 Bad Gateway, errors are reported to Nginx / the webserver.

Furthermore, the freeze is directly dependent of the number of participants,even if emails are sent quickly.

This will change with the next release, as we then can respond back to the user, continue sending notification mails and if all send successful or some failed report that via a push notification back to the user.

However thank you for this program, it’s a beautiful work.

Thanks

Ralf

[StefanU]

For the update, I tried once but I have an nginx error “502 BAD GATEWAY”, and

502 we had several times a few months ago. There were different constellations that caused this. But we should avoid them mostly by correcting the installation scripts. So I have to ask:
When did you try this?
When’s the installation date?

You should read this:
Wiki:
19.1 Installation using egroupware docker RPM DEB package
19.1 Release notes and distribution specific instructions
Update recommendations and troubleshooting

Forum:
My installation of EGroupware 19.1 on Debian 10
Docker (in EGroupware 19.1)?
And from here, of course:
EGroupware 19.1 Release Notes / Changelog

If you try it again and you find such a problem, create a new (!) topic here in the forum. Until then please mark this one as solved.

User manual Forum

Stefan

[Gregory]

Done.

To answer your questions, I tried to update to 19.1 the same day (June 12),
The installation date I don’t remember well, on this server, for the version 17.X perhaps one year…
By the way thanks for the links, I will try a new update later.
Grégory.