Menu

(no subject)

2020-10-11
2020-10-20
  • Harold Roberts

    Harold Roberts - 2020-10-11

    I am running 20.04.1 with a kernel version of 5.4.0-48-generic

    I am running Remotebox on Windows 10 using strawberry perl.

    I am getting this error message when I try to connect to the server:

    (rboximage1.png attachment)

    My /etc/default/virtualbox config is this:

    (rboximage2.png attachment)

    And when I run the systemctl status virtualbox-service command I see this:

    (rboximage3.png attachment)

    I am not running any firewalls that I am aware of on this bare install.

    Can anyone provide me where I can go to look at next.

    Thank you very much.

    Harold

     

    Last edit: Harold Roberts 2020-10-11
  • Ian Chapman

    Ian Chapman - 2020-10-13

    It tentatively looks fine, but on the windows box can you install telnet (if not already installed). It's part of the Windows Features options.

    With telnet, do the following:

    telnet 192.1682.187 18083

    This should verify network connectivity at least. On the linux box I'd check that the weboxwebsrv process is actually running with ps -aef also

     
  • Ian Chapman

    Ian Chapman - 2020-10-13

    I also meant to add, that I'm pretty sure when you do systemctl status is should be report as active running, NOT active exited. This tells me your vboxweb service is quitting.

    Look at your /var/log/vboxwebservice.log file to see any error.

    If it's empty or doesn't exist then your web service doesn't have permissions to write to it. This will also cause it to fail.

     
  • Harold Roberts

    Harold Roberts - 2020-10-14

    Yes that is my concern as well is the fact it says active exited. The /var/log/vboxwebservice.log file is 0 bytes. I even chmod to 777 just to see if that changed anything. I made root owner. I made myself owner. I made my user virtual owner. and it never gets any data in the file. I am not sure where to even start at this point. I can't figure out why vboxwebservice will not stay running.

    Tonight I went so far as to purge the install, and reinstalled (BTW, both installs were done with 6.1.14) this is the only one I could get the kernel modules to load into with the 5.4.0-48 kernel.

     
  • Ian Chapman

    Ian Chapman - 2020-10-15

    I'd suggest running it manually on the server as the user you intend to run it as like this:

    vboxwebsrv -t -H 192.168.2.187

    It should output any errors. If it doesn't connect to it.

    Are you using VirtualBox directly from VirtualBox or your disto's packages?

     
  • Harold Roberts

    Harold Roberts - 2020-10-20

    OK so running this above command as myself. works. and I am able to atleast try to authenticate. it tells me i have the wrong password, but i can su as that user and password.

    But when I do su as that user, and try to run it, I get an error message that says failed to initialize com! hrc=NS_ERROR_FAILURE

     
  • Harold Roberts

    Harold Roberts - 2020-10-20

    OK a little more information. I needed to create the home folder using the "sudo mkhomedir_helper virtual" command, and then "sudo usermod -s /bin/bash" command. Now if I log in as that user the command above runs and stays running and I am able to connect via remote box.

    But stopping and restarting the service does not stay running. also even though virtual is the owner of the vboxwebservice.log file it is still empty.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.