vicidial.org

Hi All,
I installed Vicidial 2.9rc1 with Asterisk 1.8 and MySql 5.5.43

I would like if it is possible to kill the vicidial process like (ASTVDauto, ASTVDadapt ..) without restarting the server.

Is there a script that can find vicidial PIDs and kill them?

Thank you

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Restart all vicidial processes: (Note: I have no idea if this works on such an old version of Vicidial, but it is from old notes)

Code: Select all

screen -list | grep ached | grep asterisk -v | awk '{print $1}'| awk -F'.' '{print $1}' | xargs kill
killall -9 FastAGI_log.pl
perl /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

Happy Hunting!

Thanks a lot for your response.
Excuse my English, I use the internet

I'm a new recruit,
I found the application installed on two servers,

first server: apache + mysql
second server: asterisk 1.8.23

There is a task that restarts the servers every night to clear the memory, if the servers are not restarted, the next day i find the RAM used at 100%.
I just want to initialize the VICIDIAL services instead of restarting the servers,
is that a good idea?

in advance thank you
---------------------------------
vicidial 2.9rc1
BUILD: 140612-1628
Asterisk 1.8.23
Sangoma Hardware
MySql 5.5.43
---------------------------------
server characteristics: (lscpu command)

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 45
Stepping: 7
CPU MHz: 2000.134
BogoMIPS: 3999.50
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 15360K

The script initializes VICIDIAL services well,
so I restarted the Mysql and apache services,
but the memory stays full,
only the restart of the server that initializes the memory

thank you for your help.

I suspect your "memory is at 100%" is actually incorrect. The fact that all the memory has been used in the past does not mean there is no memory available presently. This is a feature of mySQL, it will use up all the available memory and yet mark it available for harvesting by the OS. This way mysql CAN access previous query responses in memor pages that have not yet been harvested, thus saving time and HD reads.

You sound like someone from the microsoft world trying to make linux work like microsoft. Next you'll try to defrag the HD. lol

Hint: Reboot is for memory leaks that cause instability. The symptom is that the system REQUIRES a reboot every few days in the middle of the workday. Some systems do not require this. In fact, most (recently) do not. But the cost of rebooting is ... Zero. Thus rebooting anyway (in case your system needs it) is not about 100% memory utilization, it's just about avoiding the possibility that you MAY need to reboot in the middle of a workday, thus costing money. Especially since it often takes 30-60 minutes of "What the heck is goin' on?" before someone says "hey, let's reboot the server and see if that fixes this very unusual problem!"

So to recap: Can you demonstrate what you believe to be the "memory is full" proof? Are you certain it's "full" and not merely "being utilized properly by the OS as designed"? Most importantly, have you experienced an actual symptom that is resolved by the reboot? (Memory full is not a symptom ... any more than power being used!)

That's right, I came from the Microsoft world

Below, the status of the "Top" command on one of our servers that has not been restarted for several days, the memory is almost 100% used,
(server all in one with 64 Go of RAM )

With this state, I receive complaints of slowness, if I initialize the vicidial services and also restart MYSQL and apache, memory usage remains high,

Only a restart of the server frees up the memory.

What I have learned from your answer is that restarting is not necessary every day, but once a week will be enough.

Finally a big thank for you.


------------------------------------------------------
Tasks: 338 total, 1 running, 337 sleeping, 0 stopped, 0 zombie
%Cpu(s): 1,0 us, 0,5 sy, 0,0 ni, 98,4 id, 0,1 wa, 0,0 hi, 0,0 si, 0,0 st
GiB Mem: 62,922 total, 62,639 used, 0,284 free, 0,208 buffers
GiB Swap: 63,873 total, 0,002 used, 63,871 free. 57,822 cached Mem


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1348 mysql 20 0 2595912 104848 6480 S 16,6 0,2 2424:53 mysqld
2595 root 20 0 12,038g 49328 10292 S 7,6 0,1 3086:27 asterisk
14083 root 20 0 0 0 0 S 6,3 0,0 0:17.78 kworker/0:2
15009 root 20 0 118136 9808 5452 S 2,0 0,0 0:00.06 AST_manager_kil
15006 root 20 0 122452 10016 5612 S 1,7 0,0 0:00.05 AST_CRON_audio_
4848 root 20 0 170360 58432 5968 S 1,3 0,1 7:06.17 AST_VDadapt.pl
11849 www-data 20 0 302040 21800 15712 S 1,3 0,0 0:09.77 php5-fpm
17987 www-data 20 0 2012836 10852 3208 S 1,0 0,0 1:34.01 apache2
2699 root 20 0 132896 14988 6124 S 0,7 0,0 493:13.93 AST_update.pl
2702 root 20 0 123564 11708 6016 S 0,7 0,0 591:26.87 AST_manager_sen
5610 www-data 20 0 2011132 7752 3208 S 0,7 0,0 0:31.95 apache2
10948 root 20 0 23796 3116 2420 R 0,7 0,0 0:04.69 top
11858 www-data 20 0 302000 20956 14944 S 0,7 0,0 0:09.47 php5-fpm
12598 www-data 20 0 302104 20668 14628 S 0,7 0,0 0:07.23 php5-fpm
3 root 20 0 0 0 0 S 0,3 0,0 167:47.94 ksoftirqd/0
8 root 20 0 0 0 0 S 0,3 0,0 149:07.99 rcu_preempt
76 root 20 0 0 0 0 S 0,3 0,0 0:59.04 ksoftirqd/13
398 root 20 0 41160 14464 14172 S 0,3 0,0 14:57.57 systemd-journal
791 root 20 0 27508 2776 2492 S 0,3 0,0 3:11.14 cron
2502 root 20 0 443660 331684 5936 S 0,3 0,5 271:09.15 AST_VDauto_dial
5612 www-data 20 0 2011656 9252 3204 S 0,3 0,0 0:47.70 apache2
1 root 20 0 28664 4392 2800 S 0,0 0,0 6:10.83 systemd

We recommend daily if at all possible. Otherwise you'll find that you may "get away with" weekly for a few weeks, but still in the middle of a week once in a while you'll lose production to an odd problem and then have to reboot.

And rebooting, as mentioned, is free. There is no "bonus" for not rebooting your server daily. Also, it gives the system a chance to check the HD for errors.