Page 1 of 1

memory problem whit goautodial

PostPosted: Mon Oct 25, 2010 5:12 pm
by abdel-go
hello, I use goautodial 2.0 (Vicidial 2.2.1, Asterisk 1.4.27.1-vici, dahdi 2.3, vtigerCRM, Textcube 5.1.0, 3.5.14 Sangoma, CentOS 5.5) on an HP server prolient.
my problem appear after every 3 hours or 4 hours of server usage load on the memory exceeds 90% I inform you that I actively recording for all calls and to reduce the burden I have to restart my server every time, or empty the directory monitorDONE,
Please some one help me

PostPosted: Tue Oct 26, 2010 12:11 pm
by williamconley
1) As this is a specific GoAutoDial question, I have moved it to the appropriate Forum.

2) Please post your load information

3) When you say "i have to restart my server", please explain what causes the restart (i know, the memory is full, but why did you check the memory, what "happened" or didn't happen?)

4) How much memory do you have in this server?

5) EVERY time you post, you must post your vicidial version WITH BUILD (it's at the bottom left corner of almost every management screen) :)

6) What is Textcube and does it eat memory?

Re: memory problem whit goautodial

PostPosted: Wed Oct 27, 2010 3:09 pm
by gardo
You might want to read the Memory Management sticky here: http://www.vicidial.org/VICIDIALforum/viewtopic.php?t=9395.

And the GoAutoDial FAQs here: http://goautodial.com/wiki/goautodial-faq/.

abdel-go wrote:hello, I use goautodial 2.0 (Vicidial 2.2.1, Asterisk 1.4.27.1-vici, dahdi 2.3, vtigerCRM, Textcube 5.1.0, 3.5.14 Sangoma, CentOS 5.5) on an HP server prolient.
my problem appear after every 3 hours or 4 hours of server usage load on the memory exceeds 90% I inform you that I actively recording for all calls and to reduce the burden I have to restart my server every time, or empty the directory monitorDONE,
Please some one help me