Can't capture image, looks like permissions, but can't see how it could be
-
@enorum said in Can't capture image, looks like permissions, but can't see how it could be:
So fixed that, so now I’m able to connect, authenticate and send files to all of those directories.
You mean using a FTP client software? Please try creating files (upload), creating a directory, moving and deleting files… see if all possible file/dir operations work using a standard FTP client.
-
@sebastian-roth Sorry, yes, using an FTP client.
And yes, I can perform all of those actions using the FTP client.
-
@ENorum I suppose I should have explained more clearly on what to test using the FTP client. What FOG does at this stage is move the just uploaded image from
/images/dev/<MACADDRESS>
to/images/<IMAGENAME>
. So please try moving a directory like described above (same locations in the filesystem). I doubt this will work.Please post what you get when running
ls -al /images /images/dev
on the command line of yor FOG server -
Yeah, sorry. Not really familiar with Linux. I was able to move files and folders around in those folders.
-
@ENorum Maybe there is just not enough space on disk?? Run
df -h
and post a picture here. -
Had that problem, moved the server and added more diskspace 6 months ago.
-
@ENorum Well then, I have to admit, I am out of ideas for now. But I am sure others here in the forum have new ideas.
I am still wondering why this is working properly using a FTP client. Could you take a picture of when you move a directory (including files) from
/images/dev/abc
to/images/test
? -
Just for something abstract, is 10.2.0.87 your FOG master node server?
Oh, what the hell is that?? image name =v2Office365-SymFix/18 Why is that forward slash ( / ) in the file name? What you have done is allowed in FOG, but I don’t think that is what you really intended here. By putting the forward slash in there FOG will look for a directory called v2Office365-SymFix and place the image in a image directory named 18 This allows for grouping of like Images. If this isn’t what you intended, replace the forward slash with something other than a special character.
-
@george1421 Awesome man! We had this before and I remember noticing it after staring at the error pic long enough… but not this time. Great you found it!!!
-
Ok, fixed that and capturing a new image now, but I have to head home for the day. I’ll update tomorrow, but I bet that’s it.
Awsome guys, thank you. Especially you Sebastian for wracking your brain over it!
-
That did it! Thank you guys!