Posts made by lmorel12

Tom, Wayne and George, THANK YOU!!!

It’s all good now. And I learned a lot. And archiving this on my end with my notes. Until next time.

I apologize for bugging so much…

@george1421 I upgraded to trunk. Went through the process with default settings. If it was clearly displayed that the path changed on me and I missed it, my fault. But I definitely did NOT change the path myself.

Again, my original configuration/installation might have something to do with it and years later those “leftovers” affected the upgrade to trunk setup? I really don’t know enough.

OK, so everything looked ok, process wise. I can see it’s doing the capture as usual, took around 10min for 17.17GB. But I also see “No valid data”.

@Tom-Elliott I added the /home/fog in front of /images and guess what? It worked!

I am embarrassed. Beyond embarrassed. But I can tell you I have NOT been in there and touch any of this. I will follow blindly tutorials and wiki without really knowing what it actually does concept wise, but definitely did NOT touch those settings under Storage Management.

Did upgrade to trunk affect this somehow? I wouldn’t blame anyone for concluding that I need to put that box of matches down and go back to my Legos.

@Tom-Elliott Sorry, but what do you mean by “that you keep blocking”? I don’t believe I have firewall up. I ran the following command systemctl status firewalld and it showed as “inactive (dead)”. I made a point to turn it off when I first installed FOG.

For selinux, are you asking about permissive vs enforcing? When I set up the server, I followed a wiki to do this because I wanted to run FOG on CentOS. Was I supposed to go through some of those steps again after upgrading to trunk? I got this “inactive (dead)” when I submitted the systemctl status selinux command.

This is what I see under Storage Management settings. Is that what you are asking?

Thanks! I did this (see screenshot) and I still get the same issue.

I am “worried” and concerned about one thing: I created a user called fog for that CentOS VM. I have been using root for everything though. But I also see /home/fog/images/dev with the “home” part in the path. I can’t remember if I originally set the server under the fog account. And I believe I was running out of space and followed a tutorial years ago to expand and mount the images folder. Like I said I have no idea what I am doing. And I followed tutorials blindly and it worked right away. I then moved on until I tried to go with the trunk route not long ago. I don’t know if any of this is helpful or not.

Server

• FOG Version: 1.4.0-RC-1
• OS: CentOS
  SVN Revision: 6069

Client

• Service Version:
• OS:

Description

I had my FOG server set up for over 2 years now. So this is not a new nor from scratch installation. I started having this issue after going with latest trunk. Another thing: I suck at linux. Big time. I do a lot of monkey-see-monkey-do stuff. While I agree this is not the best method, I managed to run and enjoy FOG for years. I should have known better than trying to upgrade it. To clarify, the server seems to be K, just cannot capture as I get the "could not mount images folder (/bin/fog.upload) error message. See screenshot below.

I also came across another thread similar to the error message I ran into (https://forums.fogproject.org/topic/9677/could-not-mount-images-folder-bin-fog-upload/18). I applied the CHMOD 777 command for the images folder. I also checked the NFS services status. I’m not sure what else I need to do. Or what I should provide here as useful information.

@Junkhacker Thanks!! I do a lot of monkey-see-monkey-do stuff. So I assume I did what others did to make this work. I applied the chmod -R 777 stuff as well. I checked the NFS services and it’s running.

I can’t say I am troubleshooting because I am applying “fixes” I found through this tread. i know, I know, that’s scary.

I will follow your advice and create a new thread. I suspect some will point me to this thread for resolution but let’s see what happens.

Anyone? Do I need to provide more information?

Using CentOS 7

I am running into a similar issue. Or maybe not?

Tue Mar 28, 2017 20:53 pm
Running Version 1.4.0-RC-1
SVN Revision: 6069

Mounting File System: Failed
Could not mount images folder (/bin/fog.upload)
Args Passed:
Reason: mount: mounting [IP_ADDRESS_HERE]:/images/dev on /images failed: Permissions denied

I suck at linux. I am a Windoz admin. I always followed FOG tutorials and got my FOG server running for years. I typically never touch it. I had an issue a few months ago regarding UEFI based images and installed the latest trunk. Since then I got this issue trying to upload/capture images.

Again I apologize in advanced. I read this thread several times but I’m not even sure if there is a fix throughout those posts or not. I guess I need some “translation” or being told where to get help. Sorry…