Posts made by ITSolutions

@Data31337 How are you mounting the share currently? You said it is mounted as /images/external if you just change your mount point to /images you should be able to complete it that way

@Wayne-Workman said in Storing FOG Images on Separate Network Drive:

@Data31337 Yes, it’ll work for network drives - but again - you cannot re-export an already exported drive. You can mount as many shares as you like for whatever purpose you like on the fog server, but those can’t be used directly for imaging.

I am not sure what you mean by this I have a simalar setup and it works great for me. Actually I have 2 storage groups on the same master FOG server. I did have to add in the /etc/exports the extra lines to do NFS correctly. But in the OP’s case that shouldn’t be needed.

@Data31337 I just re-read your “work around” instead of do as I described you could just mount the /images directory directly to the external storage the same way you are doing the mount of the /images/extstorage

What is the file system on your extstorage?

@Data31337 I haven’t tried that, so not sure it it will or not.

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

@ITSolutions Sorry, it’s an old version that was released last week that I’m currently using. I’ll update to the latest and let you know how I get on.
Did you upgrade the server from 1.2 or did you build a new server and is it the same IP?

@Data31337 I think I actually have exactly what you are trying to do working in my setup.

If you want Ubuntu to automatically mount a USB drive on boot it is possible.

First I would rename the /images to /images2
Then create a new /images folder

Next you need the UUID of the drive
-Go to a terminal and type sudo blkid and find the dev for your external drive and copy/make note of the UUID.
-Then sudo nano /etc/fstab and add the following line tot he end of it:

 UUID=(Copy the UUID of your drive)   /images      ext4  nofail,auto,noatime,rw,user 0	 0

Then run sudo mount -a

Reset the permissions on the /images folder and move all images to the new /images folder.

You should now be able to use your external drive. Make sure that the drive is plugged in at all times, especially at reboot.

@RobTitian16 Is this a new install of FOG trunk or an upgrade, I guess I am a little confused re-reading your OP.

What version of trunk do you have? If it is below 7971 can you try updating? This version was just released.

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

@ITSolutions Ubuntu 14.04… Perhaps it’s time to upgrade?

No definitely don’t upgrade Ubuntu broke a lot of things in 16.04, so 14.04 is a better choice for now. Ubuntu moved the default location for web pages in 14.04 from /var/www to /var/www/html. FOG is designed to do a symlink back to /var/www, but maybe something broke in that. Can you check to see if there is a /var/www/fog folder and a symlink /var/www/html/fog?

@RobTitian16 Something that I forgot to ask is what OS is FOG running on?

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

Windows 10 Pro with Google Chrome. I’ve already attempted to clear my browser history, cookies, etc. to no avail.
The server is Windows 2008 R2.
I do get the correct IP when I ping Fog-server.

Another thing to note is that when I go to the ‘wrong’ login page, I can’t login using any of my credentials. It keeps saying username/password is incorrect.

Can you try with IE or Firefox? I have had issues with Chrome using some hidden DNS stuff or something. Not sure how chrome handles DNS, but I had a case that in a school I worked at DNS was having an issue and user couldn’t get to a testing site, but in chrome they had no issue.

What OS are you going to the login page from and what browser? What kind of server are you using for DNS? If you ping fog-server does it return the correct IP?

This isn’t a FOG problem, it is definitely a DNS issue.

@Roger-Saffle How many partitions does your image have? It appears to me that you could be using a resizable as you state the VM is only 40gb, but your machine that is being deployed to is 250gb.

OK so I did some more testing and found a few issues.

First is that it appears the 0.10.x line of the client seems to ignore the update client settings. Even with the client updater globally disabled it will update to the latest. Not sure if @Developers are aware of this. So I cannot test an older version of the client as it just auto updates to 0.10.6

Second is that I modified the DB so that one of my snapins had an ID of -1 just for testing. When I tried deploying to the client it thinks there is something to do in the HostnameChanger module. Once I logged out to let it complete the “Host name task” it cleared the snapin task from the que, but does not run the snapin, and everything reports fine.

I tried the 0.9.12 client as it won’t update, as I have the update feature disabled, and it gives the following error for all modules.

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 6/1/2016 4:54 PM Client-Info Version: 0.9.12
 6/1/2016 4:54 PM SnapinClient Running...
 6/1/2016 4:54 PM Middleware::Communication URL: http://10.1.90.2/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=F4:B7:E2:1D:29:3D|B8:CA:3A:C9:5E:9A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
 6/1/2016 4:54 PM Middleware::Communication Unknown Response: Not Allowed Here
------------------------------------------------------------------------------

Another update, I tried creating a new snapin on the new FOG server and deploying it to the client, I still get the same error.
I have also reset the encryption data on the client.
I have uninstalled and re-installed the client also.

I am truly at a loss on this one.

I just checked the DB and the the snapin ID’s for the snapins deploying to the client are correct. Another add thing is that if I have multiple snapins in the que it will show that the client has checked in for all of them.

There are quite a few errors in the apache log, so I am posting it if it might help.
0_1464802312693_error.log

@Roger-Saffle This is a different issue. The OP is reporting that one partition doesn’t resize after deploying.

Since you created as a non-resizable it is finding that the drive is reporting that it is smaller than the image is supposed to use. This could be due to partition tables, or differences in drive manufacturers. You could try doing a wipe on the drive before deploying to see if that helps, or shrink you VM to 39GB to compensate for the differences in the drives.

@Tom-Elliott There is no -1 in the database. This happens for all snapins, no matter what is pushed tot he client. I can do a full image, push all snapins, or just one it always gives the same in the log.

I just updated to the latest this morning 7961 and still having the same issue.

Not sure if moving servers may have caused this, this is the first time I have moved servers with the Trunk and the new client. But I am pretty certain I moved everything correctly.

I just migrated to a new FOG server and am having issues with snapins. It could be something I missed but I can’t seem to figure out what I missed.

I am running Ubuntu 14.04 fully updated
FOG Trunk 7945, which is up to data as of this writing
Win 7 with 0.10.6 client

I used the .fogsettings from my old server (which was also on 7945)to install FOG. I moved my /opt folder and my /images to the new server.

The client will image and join to AD, user tracker seems to work also. When it goes to run snapins I get the following log

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 5/31/2016 4:44 PM Client-Info Client Version: 0.10.6
 5/31/2016 4:44 PM Client-Info Client OS:      Windows
 5/31/2016 4:44 PM Client-Info Server Version: 7945
 5/31/2016 4:44 PM Middleware::Response Success
 5/31/2016 4:44 PM SnapinClient Snapin Found:
 5/31/2016 4:44 PM SnapinClient     ID: -1
 5/31/2016 4:44 PM SnapinClient     RunWith: 
 5/31/2016 4:44 PM SnapinClient     RunWithArgs: 
 5/31/2016 4:44 PM SnapinClient     Name: 
 5/31/2016 4:44 PM SnapinClient     File: 
 5/31/2016 4:44 PM SnapinClient     Created: -1
 5/31/2016 4:44 PM SnapinClient     Args: 
 5/31/2016 4:44 PM SnapinClient     Action: 
 5/31/2016 4:44 PM SnapinClient ERROR: Snapin hash does not exist
------------------------------------------------------------------------------

When I check 10.1.90.2/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/win7rollup.msu
it returns:
cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e|0

So it appears that it can find the file and hash it, but doesn’t find the hash where ever the client is looking for it.

I find it odd that the ID is reporting -1 in the log.

Anyone have any suggestions?

@RLane

Are you installing a completely fresh build of Trunk?
What version of trunk are you trying to install
Are you using a .fogsettings file from a previous server?
How much space does your root drive have?
Is MySQL running?