@george1421 I do indeed but with loads of options in (), do I need options?

Also, whats the path to enter as a mount point? /data/images/*?

@george1421 said in Storage Node Permission Denied:

@coxm well that is where your access denied message is coming from.

As a test, update /etc/exportfs to the real locations. And then run the export -a command. And finally run the showmount command again to ensure the proper directories are shared.

Sorry, I dont follow. I dont have /etc/exportfs.

The only thing like it in /etc is /exports

@george1421
Hi,

The “Data” part ofthe file path ist he name of a second disk attached to the ubuntu box. Idea being have a large images disk and smaller system disk.

Showmount -e 127.0.0.1 results in

Export List for 127.0.0.1
/images/dev*
/images *

Upon going into those locations they do not hold the fog images found in the path shown in the screen shot.

it is a real fog server running on ubuntu configured as storage node only.
This is the error I am getting, looks more local bases than I first thought.

Hi All,
i have got a single master storage node setup in a remote office along with my main FOG server on my local site.

When I set of an imaging task for a machine in the remote location which uses the storage node I get a permission denied at the point of applying the image.

Any suggestions? I assume that the username/password somewhere doesn’t match?

Thanks

Perfect! That worked a treat.

In the interest of housekeeping, can I now delete that group? If so do I need to remove hosts first?

Thanks,
Matt

Hi All,

We have now changed the domain being used in our office from A.com to B.com as an example.

I have edited the default AD settings in the Fog Settings section but I can see that each host that was imaged prior to the change still has the old one set, i guess this was populated from the default options during imaging.

How can i get all hosts to reflect the new default AD settings? I am concerned that if I were to put fog live now any old client would reboot and try to change back to the old domain!

Thanks.

@sebastian-roth @Tom-Elliott
Thank you both so much, through a combination of things I have it working. you guys ROCK!

Thanks again!

@sebastian-roth
Hi,
Sorry for the lack of useful feedback!
Here are the shots of both files, its worth noting that originally the mysql password in the class.php file was blank. I have since edited.

This is my current apache2 log

@tom-elliott
Hi,
Have run df -h and have space on all partitions.

Getting desperate now, need to image some machine for our new users. Any other ideas? What about exporting the Db and reinstalling?

Just need to find a way back to a working Fog install with my existing Db.
Thanks,

@tom-elliott No luck

is it going to be easier to backup what I have and reinstall? I even have a working snapshot of the server, if I could ensure it using the newer up to date Db then I could roll back?

@sebastian-roth this is what I get, still in the mysql prompt use the fog database and get status

@sebastian-roth
This is what happens when using the username “root” and the same password as I would use to log into the fog web ui

@sebastian-roth Thanks. I did have some issues with username and password matching when configuring a new storage node but it still worked after that.

I can see in .fogsettings I have the username and password field which appears to be what I use to login to the fog web ui. then there is snmysqluser, snmysqlpass and snmysqlhost. currently thats “root”, blank and “localhost”. Is that correct?

Any further guidance this would be amazing.

Thanks,

Matt

@sebastian-roth ok cool, that makes sense. Where can I take the correct sql credentials from? .fogsettings?

Thanks,

Matt

@sebastian-roth That doesn’t seem to have resolved it.
Do you think its still a mysql issue? The MySQL error appears to have gone away and the service has started. I ran the repair sql command but all came back with status of ok.

@sebastian-roth Thanks, any pointers what to look for, there is alot of info on that link.

@sebastian-roth @Tom-Elliott
thanks for the help, I was out the office for a few days but back now and really need to get this sorted… Apache2 error…

@Tom-Elliott I have ow had some progress, turns out MySQL wouldn’t start due to the local nic being disabled and therefore couldn’t bind. This is now resolved but still I get an empty white screen from the fog management url.