ovtr closes itself automatically after start up

[renyuneyun]

I'm using ovtr 1.7.1 under archlinux, from the AUR package.

It used to work, but I haven't been using it for a while. In April, after moving to a new place, I would like to test the network, so I started ovtr again. However, since then, ovtr never actually worked.

The problem is: after running ovtr, the application window displays for a very short while, and then ovtr is closed automatically. This is the same whether I run it with my user (in group network and can run tracepath) or root.
I looked at the console output, but nothing appears to be useful. (See attachments.)

ovtr_root_proxyed.log
ovtr_root_noproxy.log
ovtr_user_noproxy.log
ovtr_user_proxyed.log

My network has some issue in connecting to certain websites. That's the reason I used proxy to download the latest databases, and also the reason for:

Failed to download dynamic config. Fallback to default
java.net.ConnectException: 拒绝连接 (Connection refused)

Is there any more directives on how I may examine further?

[BIZ4Africa]

Hi,
Having exact same behaviour with 1.7.1 on Ubuntu.

[zell-mbc]

Same here on Arch

sudo ovtr              
08:26:35.809 [main] INFO  org.leo.traceroute.Main - Open Visual Traceroute 1.7.1 
08:26:35.886 [main] INFO  org.leo.traceroute.install.Env - Java run-time version: 1.8.0_292
08:26:35.887 [main] INFO  org.leo.traceroute.install.Env - NASA World Wind Java v2.1.0
08:26:35.887 [main] INFO  org.leo.traceroute.install.Env - /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
08:26:35.913 [main] INFO  org.leo.traceroute.install.Env - OS:Linux / arch:amd64
Locale en_GB
08:26:37.280 [SwingWorker-pool-1-thread-1] INFO  o.leo.traceroute.core.geo.GeoService - Use geoip db /root/ovtr/GeoLite2-City.mmdb which is 0 day(s) old
08:26:38.065 [SwingWorker-pool-1-thread-1] INFO  o.leo.traceroute.core.geo.GeoService - DNS LOC records file /root/ovtr/dns.loc loaded
08:26:38.750 [pool-2-thread-1] INFO  o.leo.traceroute.core.ServiceFactory - Try using device enp0s31f6 null
08:26:38.751 [pool-2-thread-2] INFO  o.leo.traceroute.core.ServiceFactory - Try using device wlp2s0 null
08:26:38.751 [pool-2-thread-3] INFO  o.leo.traceroute.core.ServiceFactory - Try using device docker0 null
08:26:39.757 [pool-2-thread-2] INFO  o.leo.traceroute.core.ServiceFactory - Try using device veth1ca2226 null
08:26:40.751 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out enp0s31f6
08:26:42.753 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out docker0
08:26:44.754 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out veth1ca2226
08:26:46.755 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out any
08:26:48.756 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out lo
08:26:50.758 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out br-90f5da75a979
08:26:52.758 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out br-fbd3e9587c29
08:26:54.760 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out bluetooth0
08:26:56.760 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out bluetooth-monitor
08:26:58.761 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out nflog
08:27:00.763 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out nfqueue
08:27:02.764 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out dbus-system
08:27:04.765 [SwingWorker-pool-1-thread-1] WARN  o.leo.traceroute.core.ServiceFactory - Device timed out dbus-session
08:27:05.365 [AWT-EventQueue-0] INFO  org.leo.traceroute.Main - Startup completed in 29563ms
08:27:06.408 [Shutdown] INFO  o.leo.traceroute.core.geo.GeoService - DNS LOC records saved to /root/ovtr/dns.loc
08:27:06.410 [Shutdown] INFO  org.leo.traceroute.install.Env - Preferences saved.
08:27:06.412 [Shutdown] INFO  o.leo.traceroute.ui.TraceRouteFrame - Application exited.

[leolewis]

Can you try the version 2.0.0 and see if the issue persists?

[zell-mbc]

Thanks for looking into this. But I don't know how to launch v2 I am afraid.

The AUR version I used previously is still on 1.7.1, so I went and cloned the repo. Found the bin/run.sh script but that's complaining about a missing org.leo.traceroute.jar, which indeed isn't part of the package.
Do I need to compile that jar file first? If so how?

[leolewis]

You should be able to download the universal package from https://sourceforge.net/projects/openvisualtrace/files/2.0.0/OpenVisualTraceRoute2.0.0.zip/download, unzip it and run the script run.sh (sudo is not required).