I downloaded the latest OBS iso file (2.6.2) and installed it on virtualbox virtual machine. Everything went well, but after reboot when I try to open https://server_ip/ I get “Internal server error”.
I already tried to fix as said here: https://github.com/openSUSE/open-build-service/issues/905 - it didn’t help.
Where should I start to dig?
On Tue 09 Jun 2015 06:36:02 PM CDT, g4852251 wrote:
I downloaded the latest OBS iso file (2.6.2) and installed it on
virtualbox virtual machine. Everything went well, but after reboot when
I try to open https://server_ip/ I get “Internal server error”.
I already tried to fix as said here:
Internal Error 500 after initial install · Issue #905 · openSUSE/open-build-service · GitHub - it didn’t
help.
Where should I start to dig?
Hi
Are you sure the network started, if you login to the appliance and run
ifconfig you have an ip address?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Yes, wget is working and I also installed “nano” package with zypper.
I found very stange thing: on the same host machine with the same virtual machine everything works at my home network, but it doesn’t work at office network. I spent several hours at office trying to figure out what can be wrong and then came at home, started VM and successfully opened obs webgui. It is very strange, because i doubt that there can be restricted access to some neccessary for obs web resources. I’ll talk to IT specialist there to try clear everything.
So, finally I got obs working in it’s initial state with NAT/Bridged (doesn’t matter) on virtualbox VM. At least somewhere, but it is a good start.
I also noticed, that if OBS working properly (at my home network), then virtual machine is stopping and rebooting without issues. But at office network VM hangs at every reboot or shutdown, so I need to force close it and start again. And I wondering, how local network can affect at VM beyond host machine’s NAT?
Hi
Sounds like the network maybe generating traffic with your setup at the office, run something like tcpdump to see if it’s excessive. This maybe causing it to hang. Check with IT staff and see if you can get an ip address allocated to the vm mac address and use bridged (I use individual network cards for my vm’s and bridged on the host).
Yeh, I tried bridged networks adapter - result is the same.
Can you direct me where to look for logs of the error? Here is how it looks like:
https://dl.dropboxusercontent.com/u/9926406/internal_error.png
Yeh! I did it!
I changed dns server at my host machine to 8.8.8.8, so virtual machine uses the same, and everything is up now. Looks like the problem was in local or ISP dns.