[Spce-user] Redis connection problem

[Thomas Schlien]

Hi,

we use Sipwise CE mr10.1.1 and around every two weeks we get this kind 
of repetitive errors in /var/log/ngcp/kamailio-proxy.log:

Jan 21 08:43:53.398727 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=«sip:sip.example.de» 
F=«sip:client at sip.example.de» T=«sip:client at sip.example.de» 
IP=«1.2.3.4»:«48941» («127.0.0.1»:«5060») 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=«127.0.0.1»:«5062»
Jan 21 08:43:53.398806 sip2 proxy[1837067]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='«127.0.0.1»:«5062»' 
du='«127.0.0.1»:«5060»' - R=«sip:sip.example.de» 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.398876 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Authentication failed, no credentials - R=«sip:sip.example.de» 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
Auth=«<null>»
Jan 21 08:43:53.399508 sip2 proxy[1837067]: NOTICE: ROUTE_AUTH <script>: 
Sending reply S=401 fs='«127.0.0.1»:«5062»' du='«127.0.0.1»:«5060»' - 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.423845 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: New request on proxy - M=REGISTER R=«sip:sip.example.de» 
F=«sip:client at sip.example.de» T=«sip:client at sip.example.de» 
IP=«1.2.3.4»:«48941» («127.0.0.1»:«5060») 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)' 
DESTIP=«127.0.0.1»:«5062»
Jan 21 08:43:53.423922 sip2 proxy[1837070]: NOTICE: DEFAULT_ROUTE 
<script>: Sending reply S=100 Trying M=REGISTER fs='«127.0.0.1»:«5062»' 
du='«127.0.0.1»:«5060»' - R=«sip:sip.example.de» 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431007 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:127]: db_redis_connect(): cannot open 
connection to redis://localhost:6379/20: System error
Jan 21 08:43:53.431078 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_connection.c:381]: db_redis_get_reply(): Failed to 
reconnect to redis db
Jan 21 08:43:53.431123 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2043]: db_redis_perform_update(): Failed to get 
reply for query: <broken redis connection>
Jan 21 08:43:53.431166 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2298]: db_redis_perform_update(): failed to 
perform the update
Jan 21 08:43:53.431208 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
db_redis [redis_dbase.c:2850]: db_redis_update(): failed to do the query
Jan 21 08:43:53.431258 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1147]: db_update_ucontact_ruid(): updating database 
failed
Jan 21 08:43:53.431301 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
usrloc [ucontact.c:1663]: update_contact_db(): failed to update database
Jan 21 08:43:53.431343 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
registrar [save.c:796]: update_contacts(): failed to update contact
Jan 21 08:43:53.431386 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE 
<script>: Contacts failed - R=«sip:sip.example.de» 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431430 sip2 proxy[1837070]: NOTICE: ROUTE_REG_HANDLE 
<script>: Sending reply S=500 Server Error fs='«127.0.0.1»:«5062»' 
du='«127.0.0.1»:«5060»' - R=«sip:sip.example.de» 
ID=«tpB4lmA~R6v9ho]k+3. at 1.2.3.4» UA='2wcom 4audio IP-4c 2.06.9 (1.07)'
Jan 21 08:43:53.431473 sip2 proxy[1837070]: ERROR: ROUTE_REG_HANDLE sl 
[sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm 
terribly sorry, server error occurred (1/SL)

When the first message of this arrives, registering and calling is no 
longer possible. I already looked at the redis log (after enabling it), 
but there is no useful information. In addition I connected via 
"redis-cli -p 6379 -n 20" via SSH Console and the command "KEYS *" works 
without problem in the situation.

The only way to get the server back to work was to reboot the system or 
do a "systemctl restart redis-server".

Do you have any hint how I can find out what is going wrong?

Best regards,
Thomas

-- 
Dr.-Ing. Thomas Schlien
Ferncast GmbH
Gallierstr. 41a, 52074 Aachen
Germany

Phone: +49 241 99034567
Web:   www.ferncast.de
--
CEO: Detlef Wiese
Court of Registration: Amtsgericht Aachen
Commercial Register: HRB 22350