Message output airnotifier servers timeout

Message output airnotifier servers timeout

by Aitor Renobales Irusta -
Number of replies: 1

Hi all,

Since first days of January we are facing a timeout issue related to airnotifier servers.

Forum posts generated messages should be send almost inmediately (cron mod_forum task is executed every minute), but we realize that they were delivered to end-users with delay which was getting longer as the hours go by.

As we were tracing the code, we conclude that, after Moodle execute "/message/output/airnotifier/message_output_airnotifier.php", the "message.moodle.net" farm is not responding requets as it should, as you can see below:

---------------

access("<dirroot>/message/output/airnotifier/message_output_airnotifier.php", R_OK) = 0
access("<dirroot>/message/output/airnotifier/settings.php", R_OK) = 0
...

connect(7, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("52.48.236.19")}, 16) = -1 EINPROGRESS (Operation in course)
poll([{fd=7, events=POLLOUT|POLLWRNORM}], 1, 0) = 0 (Timeout)
poll([{fd=7, events=POLLOUT}], 1, 1000) = 1 ([{fd=7, revents=POLLOUT}])
poll([{fd=7, events=POLLOUT|POLLWRNORM}], 1, 0) = 1 ([{fd=7, revents=POLLOUT|POLLWRNORM}])
getsockopt(7, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
getpeername(7, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("52.48.236.19")}, [128->16]) = 0
getsockname(7, {sa_family=AF_INET, sin_port=htons(26437), sin_addr=inet_addr("10.0.100.215")}, [128->16]) = 0
...
getpeername(10, 0x7ffd05de7c30, [112])  = -1 ENOTCONN (Peer is not connected)

...

poll([{fd=7, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=7, events=POLLIN}], 1, 1000)  = 0 (Timeout)

----------------------


Is Moodle facing any disruption of its service?

Is there any recommended workaround to prevent mentioned delay?

Thanks in advance,

Aitor


Average of ratings: -
In reply to Aitor Renobales Irusta

Re: Message output airnotifier servers timeout

by Isabel Renedo -
Picture of Moodle HQ Picture of Particularly helpful Moodlers
Some days ago we detected that one of our production servers was having issues, we detected that traffic for certain regions was not properly routed, we restarted some services. The main issue was solved. 

For old Moodle sites (*) take into account https://tracker.moodle.org/browse/MDL-65970. If you need help upgrading your site, please consult the Moodle documentation (Upgrade overview, Upgrading, ..).

Kind regards,

Isabel

(*) versions <3.6.7 or <3.7.3