I have a fresh install ubuntu server 12.04-3 64bit on a AMD 8 core CPU FX-8320 with 8 Gb ram.
In certain conditions working on a virtual machine phpvirtualbox crash and reboot my server ... in particular every time you try to modify some aspect of vm (i.e. network card, video, etc).
The only trace that I can found is in the access.log of apache where, upon before crash I found:
... POST /phpvirtualbox/lib/ajax.php HTTP/1.1" 200 649 "http://<myserver ip="">/phpvirtualbox/" "Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0"
repeated every 3 second until crash ....
I have disabled the auth in config.php.
kernel is 3.8.0-32-generic, virtualbox and phpvirtualbox are 4.3 (latest available, but I have the same problem also with previous version 4.1 and 4.2), apache is 2.2.22-1ubuntu1.4 (latest available from repository).
I suspect a bug in the ajax.php and a vulnerability in apache ...
Any ideas ?
Thank in advance,
PHP/apache running in user space should not reboot your server. What version of VirtualBox are you running? On what OS? What do you see on the monitor after a crash? Or does it just reboot without a console message?
As I have wrotten on my post, I have a fresh install Ubuntu server 12.04-3 AMD64 and the virtualbox is 4.3 (but the problem is present also with 4.2.18) ... Sincerly ... I have not attached a monitor on my server (is not in my room but is in another room on another flor in the same building .. I operate by remote with ssh).
Now I have downgrade (deletting all previos config files of 4.3 obviously) the virtualbox to 4.2.18 because the 4.3 have some other bug (google error VERR_SVM_DISABLED if you want to know in depth)
In the afternoon I will try to connect a monitor and operate by local ... I will say you what I see on the monitor (if I will see something) when the system crash.
Thank you for the attention gived to my problem,
I apologize for the long wait but only today I was able to do the tests.
I confirm that on the monitor nothing is write when the machine crash ...
Simply reboot ... as I have just sayed, the only info that i can found is in the log of apache where I see this:
POST /phpvirtualbox/lib/ajax.php HTTP/1.1" 200 648 "http://<myip>/phpvirtualbox/
repeated many time until the server crash.
I can assure you that the server have no problem and working fine except for this problem generated by phpvirtualbox.
I am here if you have any suggestion or request for other test to resolve the problem.
Thank in advance,
No more any suggestion ?
The request for ajax.php every few seconds is normal. That is phpVirtualBox polling for events. Try disabling authentication for vboxweb. Run:
VBoxManage setproperty websrvauthlibrary null
as the same user that vboxwebsrv is running as. Then restart vboxwebsrv and see if that fixes the problem. While using phpVirtualBox may "cause" the problem, phpVirtualBox itself is not rebooting the server. It is most likely something to do with VirtualBox itself.
Thank you for your help & patient ...
I have disabled authentication as you tell me, now when I open a browser and point to my server it don't ask me login.
But the problem is the same: when you try to change or also only display something in a virtual machine, the system crash.
For example, i have tried:
1) point to server with the browser;
2) click on my vm and on the right I can see the component of it;
3) click on "general", open the general popup (I closed with cancel without any modification);
4) click on "system" , open the system popup (I closed with cancel without any modification);
5) click on "display" and ... bang, the system crash.
But is randomic because before all working fine until storage.
Maybe, as you said, the problem will be virtualbox itself, but on the same machine, and same installation, I have checked RemoteBox as alternative to phpvirtualbox (phpvirtualbox was my first chosed but when it give me all this problem I had googled and have discovered RemoteBox) and with it all working fine ....
Ok, I can use RemoteBox, but I would like that the phpvirtualbox working fine ...
For this I ask you help on debugin ...
What do you mean by "because before all working fine until storage." ?
Hi, I mean the proof that I had done before had not crash the server until I arrived at the storage management ...
as I said, the system collapses in a completely random. You can not say if I do this and then this other then this other yet the system collapses ... can take place now and that after this operation and also after only after the first ... I hope to be able to make the idea ...
I have no idea on how to debug the problem, so was wondering if it is possible to trace in some way what is happening ..
Other than remembering your actions, no. I imagine some error is being printed to the screen or perhaps in some log file such as /var/log/messages or /var/log/syslog .. Ubuntu people should be able to help with that.
Log in to post a comment.