phpvirtualbox not starting after upgrade to salckware64-14.0
I finally found sometime to upgrade slackware64 to v14.0 and I can not get phpvirtualbox to present the login screen.
I had to re-enable php support in httpd.conf & to recompile the vbox kernel modules.
However, phpvirtualbox fails to start properly. Also I don't think there is a phpvirtualbox logfile to keep an idea of what might be wrong. or is there?
Has anyone else been through this?
I am completely unfamiliar with phpvirtualbox - did not know there was such a thing - but as no one else has answered I'll take a few guesses.
You said it will not present a login screen, do you get anything back from the http request?
You said you had to re-enable php in httpd.conf - if you are using a virtualhost to reach the phpvirtualbox host you may also find that you need to reconfigure vhosts in httpd.conf and the extras/httpd-vhosts.conf file.
From what I can tell from a quick look, it is all just an ajaxed web interface, so you might set up a very simple non-php target page at the location just to see that the path is reachable, then troubleshoot the php end afterwards.
So the starting point - is the target host reachable?
If so, add a php echo to the target - is php alive?
Then begin to look at phpvirtualbox itself...
Hope this is some help.
hi astrogeek. thank you for the information.
I know very little about html, and the apache webserver and absolutely nothing concerning php.
I haven't really tampered with it anymore than is absolutely necessary in order to setup virtualbox, webmin & mrtg (for squid monitoring).
the /var/log/httpd/access.log doesn't say anything when I go to the address.
I copied a simple html file in the phpvirtualbox folder and it is shown fine.
There exist some updates though. The server is headless and only today I fixed nx connection to the server so I logged in to the server and started a firefox session on the server. So I connected to "localhost" (unlike before where i was sitting on a client pc). Well from localhost I can connect properly.
Additionally, if from the same firefox session I replace localhost with the server's hostname (also available to my intranet through DNS), trying to get the login screen will again fial, but this time I'll get an informative msg:
from the same pc where virtualbox and phpvirtualbox are installed, I actually CAN access the phpvirtualbox login screen if I type in the address bar any of the following:
- <the pc's intranet ip address>/phpvirtualbox
I can NOT access the phpvirtualbox if I type:
What I get is the message
From any other intranet pc, (where I can only use the "hostname" or "hostname.atMyIntranet.domain" in the address bar to access the server) i will not get this message - just a blank page.
So it seems it is not a problem with the phpvirtualbox, or the php configuration itself..
Could it be the apache server? could it be the squid proxy? (there is a transparent proxy setup as well).
Any help would be greatly appreciated.
When I upgraded it removed the /etc/vbox/vbox.cfg file. In that file it tells which interface the vboxwebservice binds too. I had to recreate that file and added the following.
unfortunately this didn't help...but it comes as no surprise since the phpvirtualbox will actually startup fine when the address will be the ip of eth0 (and not the ip address of "lo" interface").
I have squid transparent proxy set up and redirect traffic from clients (even from the same server).
so I "tail -f" squid's "access.log".
When I open a tab with address http://localhost/phpvirtualbox, i get to see the following:
Now, if I open another tab at http://"hostname"/phpvirtualbox , nothing is printed in squid's access.log! as if the webserver does not (?) process the request somehow?
I checked with httpd's access.log and the same thing happens; nothing is wrtten when I access the site through its hostname.
|All times are GMT -5. The time now is 02:54 AM.|