[asterisk-users] 1.8.11.0 - CLI error res_timing_timerfd

[Stefan Viljoen]

Hi all

Sometimes (about every three months) some of my Asterisk 1.8 boxes will
start running this message thousands of times in the CLI:

[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument
[Feb 12 14:18:23] ERROR[28129]: res_timing_timerfd.c:180 timerfd_timer_ack:
Call to timerfd_gettime() error: Invalid argument

ad infinitum

Sometimes, this will disappear after a few minutes, and not re-appear. On
other occassions, after this started appearing in the CLI, the Asterisk will
crash without any slowdown or problems. On yet other occassions, the box
will start getting slower, load average rising and rising until it become
virtually frozen and it has to be rebooted in order to come back up in a
functional state again.

I've also noticed that stopping the Asterisk process and restarting it does
not help  if this error is in effect and a slowdown (rising load average)
has started - the whole physical machine has to be rebooted in toto.

I'm running on Centos 6.5.

Anybody else seen this message before? What does it mean?

Thanks

Kind regards

Stefan