Problems running v3.1 first time

[sai-mike]

I have been running phpVirtualBox for several years and I am looking at moving to RemoteBox. My headless Debian Stretch server is running VirtualBox web service 6.1.10 r138449.

When I connect using RemoteBox from a Debian Stretch desktop, I just get a spinning cursor. No guest list or other server information. I have to force quit RemoteBox to close it. Nothing of value is logged in the terminal window used to start RemoteBox (just several Gtk error messages prior to connection). Here is what is logged in the server's vboxweb.log every few seconds until I kill RemoteBox:

01:46:51.926210 SQW01 Access for user 'vboxuser' granted
01:46:53.490670 SQPmp Request 424 on socket 10 queued for processing (1 items on Q)
01:46:53.490730 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)
01:46:55.410311 SQPmp Request 425 on socket 10 queued for processing (1 items on Q)
01:46:55.410374 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)
01:46:57.310364 SQPmp Request 426 on socket 10 queued for processing (1 items on Q)
01:46:57.310420 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)
01:46:59.150658 SQPmp Request 427 on socket 10 queued for processing (1 items on Q)
01:46:59.150712 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)
01:47:01.030656 SQPmp Request 428 on socket 10 queued for processing (1 items on Q)
01:47:01.030710 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)
01:47:02.850089 SQPmp Request 429 on socket 10 queued for processing (1 items on Q)
01:47:02.850141 SQW01 Processing connection from IP=192.168.73.98 socket=10 (0 out of 1 threads idle)

I followed the web site instructions for installing the Debian dependencies. What am I missing?

[Ian Chapman]

What does the message log in RemoteBox say?

What user are you running the web service as?

What user are logging in with?

[sai-mike]

I have a notebook running Debian 10 so I tried to install RemoteBox on that this morning. I went to the message log tab and saved the log to get a time stamp and then immediately attempted to connect. In the attached screenshot, you can see it took over a minutes to connect. I gave it about 7 more minutes and it never got past retrieving the guest list and then I killed it. I am running over a high latency connection (ViaSat) and a VPN. I do use the same connection frequently for remote SSH & RDP connections to the VBox Headless Server without any major issues.

[Ian Chapman]

Do you have a lot of guests?

Although I'd expect it to be quicker than 7 minutes (depends on how many guests you have really), RemoteBox will not perform well over high latency connections and particularly if there's any kind of packet loss.

[sai-mike]

I have 4 Groups of VirtualBox VMs on the Server:
Group 1 - 9 VMs - 1 Active
Group 2 - 12 VMs - 12 Active
Group 3 - 3 VMs - 0 Active
Group 4 - 3 VMs - 3 Active

Does this look excessive? If so, I could run RemoteBox on a Debian
Virtual Machine on the headless server - if that will not cause
additional problems?

--

On 2022-05-06 10:11 pm, Ian Chapman wrote:

Do you have a lot of guests?

Although I'd expect it to be quicker than 7 minutes, RemoteBox will not
perform well over high latency connections

---

Problems running v3.1 first time [1]

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/remotebox/discussion/RemoteBox/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

Links:

[1]
https://sourceforge.net/p/remotebox/discussion/RemoteBox/thread/53f857d634/?limit=25#4802

[Ian Chapman]

I wouldn't say it's excessive in itself, I have around 50 guests but then between my desktop and my server it's a 10Gbit link, so latency isn't an issue. It boils down to, the more guests you have, the more API calls RemoteBox has to make to grab the list of guests. Those calls occur synchronously and in serial so on a high latency link or a link with some packet loss, performance just sucks.

There's 100% no problem running RemoteBox within a VM, even under the VirtualBox instance you're connecting to and it sounds like in your case, performance may be much better by putting RemoteBox on a guest and connecting to that guest over RDP and launching it.

[sai-mike]

I setup a Debian Bullseye VM with Xfce on the VirtualBox server and it is working fine running RemoteBox. I am connecting to the RemoteBox VM using VNC.

[Ian Chapman]

That's good to hear, a work around at least