voiceip / oreka

OpenSource G711, G722, G729, Opus & Other Format VoIP SIP Recorder
GNU General Public License v3.0
149 stars 79 forks source link

Orktrack init connection:false success:false #60

Closed adityapranavbhuvanapalli closed 2 years ago

adityapranavbhuvanapalli commented 2 years ago

I followed the procedure for setting up the docker image. Platform: RHEL 8 The oreka database tables were created, so I presume the .war files setup was correct. In the config.xml file, I made the required changes <Devices>eno2</Devices> When I run the docker container it gives me this error 2021-09-14 05:50:08,012 ERROR orkclient:36 - apr_socket_connect connect failed errno:Connection refused 2021-09-14 05:50:08,012 WARN reporting:320 - [localhost:8080/orktrack] init connection:false success:false

The interface eno2 is not shown in the available pcap devices Instead it is showing eth0

2021-09-14 05:50:07,993 INFO packet:1515 - Available pcap devices: 2021-09-14 05:50:07,993 INFO packet:1522 - * eth0 - 2021-09-14 05:50:07,993 INFO packet:1522 - * any - Pseudo-device that captures on all interfaces 2021-09-14 05:50:08,009 INFO packet:1522 - * lo - 2021-09-14 05:50:08,009 INFO packet:1522 - * nflog - Linux netfilter log (NFLOG) interface 2021-09-14 05:50:08,009 INFO packet:1522 - * nfqueue - Linux netfilter queue (NFQUEUE) interface 2021-09-14 05:50:08,009 INFO packet:1522 - * usbmon1 - USB bus number 1 2021-09-14 05:50:08,009 INFO packet:1522 - * usbmon2 - USB bus number 2 2021-09-14 05:50:08,009 INFO packet:1522 - * usbmon3 - USB bus number 3 if I ran ifconfig, I can see that the interface name is eno2

Is there any particular reason that this occurs? And how do I rectify this?

kingster commented 2 years ago

Hi

The oreka database tables were created, so I presume the .war files setup was correct.

Yes, this means that the tracker app was correctly initialized.

The interface eno2 is not shown in the available pcap devices Instead it is showing eth0

Are you running with --net=host flag while launching the docker instance? If not can you try that? https://www.metricfire.com/blog/understanding-dockers-net-host-option/ says that it should show all the host adapters on the container. If you still don't see them probably you might want to try the macvlan option of docker.

2021-09-14 05:50:08,012 ERROR orkclient:36 - apr_socket_connect connect failed errno:Connection refused 2021-09-14 05:50:08,012 WARN reporting:320 - [localhost:8080/orktrack] init connection:false success:false

This would happen as you might have configured the tracker hostname as localhost in your config.xml and it is not accessible from within the docker instance. When running inside docker it would mean the docker host. Try using the actual IP address of your tomcat host.

adityapranavbhuvanapalli commented 2 years ago

Thanks it worked