Has anyone successfully upgraded their Fog server?
Getting the nag message about 14.04 not in LTS anymore and pushing to do an upgrade.
Do I need to shut any services down before initiating this upgrade?
tried it once and it seemed Apache broke, so back to 14.04
@Sebastian-Roth
Yes, very much under time pressure in the business at the moment… I had to rebuild another Fog server… and I uploaded my 2 main images onto it manually… so I didnt use any of the backup procedure.
This is all a consequence of being forced by company circumstances to run things into production without any testing time…
the joy of decisions being made above your head and you just being told to get on with it!
The wiki is out of date for backup process?
Has anyone documentd the process for my version?
I have a second fog server with some images on it… they fail to push because I havent copied over the sql table from the original Fog server.
So just need
copy sql from first FOG copy over to second Fog
cheers
all
Just need the commands to copy
Personally, I would setup a test FOG environment just get FOG working.
I was in the same boat quite a number of weeks ago.
Setting up FOG on your established network will be tough to get right.
Use the standalone approach firstly.
It probably took me 40 to 50 hours of work to get a solution.
Last week using my Fog server , I was able to image 50 PCs in Win7 Sysprepped mode ready to join the domain.
My breakthru was seeing FOG actually working when I used a VMbox setup on my own PC following a YouTube tutorial.
good luck
When I can, I will be copying the sql table over to the new server.
I will update as to success when trying to push an image out.
Do I have import/export on 1.2.0? didnt think I did…
anyway, done some digging…
if I do the backup command mysqldump … etc
and then do a restore with the set of commands as in Fog Wiki
https://wiki.fogproject.org/wiki/index.php?title=Restoring_FOG_from_Backup
that should do it also?
I have copied over 2 important images from a FOG server to a new server.
It seems I need to have the images table re created or copied as well?
Is there a method of doing this?
The new Fog server is reporting the existence of the images in Storage and I have recreated the image names in Image Management.
A test download failed… but was just too quick to note any meaningful error message…
Ubuntu 14.04
Fog 1.2.0
I am installing Windows 7 Enterprise on an HP 280G1 with its 500gb hdd.
As this is not a ‘factory install’ I am aware it is presenting issues after uploading to FOG and then deploying to a new client.
It can fail to find the MBR.
A vanilla FOG image with HP Win7Pro out of the box presents no problems whatsoever.
Are there any best practices for FOG… re PARTITION sizes for example…?
I am making sure the credentials match like for like from the working FOG to the new one.
I moved the PC image up one level… but still not showing in the WEB gui… did permissions …
the screenshot shows a correct output this time s it does on my working VMbox FOG:
At the moment I am uploading the PC image again.
Will update progress
@Quazz said in FTP/TFTP issues:
The WebGUI looks in /images
If your image is in /images/dev then FTP failed to move it to /images
… any sensible reason why it should do this ?
I have a working FOG environment in VMBox… never had an issue, everything just worked … then replicating with actual workstations… and yet again one issue after another.
I’m just saying this to confirm that I have actually got FOG to work!
Screenshots:
Using my Fog server credentials how can I see the image listed on ftp:\
but the FOG web interface shows as 0??
That makes perfect sense… I will have to check how I amended the fstab file… which I know I did according to some other instructions.
Those ‘steps’ by the way are on the FOG wiki pages as regards NFS… there are noted as ‘old’ but there doesnt seem to be any ref to what you have suggested.
This editting the exports file
“/home/fog/images/”
and
“/home/fog/images/dev/”
for example.
If you already have created images with FOG, don’t forget to move the complete directory /images to the new place. Be sure that the correct access rights are granted.
/home/fog/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
After that tell the running NFS-server to read the new config:
exportfs -a
After that your “Disk Information” (Free / Used / Total) at the dashboard may not be correct anymore. Edit the file freespace.php in your web-root (/var/www/fog/status/) (on centos 6 see /var/www/html/fog/status):
define( “SPACE_DEFAULT_STORAGE”, “/home/fog/images/” );
You may also need to modify the permissions for the /home/fog directory. It is suggested that you use:
chmod 701 /home/fog
Nothing here mentions /dev/sdb* where my images now reside… it’s all about a share name … so this where I am getting confused… how does FOG know about a second hdd?
@Wayne-Workman said in Fog Download FAILS:
If you’ve added a second HDD to the FOG server and have re-configured your storage node to point to it, and have it mounted and all that jazz,
You still need to update the
/etc/exportsfile. This file is how to configure the NFS sharing for FOG. If a second HDD in the fog server is the case, it should be pretty simple for you to edit the exports file to reflect where the new images directory is.
Hi
I will check that file and edit appropriately if need be…
Unfortunately, I am in a position just to be able to get this deployment scenario up and running whilst having to attend to my other IT duties… not conducive to sensible troubleshooting.
Plan B now, is to create this whole FOG setup on VM box on 1 machine so that I can at least carry the entire concept on 1 laptop… and work out what works and does not work.
I havent even got to the point of overcoming the fact that the HP 280 desktop machines having UEFI boot as default.
Thsi is just a thought, I have installed a second hdd for the images… and all good when it comes to upload to the new image store.
Again Fog scripts seem to want to default to /dev/sda when the path should be sdb.
Does anyone else have issues with this?
I task downloading, the script runs… NO ERRORS… just doesnt do it.
I assume you mean I should have hit FOG at that point? anyways … at the moment I am re creating a n ew image with UEFI disabled and then I will test a download to another out of the box HP280 also with UEFI disabled.
A basic Win 7 image has been uploaded.
A debug download task created and fails at this point .
Any hints?
Last week successfully uploaded the image.
This is initial enquiry… I have about 70 of them to image soon for a new office.
I did a test a few weeks back and was able to grab a test image off one of the PCs with a basic Win7 build… when downloading to a fresh out of the box HP, it would’nt boot … I managed to rescue it with judicious use of a Win7 disk, but was lucky.
I will try with UEFI disabled in BIOS next week.
At least now , I have a working FOG environment to do this after 2 weeks of frustration.
Has anyone had any issues with deploying a FOG image to this model?
(The fact hat it has UEFI secure boot makes thing nervous)
