Cluster Dialer ERROR[15280] utils.c: write() returned error

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Cluster Dialer ERROR[15280] utils.c: write() returned error

Postby conrad230 » Fri Mar 20, 2015 5:21 am

Hi All , Please help i have an issue on my vicibox cluster install .

My specs are as per below .

1 DB : ViciBox Redux v.5.0.2-130821 : Mem 24737308 total : Disk 546G : Linux 3.7.10-1.16-default #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) x86_64 x86_64 x86_64 GNU/Linux
: Used Vicibox-install chose DB install expert mode
1 WEB : ViciBox Redux v.5.0.2-130821 : Mem 20600364 total : Disk 300G : Linux 3.7.10-1.16-default #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) x86_64 x86_64 x86_64 GNU/Linux
: Used Vicibox-install chose web install expert mode
1 Dailer/Telephony : ViciBox Redux v.5.0.2-130821 : Mem 24737308 total : 4 CPU Intel(R) Xeon(R) CPU E5310 @ 1.60GHz : Disk 300G : Linux 3.7.10-1.16-default #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) x86_64 x86_64 x86_64 GNU/Linux : Used Vicibox-install chose telephony expert mode

The cluster is working . I am experiencing issues on the Dailer/Telephony (Asterisk 1.8.23.0-vici ), as soon as i have 55 agents logged in and working , i start seeing the following error on the asterisk cli
[Mar 12 09:02:06] ERROR[15280] utils.c: write() returned error: Bad file descriptor

[Mar 12 09:02:06] WARNING[15280] res_agi.c: Connect to 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----CHANUNAVAIL----------' failed: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

[Mar 12 09:02:33] WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor

Followed by allot of continue
[Mar 12 09:02:32] WARNING[15477] app_meetme.c: Failed to read frame: Resource temporarily unavailable
[Mar 12 09:02:33]
WARNING[15477] app_meetme.c: Failed to read frame: Resource temporarily unavailable
[Mar 12 09:02:33]
WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor
[Mar 12 09:02:33]
WARNING[15477] app_meetme.c: Failed to read frame: Bad file descriptor


The dailer then gets a hight load and also cuases agents not to be able to work .


screen -ls

There are screens on:
17492.ASTVDremote (Detached)

6247.ASTupdate (Detached)

1390.ASTfastlog (Detached)

1384.ASTVDauto (Detached)

1381.ASTlisten (Detached)

1378.ASTsend (Detached)

6 Sockets in /var/run/screens/S-root.


Is there a fix i can apply or a setting that i might have missed .

Please kinldy advise .

Thanks
TR
conrad230
 
Posts: 2
Joined: Fri Mar 20, 2015 4:43 am

Re: Cluster Dialer ERROR[15280] utils.c: write() returned e

Postby conrad230 » Thu Apr 02, 2015 8:44 am

Pickup issue that the dailer did not have enough processing power (cpu) .
conrad230
 
Posts: 2
Joined: Fri Mar 20, 2015 4:43 am

bad file descriptor error in vicibox 6.0.3

Postby rosnlama001 » Mon May 30, 2016 1:01 am

I have installed vicibox 6.0.3 in X3250 M5 server. It was working fine about 6 months. But suddenly i see bad file descriptor error on asterisk logs. i have 24 agents who login in the server. when i give dial level more than 4 then bad file descriptor error message coming in the screen and every agent goes to waiting mode. When i reduce the dial level it is working fine. I dont get the issue. My production is getting hamper. Please help .
rosnlama001
 
Posts: 7
Joined: Tue Nov 17, 2015 5:38 am

Re: Cluster Dialer ERROR[15280] utils.c: write() returned e

Postby MJCoate » Tue May 31, 2016 8:18 pm

55 agents is way too many for a single telephony server. You'll need two to support that. Your CPU is also under powered; we recommend at least a 2.4 GHz. It sounds like you might be overloading your hardware.
Mike Coate | VICIdial Technical Support Staff
MJCoate
 
Posts: 82
Joined: Wed Mar 25, 2015 1:57 pm


Return to Support

Who is online

Users browsing this forum: No registered users and 82 guests