I face some problem when start sems

1

image
image1801×506 250 KB

image
image1894×604 399 KB

As you see, the have two problem when start sems. Pls give me some advice.

  1. management database connections error
  2. ERROR: get connection can’t get connection from write redis pool. retry every 1s
2

cat sems.conf:

general {
stderr = no
syslog_loglevel = 2
syslog_facility = LOCAL0

node_id = 8

shutdown_mode {
    code = 508
    reason = "Yeti node in shutdown mode"
    allow_uac = true
}

media_processor_threads = 4
rtp_receiver_threads = 4
session_processor_threads = 20
sip_udp_server_threads = 2
sip_tcp_server_threads = 2

dead_rtp_time=30

default_bl_ttl=0

symmetric_rtp_mode = packets
symmetric_rtp_packets = 20

}

signaling-interfaces {
interface internal {
default-media-interface = internal
ip4 {
sip-udp {
address = 192.168.0.38
port = 5060
use-raw-sockets = off
}
sip-tcp {
address = 192.168.0.38
port = 5060
connect-timeout = 3000
static-client-port = on
idle-timeout=900000
use-raw-sockets = off
}
}
}
}

media-interfaces {
interface internal {
ip4 {
rtp {
address = 192.168.0.38
low-port = 16384
high-port = 32769
dscp = 46
use-raw-sockets = off
}
}
}
}

modules {
module “di_log” {}
module “mp3” {}
module “opus” {}
module “wav” {}
module “gsm” {}
module “ilbc” {}
module “adpcm” {}
module “l16” {}
module “g722” {}
module “g729bcg” {}

module "registrar_client" {}
module "sctp_bus" {}
module "session_timer" {}
module "jsonrpc" {
    listen{
        address = 127.0.0.1
        port = 7080
    }
    server_threads = 1
}

module "http_client" {}

module-global "uac_auth" {}
module "options_prober" {}

module "radius_client" {}

module "yeti" {
    pop_id = 4
    lega_cdr_headers {
        header(p-charge-info, string)
        header(diversion, array)
    }

    auth {
        realm = yeti-switch
    }

    msg_logger_dir = /var/spool/sems/dump
    audio_recorder_dir = /var/spool/sems/records
    audio_recorder_compress = true

    db_refresh_interval = 5
    ip_auth_reject_if_no_matched = true

    routing {
        schema = switch20
        function = route_release
        init = init
        master_pool {
            host = 127.0.0.1
            port = 5432
            name = yeti
            user = yeti
            pass = somepassword
            size = 4
            check_interval = 10
            max_exceptions = 0
            statement_timeout=3000
        }
        failover_to_slave = false
        slave_pool {
            host = 127.0.0.1
            port = 5432
            name = yeti
            user = yeti
            pass = somepassword
            size = 4
            check_interval = 10
            max_exceptions = 0
            statement_timeout=3000
        }
    }
    cdr {
        dir = /var/spool/sems/cdrs
        completed_dir = /var/spool/sems/cdrs/completed
        pool_size = 4
        schema = switch
        function = writecdr
        master {
            host = 192.168.0.118
            port = 5432
            name = cdr
            user = cdr
            pass = somepassword
        }
        failover_to_slave = false
        slave {
            host = 192.168.0.118
            port = 5432
            name = cdr
            user = cdr
            pass = somepassword
        }
        failover_requeue = true
        failover_to_file = false
        serialize_dynamic_fields = true
        batch_size = 1
        batch_timeout = 5000
    }
    resources {
        reject_on_error = false
        write {
            host = 127.0.0.1
            port = 6379
            size = 200
            timeout = 3000
        }
        read {
            host = 127.0.0.1
            port = 6379
            size = 200
            timeout = 3000
        }
    }
    registrations {
        check_interval = 5000
    }
    registrar {
        enabled = true
        expires_min = 600
        expires_max = 7200
        expires_default = 1200
        redis {
            host = 127.0.0.1
            port = 6379
        }
    }
    rpc {
        calls_show_limit = 10000
    }
    core_options_handling = yes
}

}

routing {
application = yeti
}

3

Please don’t create a new thread for the same issue.

As you can see in your sems status thatmanagement database connections error says CLEARED so that is not an error, It is just an INFO.

Also you can Ignore the Redis Error. it will not effect anything. THE SEMS is working fine.

4

Oh, Thank you very much.