• Nginx installation guide for Debian Wheezy

    11
    0 Votes
    11 Posts
    4k Views
    T

    I installed FOG again, and same issue happened.

    /opt/fog/.fogsettings is nowhere to be found.

    Can’t find the proper file to stop apache2.

    drwxr-xr-x 8 root root 4096 Aug 21 14:10 …
    drwxr-xr-x 2 fog fog 4096 Aug 21 14:10 bin
    -rwxr-xr-x 1 fog fog 27695 Jul 20 2014 changelog.txt
    drwxr-xr-x 3 fog fog 4096 Aug 21 14:10 FOGCrypt
    drwxr-xr-x 4 fog fog 4096 Jul 21 2014 FOG Service
    -rwxr-xr-x 1 fog fog 1419 May 28 2014 installation.txt
    drwxr-xr-x 2 fog fog 4096 Aug 21 14:10 kernel
    drwxr-xr-x 5 fog fog 4096 Jul 21 2014 lib
    -rwxr-xr-x 1 fog fog 35147 Feb 12 2008 license.txt
    drwxr-xr-x 6 fog fog 4096 Jul 21 2014 packages
    drwxr-xr-x 2 fog fog 4096 Aug 21 14:11 rpttmp
    drwxr-xr-x 7 fog fog 4096 Jul 21 2014 src
    drwxr-xr-x 7 fog fog 4096 Aug 21 14:10 utils ```

    This is installation error message: ```

    Configuring services.

    Setting up and starting MySql…OK

    Backing up user reports…OK

    Did you leave the mysql password blank during install? (Y/n) n

    Please enter your mysql password:

    Please re-enter your mysql password:

    Setting up and starting Apache Web Server…Failed!
    Script done, file is /var/log/foginstall.log ```

  • Second Drive Fog Server

    6
    0 Votes
    6 Posts
    2k Views
    george1421G

    Don’t forget that case IS important, /Images2 is not the same as /images

    The idea is to mount the /dev/sdb1 partition over a temp directory, move the contents of /images to that temp directory, unmount the temp directory and then mount /dev/sdb1 over /images. That way there is no need to change the FOG settings one bit, its all done in the linux realm.

  • boot error after deplying linux image

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    N

    well,
    i tried another way and solved it.
    installed grab4dos on the hard drive and set up a menu that will grab and boot thinstation.iso.
    captured it as a linux image, and deployed with no problems!

  • Unable to install Fog on RHEL7 / CentOS7

    Solved
    14
    0 Votes
    14 Posts
    4k Views
    george1421G

    @dwithandelmo Great job, it would be interesting to know why RHEL7 is different then Cento7. But at the end of the day, as long as you have fog up and running with the least amount of extra headache then we’re good.

    As for 1.2.0 acting the same way on Centos7 I can kind of expect that too.

  • Windows Other (4) Error / Updating Fog from 1.01

    5
    0 Votes
    5 Posts
    2k Views
    Wayne WorkmanW

    @mcgill-eus if you follow the Upgrade to Trunk instructions exactly, you’ll get Release Candidate 6. RC-7 will probably be out sometime today though and I feel it highly important to move to that when it’s out, as it fixes some issues in 6.

  • Boot menu configuration

    18
    0 Votes
    18 Posts
    5k Views
    B

    @Quazz
    OK!!! Houston we have liftoff…

    I was able to get this working by completely ignoring mounting the iso at all and instead doing what I had found in another forum with directly using memdisk and the raw iso. My working config for this is as follows

    0_1469802843514_upload-365ae328-e013-4ad9-b6cc-2f6183ce8087

  • Network throughput crippled.

    Solved
    12
    0 Votes
    12 Posts
    4k Views
    Wayne WorkmanW

    So, we found out what it was.

    A security camera contractor had damaged the fiber line that the VMWare platform used.

    He fixed it Friday morning. I’m guessing he told our network team what happened sometime Friday. After that, everything was fine.

  • FOG ICS-DHCP does not auto-start at bootup (Debian 8)

    7
    0 Votes
    7 Posts
    3k Views
    Wayne WorkmanW

    @coco65 Awesome.

    I’ll add the details to the #wiki sometime, so we know in the future.

  • Howto clone xfs partitions ? (upload and download, multicast)

    Solved
    10
    0 Votes
    10 Posts
    3k Views
    sudburrS

    My quick test with build 8599 of capturing CentOS 7.2.1511 as:

    /sda1 Boot xfs
    /sda2 Swap swap
    /sda3 / ext4

    … it captured and deployed fine.

  • Host Management: "Connection Refused" on Raspberry Pi client

    5
    0 Votes
    5 Posts
    2k Views
    Wayne WorkmanW

    Your imaging a pi with fog?

  • Constant bandwidth suck

    Solved
    9
    0 Votes
    9 Posts
    3k Views
    N

    @Joe-Schmitt said in Constant bandwidth suck:

    Either re run your fog server installer or upgrade. The smart installer can’t be downloaded from your server. This means it wasn’t obtained properly when you last upgraded your server.

    I moved .fogsettings to .fogsettings.old and ran the upgrade. Seems to have fixed all my remaining issues, including my broken replication. Thanks for that. I’ve been upgrading regularly for months now and I’m not sure now if it’s just coincidence that I moved .fogsettings and let it regenerate. In any case, looks like I’m back to normal here. Thanks again.

  • Images not properly expanding after update from Trunk

    Solved
    20
    0 Votes
    20 Posts
    5k Views
    S

    @wbtech said:

    On the plus side, I just did an upgrade from the trunk and everything worked perfectly. I was able to capture and deploy an image and everything expanded properly.

    Great to hear. So I guess you had a “buggy” version of the inits in place, something we already fixed along the way.

    I owe you guys a beer!

    I think this is number three or four on my list. 🙂 Should start to think about getting on a plane to visit all those people at some point… haha.

  • FOG on an Isolated network and Production network at same time. Possible?

    8
    0 Votes
    8 Posts
    3k Views
    george1421G

    @Bob-Henderson Setting this up isn’t a problem and a pretty simple setup. Please create a new thread since you have specific requirements.

  • How do I reboot Linux with a Snapin?

    5
    0 Votes
    5 Posts
    2k Views
    K

    @Joe-Schmitt Thanks so much! That worked like a charm

  • Dual NIC clients

    25
    0 Votes
    25 Posts
    10k Views
    Wayne WorkmanW

    @tag correct. No getting around that.

  • hostname won't change on clients

    2
    0 Votes
    2 Posts
    1k Views
    Wayne WorkmanW

    Did you install the fog client on the image? Did you register the destination host?

    Oh - read further… you mention /etc/hostname. Fog 1.2.0 doesn’t change names on linux. This functionality is only available in fog trunk, with the new fog client properly installed on the image.

    Read these two links for info:

    https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

    https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

  • PXE Not Uploading

    4
    0 Votes
    4 Posts
    1k Views
    S

    @cschwab Please post a picture of where the client hangs (times out)!

  • Setup Debian image - How?

    Solved
    5
    0 Votes
    5 Posts
    2k Views
    L

    This worked great! The Wiki for installing Mono should be updated for Debian Jessie, as apt-get does not work for installing Mono. I had to resort to the instructions on this page:

    apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF echo "deb http://download.mono-project.com/repo/debian wheezy main" | tee /etc/apt/sources.list.d/mono-xamarin.list echo "deb http://download.mono-project.com/repo/debian wheezy-apache24-compat main" | tee -a /etc/apt/sources.list.d/mono-xamarin.list echo "deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main" | tee -a /etc/apt/sources.list.d/mono-xamarin.list apt-get update apt-get install mono-complete
  • FOGImagereplicator not working

    22
    0 Votes
    22 Posts
    9k Views
    N

    @Tom-Elliott said in FOGImagereplicator not working:

    @Neil-Underwood DHCP Server if FOG is to be the dhcp server.

    It defines the start and end range of DHCP.

    Got it. So this does not apply to my setup then. Must have been defined a long time ago when I was playing with that. Thanks!

  • #!db

    Solved
    18
    0 Votes
    18 Posts
    4k Views
    Wayne WorkmanW

    Tom figured out the problem was due to mis-matching storage node versions and main server version of fog. the main server is behind a little from the recent node installations. Tom was able to create a patch that solved the issue without me having to update the main server, it is working good.

98

Online

12.2k

Users

17.4k

Topics

155.6k

Posts