FOG Imaging Not Saving
-
@george1421 But that IS the image I created, just in the wrong folder?
-
It’s not the wrong folder. As @george1421 states that folder where the files of the image you uploaded are is a temp folder so to speak so that once it’s completed uploading then the next task is to move it to the images directory. That is what FOG does. So it’s clear at this point that it’s definitely a credentials issue here because the image does upload but the very last step for FOG is to move those files to the Images directory but it can’t because it requires the proper credentials.
I would re-read the suggestion @george1421 said earlier and examine your files to confirm credentials are accurate. I hope that helps.
-
@jgallo I understand there is a credentials issue and that FOG will automatically move the image to the appropriate folder once that is resolved.
However, can I not just copy the files myself to the folder named for the image name? -
@dpotesta50 Well yes if you want to salvage this captured image you can do that. It would be a bit tedious if you had to do that for every image.
Also I would use the
mvcommand over thecpcommand so it won’t have to copy the files only move the directory entries (like ftp would do). -
Yes. You would need to connect to the FOG server via FTP from your computer. I would highly discourage from using this method because if you have storage nodes replication gets out of wack at least in my experience. I believe something to do with file permissions to the directory.
If you are just worried about getting the image over to the proper directory and get working that it easy but doesn’t resolve the bigger problem. You could just re-name that folder with the MAC address with the name of the image you defined in FOG and place it in the /images folder. As long as the name matches and all the files from the screenshot you took are placed in there, you should be fine to deploy the image. Hope that makes sense.
-
Place the newly re-named file from /images/dev/(name of image) to /images so it resides outside of the dev folder.
-
@jgallo
That’s not the path to the images. All the images are under “/images” and the one I’m working with is under “/images/New_Windows_Test10-9”. -
OK. So if the image you have defined on the Web UI is named New_Windows_Test10-9 then the location of that image is /images/New_Windows_Test10-9 but remember that it will not exist if it’s a new image because your FTP credentials are not working right now. So there is no way for it to exist unless you create the folder manually. Hence why it would be imperative you focus on figuring that out as well so you don’t need to do this tedious work around. In any case as long as the directory is matching what you defined in the Web UI when creating a new image then you can simply use the mv command into that new location.
-
@george1421 It’s been awhile since I posted because I was exploring other imaging options. Since this is established I really need to learn it.
So you last instructed me to check the /.fogsettings text file for the FTP password. I found it and it’s an extremely ridiculous string of alpha-numeric characters. Nothing that anybody would remember. Is this particular password used automatically by the system or is it suppose to MATCH the GUI password? -
@dpotesta50 Its been so long I really forgot about this thread or where we are (and a bit lazy to re-read it at the moment).
The password in the .fogsettings file is intended for internal use by the fog server and not by users. Its is intentionally long and complex to protect your fog server from brute force password hacks. This linux service account
fogwhere the password is associated with is only for the fog service. It is not the same as the default web gui admin account called fog. -
@george1421 I’ve tried logging in multiple times via FTP using that password but fails everytime. HOWEVER. I’m not convinced it’s not failing because I’m mis-typing it. (though I did copy and paste the password and it still failed.) I will add, images created by the engineer BEFORE ME are working perfectly fine. We have no problems pulling those images. Only the ones i’m creating are having issues.
-
@dpotesta50 ok lets assume that someone has mucked about with the linux user
fog’s user account. (Not implying one way or the other). Since you can’t login via ftp, that is kind of in line with someone changing the fog user’s password.I’ll give you a hint here: if you use putty (free) from a windows computer to connect to your fog server when reviewing your .fogsettings file, you can copy and paste that crazy password much easier.
I just wrote a tutorial on how to resync the fog service account here: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password
-
@george1421 I was using CuteFTP so I’ll try putty. To clarify, this is what you’re talking about?
http://www.putty.org/ -
@dpotesta50 yes, putty has several components, but what you might be interested in is the program called putty, which will give you remote terminal access to your FOG server. From there you can view the files just like on the console of the fog server, with the ability to copy text on the screen and paste it into an editor or web gui as part of the resync process.
-
@george1421 So what do these FTP credentials do for FOG and why are they (possibly) hindering my imaging process?
-
@george1421 I see no way to paste the password. CTRL-V doesn’t work. Right-Click- Paste is not available.
-
@dpotesta50 when using putty, highlighting text copies that text into your clipboard. right clicking pastes clipboard contents into the terminal window
-
@junkhacker it’s not going to auto-copy by highlighting OUTSIDE of putty i’m sure. I have the password in a regular text file on the desktop. I copy it, switch to the putty terminal window, right-click (no menus or anything show up), hit enter and get “invalid password”.
-
@junkhacker Not invalid password but ACCESS DENIED
