Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
web interface not working in console
#1
I can run Vuze on my server from the gui and xmwebui will come up on http://<server_name>:9091 from other machiens.  When I run from command line:

java -jar Azureus2.jar --ui=console

​It goes thru the logging of output, not errors.  Don't see anyting about xmwebui but when I do

plugin status xmwebui

it says Running is true and run at startup true.

​But connecting to the website local or remote doesn't work.

Thoughts?

Thanks.

JR
Reply
#2
Hmm, 'works for me'...

You're running this from the same directory as the GUI based one? You can check this by replacing your command with

java -classpath Azureus2.jar;swt.jar org.gudy.azureus2.ui.swt.Main
Reply
#3
(11-25-2016, 08:56 PM)'parg' Wrote: Hmm, 'works for me'...

You're running this from the same directory as the GUI based one? You can check this by replacing your command with

java -classpath Azureus2.jar;swt.jar org.gudy.azureus2.ui.swt.Main

 


Correct.  I can say that java is not in my path so call it directly like: jre\bin\java.exe -classpath Azureus2.jar;swt.jar org.gudy.azureus2.ui.swt.Main

​But see nothing in the error to say that's the issue.  This pulls up the GUI like clicking the icon does however does NOT launch the web interface.  Obviously something is having challenges using the ports.  Note this is a fresh restart.  If I click on the desktop icon it's fine.  Below is the output of the command window:



Code:
D:\Program Files\Vuze>jre\bin\java.exe -classpath Azureus2.jar;swt.jar org.gudy.
azureus2.ui.swt.Main
file:/D:/Program%20Files/Vuze/Azureus2.jar ; file:/D:/Program%20Files/Vuze/swt.j
ar ; file:/D:/Program%20Files/Vuze/
changeLocale: *Default Language* != English (United States). Searching without c
ountry..
changeLocale: Searching for language English in *any* country..
changeLocale: no message properties for Locale 'English (United States)' (en_US)
, using 'English (default)'
UIFunctions/ImageLoad took 25ms
new shell took 250ms
new shell setup took 51ms
skin init took 75ms
MainMenu init took 100ms
pre skin widgets init took 50ms
skin widgets (1/2) init took 330ms
skin widgets (2/2) init took 301ms
pre SWTInstance init took 0ms
Init Core Columns took 175ms
SWTInstance init took 26ms
shell.layout took 101ms
---------SHOWN AT 1480171718024;4449ms
---------DONE DISPATCH AT 1480171718534;4959ms
---------READY AT 1480171718559;4984ms
shell.open took 548ms
processStartupDMS took 0ms
postPluginSetup init took 0ms
Locale Initializing took 0ms
com.vuze.plugins.azlocprov.internat.Messages: no default resource bundle
[alert] Alert:3:Keystore is empty. Please create a self-signed certificate (see
Tools->Options->Security) or import an existing certificate into 'C:\Users\syarb
rou\AppData\Roaming\Azureus\.keystore'
[alert] Alert:3:Failed to establish listen on port 9091.
Check that other applications aren't already using this port.
Also check for another copy of Vuze running.
[tracker] TRTrackerServer: SSL listener failed on port 9091
DEBUG::Sat Nov 26 08:48:40 CST 2016::org.gudy.azureus2.core3.tracker.server.impl
.tcp.blocking.TRBlockingServer::<init>::159:
  org.gudy.azureus2.core3.tracker.server.TRTrackerServerException: TRTrackerServ
er: failed to get SSL factory
        at org.gudy.azureus2.core3.tracker.server.impl.tcp.blocking.TRBlockingSe
rver.<init>(TRBlockingServer.java:100)
        at org.gudy.azureus2.core3.tracker.server.impl.TRTrackerServerFactoryImp
l.create(TRTrackerServerFactoryImpl.java:194)
        at org.gudy.azureus2.core3.tracker.server.TRTrackerServerFactory.createS
SL(TRTrackerServerFactory.java:171)Core Initializing took 2391ms

        at org.gudy.azureus2.pluginsimpl.local.tracker.TrackerWebContextImpl.<in
it>(TrackerWebContextImpl.java:70)
        at org.gudy.azureus2.pluginsimpl.local.tracker.TrackerImpl.createWebCont
ext(TrackerImpl.java:240)
        at org.gudy.azureus2.ui.webplugin.WebPlugin.setupServer(WebPlugin.java:1
364)
        at com.aelitis.azureus.plugins.xmwebui.XMWebUIPlugin.access$15(XMWebUIPl
ugin.java:1)
        at com.aelitis.azureus.plugins.xmwebui.XMWebUIPlugin$9.handleEvent(XMWeb
UIPlugin.java:635)
        at org.gudy.azureus2.pluginsimpl.local.PluginInterfaceImpl.firePluginEve
ntSupport(PluginInterfaceImpl.java:866)
        at org.gudy.azureus2.pluginsimpl.local.PluginInitializer$12.runSupport(P
luginInitializer.java:2157)
        at org.gudy.azureus2.core3.util.AsyncDispatcher$1.run(AsyncDispatcher.ja
va:160)
        at org.gudy.azureus2.core3.util.AEThread2$threadWrapper.run(AEThread2.ja
va:294)

[plug] [xmwebui] Server initialisation failed
DEBUG::Sat Nov 26 08:48:41 CST 2016::org.gudy.azureus2.ui.webplugin.WebPlugin::s
etupServer::1765:
  org.gudy.azureus2.plugins.tracker.TrackerException: TRTrackerServerFactory fai
led
        at org.gudy.azureus2.pluginsimpl.local.tracker.TrackerWebContextImpl.<in
it>(TrackerWebContextImpl.java:77)
        at org.gudy.azureus2.pluginsimpl.local.tracker.TrackerImpl.createWebCont
ext(TrackerImpl.java:240)
        at org.gudy.azureus2.ui.webplugin.WebPlugin.setupServer(WebPlugin.java:1
364)
        at com.aelitis.azureus.plugins.xmwebui.XMWebUIPlugin.access$15(XMWebUIPl
ugin.java:1)
        at com.aelitis.azureus.plugins.xmwebui.XMWebUIPlugin$9.handleEvent(XMWeb
UIPlugin.java:635)
        at org.gudy.azureus2.pluginsimpl.local.PluginInterfaceImpl.firePluginEve
ntSupport(PluginInterfaceImpl.java:866)
        at org.gudy.azureus2.pluginsimpl.local.PluginInitializer$12.runSupport(P
luginInitializer.java:2157)
        at org.gudy.azureus2.core3.util.AsyncDispatcher$1.run(AsyncDispatcher.ja
va:160)
        at org.gudy.azureus2.core3.util.AEThread2$threadWrapper.run(AEThread2.ja
va:294)
Caused by: org.gudy.azureus2.core3.tracker.server.TRTrackerServerException: TRTr
ackerServer: failed to get SSL factory
        at org.gudy.azureus2.core3.tracker.server.impl.tcp.blocking.TRBlockingSe
rver.<init>(TRBlockingServer.java:100)
        at org.gudy.azureus2.core3.tracker.server.impl.TRTrackerServerFactoryImp
l.create(TRTrackerServerFactoryImpl.java:194)
        at org.gudy.azureus2.core3.tracker.server.TRTrackerServerFactory.createS
SL(TRTrackerServerFactory.java:171)
        at org.gudy.azureus2.pluginsimpl.local.tracker.TrackerWebContextImpl.<in
it>(TrackerWebContextImpl.java:70)
        ... 8 more

DEBUG::Sat Nov 26 08:48:48 CST 2016::com.aelitis.azureus.core.dht.transport.udp.
impl.DHTTransportUDPImpl::setLocalContact::1299:
  DHTTransport: address changed to /73.208.134.128:19096
    DHTTransportUDPImpl$8::run::1073, AEThread2$threadWrapper::run::294
Reply
#4
[alert] Alert:3:Failed to establish listen on port 9091.
Check that other applications aren't already using this port.
Also check for another copy of Vuze running.

looks as if something else is listening on the web ui port...
Reply
#5
I was thinking not very likely it was in use because the log I sent showed it couldn't map a port which I would consider an odd number.  Plus since I can start it with the link on the desktop and it starts fine with the web interface...  Just a DOS loading issue, elevated or not.  That said I checked.

First did:

wmic PROCESS where "name like '%java%'" get Processid, caption,commandline

Came up with only one java process running that was tied to my raid monitoring software.  So no other Vuze running.  Though even with the desktop icon launch doesn't present itself as a java app, shows separate under Vuze Lancher. Then did a

netstat -na | find "9091"

Nothing found.   

Just ran it again, same errors on in theory port 9091 .  Hmmm.

Interesting without java in the path, the desktop icon calling azureus.exe directly works even plus works like it does compared to the command line.

I have removed UPNP setting checkbox in case I could eliminate mapping to my router.    So right now,

netstat -na | find "9091"

returns nothing.

Run the command.  GUI pops up dos window looks OK this time.  First time I did this it gave me some resource bundle error then continued onto not being able to map 9091.  Right now only listening on 0.0.0.0:9091 and [::]:9091 but did start without the UPNP setting on.  Also forced the protocol to http.

So what next?  I can now in theory get it working though seems flaky but want to keep testing, to get it working from a dos window with the GUI at the moment, haven't tried console mode on localhost, running http.  In essence want ALL computers in my network to be able to access this site and NOT have external access of my network and definitely NOT have that scan the QR Code and open externally thing working.  Thoughts?

Thanks.

JR
Reply
#6
Could it be Windows firewall not allowing 'jre\bin\java.exe' to listen for connections? Or some other AV product?
Reply
#7
(11-26-2016, 03:59 PM)'parg' Wrote: Could it be Windows firewall not allowing 'jre\bin\java.exe' to listen for connections? Or some other AV product?

 



I'll try to figure it out.  Based on the response don't think I'm getting my problem across or writing to much and complicating things.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Vuze Launcher Has Stopped Working [Resolved} KazaaModo 11 9,043 01-26-2017, 03:56 AM
Last Post: bec_farmer
  vuze not working in fedora 25 with wayland luca247 13 535 01-12-2017, 02:43 AM
Last Post: luca247



Users browsing this thread: 1 Guest(s)