@Interrupt said:

I updated to the new SVN (3587) and the problem is gone.
MAC addresses are now imported from the CSV. Thanks!

Thx for the report 😉

After uninstalling the location plugin, there are tons of Apache errors that are related to ‘location’. I’ll try to post it if I get the chance. This happened when I was helping @ftgjason

@cml

That did it! DefaultMember storage node was not set to Master.

It immediately loaded up the page for creating a new image.

Thanks!!

it was in the file:

./trunk/lib/ubuntu/functions.sh

was already changed.

thanks

Thank you Tom! Works like a charm

r3566 fixes this bug. Just confirmed.

That’s how fast @Tom-Elliott works, to all of you who are skeptical of FOG Trunk. 🙂

Also the case with 3563.

@Tom-Elliott said:

I’m currently in my car

Seriously ? lol

Appears to be resolved with SVN 3563.

Resolve in new svn, thanks

ok great, everything is ok, thanks !

A refresh / update once per day would probably be fine.

But thanks for fixing this, Tom.

I just fixed a handful of issues with the apache vhosts configuration. If you’re daring, you can grab the latest github commit on dev-branch if you don’t want to wait for the next SVN.

Things I want to do later:

Give users the option to use buildroot themselves (it takes a long time) Make an init updater script so the init can be updated without just downloading everything and running the installer

The problem with the service start error seems to be that $linuxReleaseName in .install.sh evaluates to “Debian GNU/Linux”, not “Debian” as the scripts expect. After setting $linuxReleaseName manually in .install.sh, everything worked fine for me.

@ch3i said:

he ID of the image is always on the table “imageGroupAssoc”

That’s concerning… I’m on the same revision.

@crosser said:

Actually, now that I’ve looked at my own picture again, I see something wrong.

So my image name is “5700dec2012”, but the location in the picture above is wrong…

The correct location should be /images/fiber-storage/… not simply /images/…

How do I fix this?

Doublecheck that your /etc/exports reflect the correct path to the images, also. Can you post a copy here?

I’m solving this post simply because the title leads it to NEVER actually be solvable.

3517 should fix this issue. Thanks for reporting.