May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Starting CGRateS CDRS service.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <CDRC> No enabled CDRC clients
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Starting CGRateS SMFreeSWITCH service
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <HTTP> enabling handler for JSON-RPC
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <HTTP> enabling handler for WebSocket connections
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <HTTP> start listening at <127.0.0.1:2080>
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Starting CGRateS JSON server at <127.0.0.1:2012>.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Starting CGRateS GOB server at <127.0.0.1:2013>.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: could not get load history: [] (<nil>)
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <ServiceManager> Starting CGRateS Scheduler.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <Scheduler> processing 0 action plans
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <Scheduler> queued 0 action plans
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Registering CDRS HTTP Handlers.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: Registering CDRS RPC service.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <Cdrc> Monitoring /tmp/cgr_fsevsock/cgrates/cdrc/in for file moves.
May  9 16:58:23 debian CGRateS <6b9cd381-d993-4f80-b04d-d9f839838dc4> [8984]: <FSock> Successfully connected to FreeSWITCH!