Error #2 in asterisk logs after upgrade to 9.1.2-37

This post is at: Forum → Thirdlane platform General Questions

8 posts / 0 new

Last post

2019/02/04 - 4:08pm

mcampbell@1poin...

Joined: 2015/05/20

Points: 0

Another new error we've never seen popped up today:

WARNING[15392][Unique Call ID] res_memcached.c: mcd_read: memcached pool error: 31

2019/02/10 - 7:13pm

thirdlane

Joined: 2007/02/07

Points: 380

Was this just once or it happens frequently?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

2019/02/12 - 1:08pm

(Reply to #2) #3

mcampbell@1poin...

Joined: 2015/05/20

Points: 0

I see it in the logs 14 times yesterday...

2019/02/15 - 1:48pm

(Reply to #3) #4

mcampbell@1poin...

Joined: 2015/05/20

Points: 0

Every day this error comes up multiple times & I can't correlate it to any specific event in the logs. Again, we never saw this error -ever- until post-upgrade...

2019/03/01 - 12:48pm

(Reply to #4) #5

mcampbell@1poin...

Joined: 2015/05/20

Points: 0

Again - this and other related errors *never* surfaced until the latest upgrade to Thirdlane Unified Communications Platform 9.1.2.37

Anyone else seeing it in their logs? Any resolution other than hoping it's not an issue?

Thanks in advance...

2019/03/12 - 12:14am

matthewmalk248

Joined: 2015/08/09

Points: 30

I get it just a couple times a day, haven't paid much attention to it.

2019/03/13 - 8:21am

eugene.voityuk

Joined: 2014/01/28

Points: 90

We are looking into this. I will follow-up results here.

2019/03/19 - 5:52pm

volodya

Joined: 2017/01/05

Points: 140

Hello everyone!

We just prepared new Asterisk package version 13.25.0-4 to fix this problem. Please run following commands to update and start using it:

yum clean all
yum update asterisk13
service asterisk restart

Make sure to do this outside of business hours as this will drop active calls.

Please let us know in case of any issues.