SEMS not writing CDR on v1.8 [error log]

Yeti-Switch
1

SEMS NODE

ay 3 10:16:44 sbc-eu-1 sems[18272]: [18293/yeti:db/PgConnectionPool.cpp:310] WARNING: PCP: : All sql connected.
May 3 10:22:31 sbc-eu-1 sems[18272]: [18294/yeti:cdr/CdrWriter.cpp:578] ERROR: Cant write record to master database
May 3 10:22:37 sbc-eu-1 sems[18272]: [18294/yeti:cdr/CdrWriter.cpp:658] INFO: CdrWriter: SQL connected. Backend pid: 23898.
May 3 10:22:37 sbc-eu-1 sems[18272]: [18294/yeti:cdr/CdrWriter.cpp:511] INFO: CdrWriter 0x55dbf0faee10 master DB connection failed alarm cleared
May 3 10:22:37 sbc-eu-1 sems[18272]: [18294/yeti:alarms.cpp:65] INFO: ALARM 2 [cdr database connections error] CLEARED
May 3 10:22:39 sbc-eu-1 sems[18272]: [18294/yeti:cdr/CdrWriter.cpp:578] ERROR: Cant write record to master database

DB-NODE

019-05-03 07:58:09.193 UTC [13700] STATEMENT: SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42);
2019-05-03 07:58:09.703 UTC [13702] ERROR: value “2886157756.000000” is out of range for type integer
2019-05-03 07:58:09.703 UTC [13702] CONTEXT: PL/pgSQL function writecdr(boolean,integer,integer,integer,boolean,smallint,character varying,integer,character varying,integer,smallint,character varying,integer,character varying,integer,json,boolean,integer,character varying,integer,integer,character varying,integer,character varying,character varying,character varying,character varying,character varying,character varying,integer,boolean,json,json,character varying,character varying,json,smallint,bigint,json,json,boolean,json) line 157 at assignment

2

could you show more DB logs?

3

@dmitry.s

Its basically the same error repeating over and over again. (is out of range for type integer)

More DB logs provided below.

2019-05-03 07:58:09.193 UTC [13700] STATEMENT: SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42);
2019-05-03 07:58:09.703 UTC [13702] ERROR: value “2886157756.000000” is out of range for type integer
2019-05-03 07:58:09.703 UTC [13702] CONTEXT: PL/pgSQL function writecdr(boolean,integer,integer,integer,boolean,smallint,character varying,integer,character varying,integer,smallint,character varying,integer,character varying,integer,json,boolean,integer,character varying,integer,integer,character varying,integer,character varying,character varying,character varying,character varying,character varying,character varying,integer,boolean,json,json,character varying,character varying,json,smallint,bigint,json,json,boolean,json) line 157 at assignment
2019-05-03 07:58:09.703 UTC [13702] STATEMENT: SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42);
2019-05-03 07:58:14.337 UTC [13703] ERROR: value “3170001392.000000” is out of range for type integer
2019-05-03 07:58:14.337 UTC [13703] CONTEXT: PL/pgSQL function writecdr(boolean,integer,integer,integer,boolean,smallint,character varying,integer,character varying,integer,smallint,character varying,integer,character varying,integer,json,boolean,integer,character varying,integer,integer,character varying,integer,character varying,character varying,character varying,character varying,character varying,character varying,integer,boolean,json,json,character varying,character varying,json,smallint,bigint,json,json,boolean,json) line 157 at assignment
2019-05-03 07:58:14.337 UTC [13703] STATEMENT: SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42);
2019-05-03 07:58:14.849 UTC [13704] ERROR: value “2886157756.000000” is out of range for type integer
2019-05-03 07:58:14.849 UTC [13704] CONTEXT: PL/pgSQL function writecdr(boolean,integer,integer,integer,boolean,smallint,character varying,integer,character varying,integer,smallint,character varying,integer,character varying,integer,json,boolean,integer,character varying,integer,integer,character varying,integer,character varying,character varying,character varying,character varying,character varying,character varying,integer,boolean,json,json,character varying,character varying,json,smallint,bigint,json,json,boolean,json) line 157 at assignment
2019-05-03 07:58:14.849 UTC [13704] STATEMENT: SELECT writecdr($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25,$26,$27,$28,$29,$30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$40,$41,$42);
2019-05-03 07:58:16.773 UTC [13705] LOG: unexpected EOF on client connection with an open transaction

4

Could you capture TCP traffic between SEMS and CDR database(ssl should be disabled in postgresql.conf) using tcpdump and send file to me?

5

@zerocool try to upgrade sems-modules-yeti to version 1.8.0-2

6

Okay thanks. will do so. Had changes “load_safe” to just “load” as a temporary hack in pgq_processors.yml . Could not figure out how to add type [symbol]. Am new to ruby. Hoewever its fixed as per your patch #474

7

sems -v comand showing

SBC 1.8.18-2

is that one okay??

8

Okay thanks. will do so. Had changes “load_safe” to just “load” as a temporary hack in pgq_processors.yml . Could not figure out how to add type [symbol]. Am new to ruby. Hoewever its fixed as per your patch #474

this fix was included to yeti-web version 1.8.2