HTTP 500 error when creating new image

Firstly let me just say I’ve been using FOG for years under many different installs, but I just can’t get this to work for some reason.

I installed fog 1.2.0 and when I goto create a new image in the web interface, it just errors straight away with a HTTP 500 error. I removed the whole installation and started again and got the same results. I then decided just on a whim to install the latest fog trunk just to see if it fixed the issue - it did not.

Installation is on Ubuntu 12.04 LTS which is fully up-to-date. It is not a clean install, it has been supporting a network monitoring program for a little while and I wanted to use the same server for FOG as well purely as it’s the only server available to me here to host it on, and it’s not going to be used a lot - more for backing up workstation images rather than mass distribution.

Puzzled by this one as I’ve installed FOG plenty of times and I’ve been using it since 2008, this is the first time I’ve ever had a problem that I’ve not been able to solve.

@rstrofton what version of fog are you using? Maybe you could update to the more current release or even the RC series? This thread was over a year old so bringing it back from the dead is a strange site lol. This is also why I ask for version. I am pretty sure current fog is less restrictive in this (not that the issue couldn’t still exist but still.)

For anyone else (like me) who found this post while searching google for help…

I had no Master storage location configured, because I had deleted my master and forgotten to configure a new one. After ticking the master box for the default location, the “Add new image” page started working again

I started from scratch with the machine, and it’s now working so who knows what the issue was. It’s co-existing with netXMS perfectly happily now.

I do however have an issue with it backing up a Dell 9020 workstation, I think because of the recovery partition on the disk it keeps saying “invalid partition data!” when using the multi partition image type, but this is a totally separate issue. A block-by-block RAW copy works fine so the FOG program is working OK and the issue seems specific that that particular workstation. Annoying as it’s the one I was using for testing and it had me stumped for a little while thinking there was another problem with FOG when it was actually a problem with the workstation.

You can export all your images (copy them to somewhere), and inside of FOG Configuration -> Configuration Save, export your database there.

With the images and database safely backed up, you can rebuild this box and put the latest Ubuntu 15.04 or Debian 8 on it, and then import your images and database, set permissions on your images, and all should be well.

Just write down what revision your using now (top right corner, number on the cloud), and then install that exact revision on the new build.

With any luck, you can have all this done in 2 or 3 hours.

It’s a clean install, that’s the thing. The box is currently running netXMS for network monitoring which shared the MySQL database which I have backed up anyway before removing and reinstalling MySQL, so I might just start again. The issue is the hardware it’s running on is very old so the newest versions of Ubuntu could struggle and I’m not the most experienced Linux user in the world. It might be an easier option that trying to troubleshoot the issue.

The only thing I can think of is some feature on that page doesn’t support the methods that Ubuntu 12.04 uses.

It’s bizarre that only this specific feature doesn’t work, but everything else does…

You can export all your images (copy them to somewhere), and inside of FOG Configuration -> Configuration Save, export your database there.

With the images and database safely backed up, you can rebuild this box and put the latest Ubuntu 15.04 or Debian 8 on it, and then import your images and database, set permissions on your images, and all should be well.

Just write down what revision your using now (top right corner, number on the cloud), and then install that exact revision on the new build.

I un-installed each service individually and re-installed and it made no difference.

Then, just in case I un-installed all those services and removed the entire fog installation, restarted the server and then re-installed fog 1.2.0 using the install script. After all that I’m still getting exactly the same result and error when I go to create a new image. It is only this part of the process that’s causing a problem, everything else in the web interface works just fine, but without the ability to create a new image definition I can’t use the product of course which is a shame.

I don’t have a spare machine to do this with unfortunately, and it’s not really good enough to start running virtual machines on. I have a working install of 1.2.0 on the same OS elsewhere that wasn’t a bother and just worked out of the box.

The Apache logs do reveal an error, I should have looked at this before.

For the observant among you, please ignore the silly IP address range this network has, I inherited this network 4 weeks ago and re-addressing it is one of many things that need doing here (along with wanting to use FOG on this site as well if I can get it working!)