Dialparties.agi freezing up?

After running asterisk for about 72 hours, things start slowing down. Specifically, calls from a queue don’t ring at agents, there are delays in every step of the dialplan, etc. When it happened today, i noticed that there where five instances of dialparties.agi running for bore than half an hour and the system load was 9.0. I imedaitly killed the running prosses, and checked the logs. The following error was in /var/log/messages:

Oct 15 19:42:19 asterisk php: /var/lib/asterisk/agi-bin/phpagi-asmanager.php[731]: date(): It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Asia/Jerusalem' for 'IST/2.0/no DST' instead

Could this error have caused asterisk to slow down like the Brooklyn bridge during rush hour? What does the error even mean?
UPDATE: it seems that this error apears in the log file every 5-10 minutes. It shows many times for the same second.
This is a listing of the last 1000 unique instances.
This is the last 1000 actual instances. Notice how its only two minutes worth!

the date.timezone error is not an issue. You can set it in the php.ini file if you want and in any event you should have TZ set in /etc/profile because if not you may get incorrect times from things like speaking clock. But that is not going to create any issues and it is defaulting to your correct timezone. As far as why you are finding zombie dialparties.agi scripts not sure what is going on there. Hopefully it is not related but you could try to change the call to dialparties from AGI() to DeadAGI() and see if it keeps happening. Sounds kind of like some old problems that used to exist with earlier versions of 1.2 on heavily loaded systems.

Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx

update - tuesday

I hade changed agi to dead agi this morning, and was having the same issues all day. Im not sure that really has anything to do with dialparties.agi…

neither do I but it rules out being related to that old issue. I say go back to Asterisk 1.2 and see what happens. It is easy enough to switch back and forth between the two revisions.

Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx