Windows 7, VB 5.1 & start service problems

Forum for general topics about how to use Hyperbox
Graziano
Posts: 2
Joined: 17 Jul 2016 11:16

Windows 7, VB 5.1 & start service problems

Postby Graziano » 17 Jul 2016 11:23

Hi!
In my system with i7, 32GB, SSD, Win 7 Pro x64 (fully patched), VB 5.1, JRE 8u91 i386 & x64 is all right if I lauch HB server in a command line shell.
If I install HB as a service the service is installed but don't run.
Into che folder C:\Program Files\Hyperbox\Server\log i find hboxd.log that contain:

Code: Select all

+==============================================================+
 Log start on 17/07/2016 @ 11:09:51           +
+==============================================================+
Hyperbox 0.0.13 - Java 1.8.0_91 Java HotSpot(TM) 64-Bit Server VM 25.91-b15 - Windows 7 6.1 amd64
2016.07.17-11:09:51.718 |      Info | Hyperbox Init Sequence started
2016.07.17-11:09:52.344 |      Info | Server ID: 975bfbe0-f0c3-49bc-a2ea-e1c05aa82ab6
2016.07.17-11:09:52.344 |      Info | Server Name: io
2016.07.17-11:09:52.875 |     Error | Hyperbox Init Sequence failed!
2016.07.17-11:09:52.875 | Exception | main | HyperboxService
java.lang.NullPointerException
   at io.kamax.hboxd.store.local.FolderStore.<init>(FolderStore.java:36)
   at io.kamax.hboxd.factory.StoreFactory.get(StoreFactory.java:37)
   at io.kamax.hboxd.factory.StoreFactory.get(StoreFactory.java:44)
   at io.kamax.hboxd.persistence.sql.SqlPersistor.listStores(SqlPersistor.java:135)
   at io.kamax.hboxd.store.StoreManager.start(StoreManager.java:60)
   at io.kamax.hboxd.core.SingleHostServer.start(SingleHostServer.java:206)
   at io.kamax.hboxd.controller.Controller.startBack(Controller.java:80)
   at io.kamax.hboxd.controller.Controller.start(Controller.java:157)
   at io.kamax.hboxd.HyperboxService.start(HyperboxService.java:39)
2016.07.17-11:09:52.875 |      Info | -------> Hyperbox is stopping <-------
2016.07.17-11:09:52.875 |      Info | Stopping front-ends
2016.07.17-11:09:52.875 |      Info | Finished stopping front-ends
2016.07.17-11:09:52.875 |      Info | Stopping back-ends
2016.07.17-11:09:52.890 |      Info | Finished stopping back-ends
2016.07.17-11:09:52.906 |      Info | -------> Hyperbox halt <-------


Can anyone help me?

Thanks.

Graziano

noteirak
Site Admin
Posts: 106
Joined: 14 Dec 2013 08:03
Location: Altherian
Contact:

Re: Windows 7, VB 5.1 & start service problems

Postby noteirak » 17 Jul 2016 15:41

This error is caused by a store that was registered but is not accessible anymore (deleted or permissions do not allow read), possibly due to the switch of user context between running it from console and then as a service.

I've put together a temporary fix that will allow the server to start and you will have an additional column in the store list view on the client that will allow you to pint point which folder is the issue.
Clearly, I need to put together better code here to manage this kind of situations which are not uncommon.

You can download the test build here: https://kamax.io/hbox/download/latest/

Let me know if that fixed your issue!

Graziano
Posts: 2
Joined: 17 Jul 2016 11:16

Re: Windows 7, VB 5.1 & start service problems

Postby Graziano » 17 Jul 2016 22:35

Hi again!

After installing the new server the service start. After I create a new server entry, started, connected the hypervisor aqll seem works but no one of the my 3 VM is showed.
I've tryed to register one of the VMs browsing the .vbox file in the appropriate folder and all the data seem ok but if I try to start the tast say STARTED but noting start!
If I run VirtualBox all the VMs are stopped.
If I do the same thing with command line batch all works fine.

Code: Select all

+==============================================================+
 Log start on 17/07/2016 @ 22:33:32           +
+==============================================================+
Hyperbox 0.0.13-1-g8f09a80 - Java 1.8.0_91 Java HotSpot(TM) 64-Bit Server VM 25.91-b15 - Windows 7 6.1 amd64
2016.07.17-22:33:32.039 |      Info | Hyperbox Init Sequence started
2016.07.17-22:33:32.719 |      Info | Server ID: dd3086a3-edce-4360-98f0-060bf764e956
2016.07.17-22:33:32.719 |      Info | Server Name: io
2016.07.17-22:33:33.349 |      Info | Refreshing modules...
2016.07.17-22:33:33.349 |      Info | Searching in C:\Program Files\Hyperbox\Server\modules for modules...
2016.07.17-22:33:33.349 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_3-ws.xml
2016.07.17-22:33:33.384 |      Info | Module ID vbox-4_3-ws (Virtualbox 4.3 WebServices Connector) was successfully registered
2016.07.17-22:33:33.526 |      Info | Module ID vbox-4_3-ws (Virtualbox 4.3 WebServices Connector) was autoloaded
2016.07.17-22:33:33.527 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-4_3-xpcom.xml
2016.07.17-22:33:33.532 |      Info | Module ID vbox-4_3-xpcom (VirtualBox 4.3 XPCOM Connector) was successfully registered
2016.07.17-22:33:33.572 |      Info | Module ID vbox-4_3-xpcom (VirtualBox 4.3 XPCOM Connector) was autoloaded
2016.07.17-22:33:33.572 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_0-ws.xml
2016.07.17-22:33:33.577 |      Info | Module ID vbox-5_0-ws (Virtualbox 5.0 WebService Connector) was successfully registered
2016.07.17-22:33:33.737 |      Info | Module ID vbox-5_0-ws (Virtualbox 5.0 WebService Connector) was autoloaded
2016.07.17-22:33:33.737 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_0-xpcom.xml
2016.07.17-22:33:33.742 |      Info | Module ID vbox-5_0-xpcom (Virtualbox 5.0 XPCOM Connector) was successfully registered
2016.07.17-22:33:33.794 |      Info | Module ID vbox-5_0-xpcom (Virtualbox 5.0 XPCOM Connector) was autoloaded
2016.07.17-22:33:33.794 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_1-ws.xml
2016.07.17-22:33:33.800 |      Info | Module ID vbox-5_1-ws (Virtualbox 5.1 WebService Connector) was successfully registered
2016.07.17-22:33:33.968 |      Info | Module ID vbox-5_1-ws (Virtualbox 5.1 WebService Connector) was autoloaded
2016.07.17-22:33:33.969 |      Info | Attempting to add module with descriptor file: C:\Program Files\Hyperbox\Server\modules\vbox-5_1-xpcom.xml
2016.07.17-22:33:33.972 |      Info | Module ID vbox-5_1-xpcom (Virtualbox 5.1 XPCOM Connector) was successfully registered
2016.07.17-22:33:34.007 |      Info | Module ID vbox-5_1-xpcom (Virtualbox 5.1 XPCOM Connector) was autoloaded
2016.07.17-22:33:34.007 |      Info | Finished refreshing modules.
2016.07.17-22:33:34.008 |      Info | Loading Hypervisor configuration
2016.07.17-22:33:34.010 |      Info | Hypervisor ID: vbox-5.1-ws
2016.07.17-22:33:34.010 |      Info | Hypervisor options:
2016.07.17-22:33:34.010 |      Info | Hypervisor AutoConnect: true
2016.07.17-22:33:34.010 |      Info | Hyperbox will auto-connect to the Hypervisor
2016.07.17-22:33:34.015 |      Info | Starting Front-ends
2016.07.17-22:33:34.058 |      Info | VirtualBox Web Services server started
2016.07.17-22:33:34.167 |      Info | Kryonet connector is listening on port 45612
2016.07.17-22:33:34.167 |      Info | KryonetServerFront has started
2016.07.17-22:33:34.167 |      Info | Done starting Front-ends
2016.07.17-22:33:34.168 |      Info | -------> Hyperbox is running <-------
2016.07.17-22:33:40.334 |      Info | Connected in 6295ms to team.loc
2016.07.17-22:33:40.335 |      Info | VB Version: 5.1.0
2016.07.17-22:33:40.337 |      Info | VB Revision: 108711
2016.07.17-22:33:40.338 |      Info | VB Client API Version: 5_1
2016.07.17-22:33:40.339 |      Info | VB Server API Version: 5_1
2016.07.17-22:33:40.348 |      Info | Host OS: Windows 7 6.1.7601sp1

I hope to be useful!

Graziano

noteirak
Site Admin
Posts: 106
Joined: 14 Dec 2013 08:03
Location: Altherian
Contact:

Re: Windows 7, VB 5.1 & start service problems

Postby noteirak » 17 Jul 2016 22:44

VirtualBox will not show you state of objects that are running in a different security context (different session and/or different UAC level) so anything happening at the service level will not be visible to your VirtualBox running as your user.
And vice-versa, hyperbox will not see your VMs since they were registered under your own user and not under the service account running hyperbox.

So if Hyperbox says the VM is STARTED, then it is, but under the session service account, which is the purpose of it.
If you would like to see your VM console, just like you were running it with the VirtualBox GUI, you need to:
- install the VirtualBox extension pack for the VRDE module using the VirtualBox GUI or vboxmanage
- Ensure that all VirtualBox processes are stopped, including the hyperbox server
- Start Hyperbox server again
- Via Hyperbox, configure your VM and enable the console (Output section), ensure the port is not in use before!
- Start your VM
- Click on the "Connect" button next to the "Console Address"


Return to “Using Hyperbox”

Who is online

Users browsing this forum: No registered users and 1 guest

cron