[Spce-user] no cdrs after upgrade - mediator is running

[qabane me]

Hi Rene

Ok I have poked and prodded but am not clear on what to look for. The user
and password for exporter are correct and can access the DB.

 /usr/sbin/cdr-exporter gives:

+++ Start run with DB exporter at accounting to sipwise
### 0 data lines written to
/tmp/TkhNDI49z4/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr.9781,
checksum is 9b8bd11538a55b017aab6b2ce9d7374f
### successfully moved
/tmp/TkhNDI49z4/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr.9781
to
/tmp/TkhNDI49z4/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr
### moving
/tmp/TkhNDI49z4/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr
to
/home/jail/home/cdrexport/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr

### successfully moved
/tmp/TkhNDI49z4/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr
to final destination
/home/jail/home/cdrexport/resellers/default/201907/03/sipwise_007_20190703100802_0000016150.cdr

### 0 data lines written to
/tmp/TkhNDI49z4/resellers/XXX/201907/03/sipwise_007_20190703100802_0000015797.cdr.9781,
checksum is 9b8bd11538a55b017aab6b2ce9d7374f
### successfully moved
/tmp/TkhNDI49z4/resellers/XXX/201907/03/sipwise_007_20190703100802_0000015797.cdr.9781
to /tmp/TkhNDI49z4/resellers/Pink
IP/201907/03/sipwise_007_20190703100802_0000015797.cdr
### moving /tmp/TkhNDI49z4/resellers/Pink
IP/201907/03/sipwise_007_20190703100802_0000015797.cdr to
/home/jail/home/cdrexport/resellers/Pink
IP/201907/03/sipwise_007_20190703100802_0000015797.cdr

### successfully moved
/tmp/TkhNDI49z4/resellers/XXX/201907/03/sipwise_007_20190703100802_0000015797.cdr
to final destination /home/jail/home/cdrexport/resellers/Pink
IP/201907/03/sipwise_007_20190703100802_0000015797.cdr

I am clearly not looking in the right place but my GPS is not showing me
where to go :-(



On Tue, Jul 2, 2019 at 12:49 PM Rene Krenn <rkrenn at sipwise.com> wrote:

> cdr-exporter is not mediator, it is a separate program, launched via cron.
>
> It also has a dedicated logfile.
>
> br
>
>
>
> *Von:* qabane me [mailto:qabaneitsolutions at gmail.com]
> *Gesendet:* Dienstag, 2. Juli 2019 12:33
> *An:* Rene Krenn <rkrenn at sipwise.com>
> *Cc:* Spce-user <spce-user at lists.sipwise.com>
> *Betreff:* Re: [Spce-user] no cdrs after upgrade - mediator is running
>
>
>
> Ok, found this:
>
>
>
> DBHOST=localhost
> DBUSER=exporter
> DBPASS=XXXXXXXXXXXXX
> DBDB=accounting
>
>
>
> in /etc/ngcp-cdr-exporter/cdr-exporter.conf
>
>
>
> Restarting Mediator gives me this:
>
>
>
> Jul  2 12:29:07 sipwise (debug) mediator[16939]: Writing pid file.
> Jul  2 12:29:07 sipwise (info) mediator[16939]: ACC acc database
> host='localhost', port='3306', user='kamailio', name='kamailio'
> Jul  2 12:29:07 sipwise (info) mediator[16939]: CDR acc database
> host='localhost', port='3306', user='mediator', name='accounting'
> Jul  2 12:29:07 sipwise (info) mediator[16939]: PROV database
> host='localhost', port='3306', user='mediator', name='provisioning'
> Jul  2 12:29:07 sipwise (info) mediator[16939]: STATS database
> host='localhost', port='3306', user='mediator', name='stats'
> Jul  2 12:29:07 sipwise (debug) mediator[16939]: Setting up mysql
> connections.
> Jul  2 12:29:07 sipwise (info) mediator[16939]: Up and running,
> daemonized=1, pid-path='/var/run/mediator.pid', interval=10
>
>
>
> No mention of a DBUSER exporter though. Am I barking up the right tree?
>
>
>
>
>
>
>
> On Tue, Jul 2, 2019 at 12:17 PM qabane me <qabaneitsolutions at gmail.com>
> wrote:
>
> Hi
>
>
>
> Thanks for the quick response. Indeed they show unexported.
>
>
>
> You can investigate by executing it from commandline. > I am not sure
> what you mean by that and/or what to fix :-(?
>
>
>
> On Tue, Jul 2, 2019 at 12:13 PM Rene Krenn <rkrenn at sipwise.com> wrote:
>
> If you check accounting.cdr databse tables, what export_status do the
> records there show?
>
> If „unexported“, cdr-exporter is not running properly; eg. it’s dbuser is
> rejected. You can investigate by executing it from commandline.
>
>
>
> br
>
>
>
> *Von:* Spce-user [mailto:spce-user-bounces at lists.sipwise.com] *Im Auftrag
> von *qabane me
> *Gesendet:* Dienstag, 2. Juli 2019 12:08
> *An:* Spce-user <spce-user at lists.sipwise.com>
> *Betreff:* [Spce-user] no cdrs after upgrade - mediator is running
>
>
>
> Hi there
>
>
>
> We upgraded our sipwise to 4.5.12. I have just picked up that the cdrs
> appear to not be generated. Mediator is running, the CDR log shows:
>
>
>
> Jul  2 12:04:15 sipwise (debug) mediator[4291]: Overall 2131068 CDRs
> created so far.
> Jul  2 12:04:18 sipwise (debug) mediator[4291]: Overall 2131071 CDRs
> created so far.
> Jul  2 12:04:21 sipwise (debug) mediator[4291]: Overall 2131073 CDRs
> created so far.
> Jul  2 12:04:24 sipwise (debug) mediator[4291]: Overall 2131079 CDRs
> created so far.
> Jul  2 12:04:27 sipwise (debug) mediator[4291]: Overall 2131083 CDRs
> created so far.
>
>
>
> So all appears to be working. It does create the various files in the
> /home/jail/home/resellers/default directory, but they are blank. There are
> no files though at all in the /system directory since the upgrade.
>
>
>
> Any ideas what could be missing?
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190703/9434d367/attachment-0001.html>