Remote Access Problem - Port 8090 in use by another program

[championc]

Hi there

I have the system installed on a Linux Mint "Server". I remotely connected into the system from my Android phone - perfectly. When I was finished, I clicked on Exit.

However, when I now try and access the server from my PC remotely, I get "Port:10.10.5.4:8090 in use by another program"

I then tried to get back in on my phone, and I got the same message.

Why is this happening, and how can I force the session to close ?

[skylord123]

I get the same issue from time to time. It usually happens after trying to modify a video camera or pull up an archive. The spinning loading wheel then comes up and just keeps spinning. After restarting the client I get the same "Port in use by another program" message.

I usually have to force restart Xeoma to fix it. I hope this is fixed soon. I'm running it on a headless Ubuntu 16.04 server.

[championc]

Thanks for that

How can I restart Xeoma from the command line ? I have Terminal Services access to the server but it won't allow the server to run like this. I think the screen resolution is not good enough to allow VNC to run either, so I'm stuck with Command Line

[championc]

I ended up rebooting the server and all resolved

[Admin_N]

Thanks for posting the results. Please let us know if the issue persists in the future!

[skylord123]

I'm running it on Ubuntu and finally found that this restarts it:

Code: Select All Code

restart XeomaCoreService

these commands also work:

Code: Select All Code

status XeomaCoreService

Code: Select All Code

start XeomaCoreService

Code: Select All Code

stop XeomaCoreService

[jonbanjo]

With Linux, starting/stopping, etc. depends on the “init” system running. An old way was:

Code: Select All Code

/etc/init.d/<service> <operation>

But things have moved on and different distributions use different methods (and I think Ubuntu which was using upstart now uses systemd as the default..). If stuck, a few to try:

Code: Select All Code

systemctl <operation> <service>

service <service> <operation>

<operation> <service>


For xeoma, <service> should be XeomaCoreService

I think in all of the above cases, <operation> can be start/stop/restart/status. systemctl additionally supports enable and disable to control whether the service starts on boot.

Distributions may also provide their own methods for administration, eg. on OpenSuse, I could ssh to a remote machine and run the ncurses text version of Yast.

Back to the topic. I have noticed that even a wrong password can case this error on the current version of xeoma.

[Admin_P]

Hello! Occasionally, Xeoma does display the wrong error message while attempting to connect to the server. However, we've yet to systematize this behavior, which complicates the task of solving the underlying issue.
If you have any particulars or managed to replicate this systematically, please share with us - it will be a tremendous help for our Testing Department.