-
Linux Headless Server – too many users
Dear $all,
I have set up a Linux Headless Server (on my Synology NAS, in a Docker container), which is – after some minor and major headaches, and some help from the Omnis Team, up and running.
As I am using my Developer license with only one user allowed, I sometimes get ‘too many users connecting too Server’ – I assume because I am starting sessions from different browsers.
However, when I close the tabs or windows of thesde sessions, the message still prevails.
How do I ‘kick out’ unwanted users/sessions from the headless server?
Using http://servername:port/jschtml/osadmin.htm (the headless server’s admin interface) just brings another message ‘too many users…’
Of course, I can restart the headless server, but this seems like using a sledgehammer to crack a nut..
Any ideas? Thanx!
-
3 Replies
-
Which version of Omnis are you using? I thought that the developer license had a 5 user number so you could test multiple connections?
Alternatively you can kill the process from the command line with “killall omnis” – this isn’t a nice way to stop everything, but it does work!
-
Thank you for such a well written composition. It’s full of perceptive information and amusing descriptions. Your point of view is the stylish among numerous.
Prescription glasses online uk Price are lower than many online glasses providers offers. We want to deliver quality online prescription glasses uk without compromising on quality, hence all you need to do request Order My Glasses Online
-
This reply was modified 2 years, 1 month ago by British Johnson.
-
This reply was modified 2 years, 1 month ago by
-
Thanx for your response, Paul!
I am using 10.2, and quite honestly, I don’t know how many concurrent users my developer license allows for – I’ll check.
But even so, there seems no way to log in to the headless server when I’m the n+1’th user, in order to kick out users as admin.
I assume your command kills all processes, as opposed to resetting client connections. Then I’d rather restart the container with ‘docker restart <containerID>
But instead of using a sledge hammer I was looking for a way to check & kick out client connections…
Log in to reply.
