Page 1 of 1

Perl Process don't move MIX recording

PostPosted: Tue Mar 06, 2018 3:04 pm
by cromerorey
Hi

VERSION: 2.14-585a
BUILD: 170114-1356
Install VIcibox Cluster (1 DB,WEB - 1 Dialer)
Installed with ViciBox_v.7.x86_64-7.0.4.iso
Asterisk 11.25.1-vici

The folder /va/spool/asterisk/monitor is full because the scritp to Move the recordings after MIX do not operate.

viciboxDIAL:/var/spool/asterisk/monitor # df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.8G 0 7.8G 0% /dev
tmpfs 7.8G 0 7.8G 0% /dev/shm
tmpfs 7.8G 2.2M 7.8G 1% /run
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/mapper/system-root 1.9T 189G 1.7T 11% /
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/tmp
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/spool
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/opt
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/pgsql
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/named
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/mysql
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/mariadb
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/mailman
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/lib/libvirt/images
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/crash
/dev/mapper/system-root 1.9T 189G 1.7T 11% /usr/local
/dev/mapper/system-root 1.9T 189G 1.7T 11% /tmp
/dev/mapper/system-root 1.9T 189G 1.7T 11% /srv
/dev/mapper/system-root 1.9T 189G 1.7T 11% /opt
/dev/mapper/system-root 1.9T 189G 1.7T 11% /home
/dev/mapper/system-root 1.9T 189G 1.7T 11% /boot/grub2/x86_64-efi
/dev/mapper/system-root 1.9T 189G 1.7T 11% /boot/grub2/i386-pc
/dev/mapper/system-root 1.9T 189G 1.7T 11% /var/log
tmpfs 6.0G 4.5G 1.6G 75% /var/spool/asterisk/monitor

only when I reboot the dialer server, this folder is empty.

How I do to fix it? Not is normal reboot the dialer server to empty the monitor folder.

Crontab -l
### recording mixing/compressing/ftping scripts
0,30 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,30 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
3,33 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3
#1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3
0 19,20,21,22 * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --MP3
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --MP3
#0 1 * * * /usr/share/astguiclient/AST_CRON_audio_4_ftp2.pl --ftp-server=server.ip --ftp-login=user --ftp-pass=pass --ftp-directory=/ --ftp-persistent --ftp-validate --transfer-limit=100000 --list-limit=100000

Regards

Re: Perl Process don't move MIX recording

PostPosted: Tue Mar 06, 2018 3:11 pm
by VoIPEssential
Are your recordings being converted to MP3 and moved/copied to the /var/spool/asterisk/monitorDONE/MP3 directory? Is the issue only that they are not being deleted from /var/spool/asterisk/monitor after they are converted and moved?

Re: Perl Process don't move MIX recording

PostPosted: Tue Mar 06, 2018 3:25 pm
by cromerorey
Yes, the others process to convert to MP3 are OK. Is Only delete files form "monitor" folder and "/var/spool/asterisk/monitor/MIX" too.

Re: Perl Process don't move MIX recording

PostPosted: Tue Mar 06, 2018 3:35 pm
by VoIPEssential
I compared your cron scripts with some dialers we have and it appears that you have changed the first script. I recommend you comment that out and use this one instead:
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
This is the default one used in stock Vicidial installations.

If that doesn't help, I suggest you run the script manually on the CLI with the --debug or --debugX parameters to see where its going wrong.