Can you show us what you mean by that exactly?

I might recommend playing around with the scan_delay and starting with 0.

@DarkSwordsman I would highly recommend leaving scan_delay at 0

Name them with the number they require in the group.

Eg 01-snapin, 02-snapin, 03-snapin

I believe you need to add two field into the accesscontrolrule side of things.

The Type: MAIN_MENU
The parent: main
The node (leave blank)
The value: accesscontrol

Possibly you will need to do this for site so:
The Type: MAIN_MENU
The parent: main
The node (leave blank)
The value: site

On 1.6 it will be two more than those but this should help.

@6rilT Let me play around a little bit. Mind you I’m running working-1.6 as @Sebastian-Roth has been doing wonderful keeping the 1.5.5 tree updated. So While some things are a little different, the actions performed should still be relatively similar.

Essentially, We just need to create the hook that manages the menu access. Without the menu available, with the access control plugin, a non-elevated user cannot access the access control and make changes, even if they know the url.

@Dee Then you may need to put the picture on an image sharing site. Something like imgur could work.

When you have errors from the GUI (and many backend areas) you can get them from:

redhat based:
/var/log/php-fpm/www-error.log
or
/var/log/httpd/error_log

Debian based:
/var/log/apache2/error.log

We need information.

The picture you uploaded didn’t complete uploading. (Hint, make sure you’re on a full screen browser, paste in the picture. On the right pain is a “preview”. Post/submit the posting when the image has appeared on the right hand window.

What version of fog?
What OS?
What error are you seeing. “Apache 2 error - won’t download -we’re down” doesn’t really tell us anything.

Our API on the init side is pretty simple. fog is the command that does all the actions for you. There’s no switches/arguments involved. Maybe in a future version we’ll have stuff like:

fog -D || fog --deploy
fog -C || fog --capture

fog -D -d || fog --deploy --debug
fog -C -d || fog --capture --debug

It’s not there yet and we rely pretty heavily on the web calls to generate the appropriate action.

@salted_cashews
I think you’re thinking too much into this.

If you have 1 storage group, the master node replicates its “replicatable” images to all storage nodes in the group.

If you have 2 storage nodes in one storage group, the images that are set to replicate will replicate from the master node to the other node. The space is not “divied” up. The master node will always be the node images captured are loaded to.

You could, I suppose, copy specific images from the master node and place it across other nodes so long as those images are not set to be replicated, but again, this does not increase your actual storage space. It just distributes it to the other nodes.

The simplest method, add more space to your master storage node.