Problems connecting to server #109
-
Hi, my name is Alexander, I'm a PhD student at TU Darmstadt/Germany. Am I the only one, having trouble setting up a remote verification server? I want to use my desktop (running linux mint) as remote server. I run (via ssh):
I tried from both, archlinux and windows, to locally run uppaal and connect to the server. E.g. at windows I run:
An error window pops up:
at server side:
after clicking "ok", uppaal opens anyway. But starting a verification is not possible. A window opens, asking for a License installation (??? i never read about sth like this?). This happens also when I start the socketserver as sudo. Is there anywhere a more clear tutorial, regarding the question what i have to do to start a remote server? I don't get whats happening here. Sorry for the inconvenience. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
Hello Alexander. Could you try running the socketserver with the arguments |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for your answer! The result is Caught signal 17, closing proxy. huh, so you're trying to statically link against a shipped libc, right? Is this really a good idea? Something is breaking at this point... I'm unsure what exactly the problem is. |
Beta Was this translation helpful? Give feedback.
-
So what is happening is that socketserver is running with the included linker and However, what the socketserver does is simply running
You might have to install it using apt: |
Beta Was this translation helpful? Give feedback.
So what is happening is that socketserver is running with the included linker and
LD_LIBRARY_PATH
, which we include to make sure that our distribution works on pretty much anything.However, what the socketserver does is simply running
./server
in a loop and serving it over port 2350. But in this case./server
is a shell script, which uses/usr/bin/env
from your system, which isn't compatible with the included linker andLD_LIBRARY_PATH
, resulting in the error. Fixing the socketserver might turn out to be a bit an ordeal, so until that is fixed, you can use socat instead of the socketserver as a workaround:You might have to install it…