• How to sync StorageGroup masters with default group?

    8
    0 Votes
    8 Posts
    4k Views
    B

    @Wayne-Workman Thank you, Wayne. That really does clear things up. It sounds like the easiest thing to do (short of upgrading to trunk) is what I’ve been doing. Do a round of image updates and assign them to default. Clear ‘is master’ from all other storage nodes and move them to default group. Watch the logs for the sync to complete, move them back to their respective groups, recheck ‘is master’ on SNs since I only have a single SN per group. I only update these images a few times per year so that’s really not that painful. I could manage rsync scripts or a manual process but I’d rather let FOG do it especially if 1.3.0 will be along sometime in the not too distant future. Much appreciated!

  • Cannot mount <ip>/images, wrong IP is used

    Solved
    9
    0 Votes
    9 Posts
    5k Views
    Wayne WorkmanW

    @tgeyer What separate config would that be?

  • Combining FOG servers?

    6
    0 Votes
    6 Posts
    2k Views
    Wayne WorkmanW

    @george1421 said:

    We do have a list of required ports that JBob put together.

    Those are in the forums, but I’ve added them to the Wiki a while back, here:
    https://wiki.fogproject.org/wiki/index.php?title=FOG_security

    While I said multicasting would not work, I should clarify that multicasting will only work on one interface of your consolidated FOG server.

    I’m thinking that if he maintains separate Storage Groups per interface, and make each one a master, it would work. images can be shared across storage groups. But all replication only happens from the original storage group to the others, and not the other way around.

    I still don’t understand why the OP is even doing what he’s doing though. Albeit I’ve not given this thread hardly any thought.

  • Can't open multicast on clients (login issue)

    Solved
    14
    0 Votes
    14 Posts
    4k Views
    Q

    @Tom-Elliott I updated before testing again, yes, still this issue. Don’t know if it’s related but something similar happens with the debug options.

  • Unable to register and inventory new Dell PCs

    Solved
    45
    0 Votes
    45 Posts
    29k Views
    Wayne WorkmanW

    @Tom-Elliott You are fired.

  • Create Snapin on SVN 6415

    Solved
    8
    0 Votes
    8 Posts
    2k Views
    Wayne WorkmanW

    @wlainey said:

    nce I realized that SELinux had not been configured properly by using ‘setenforce 0’ everything starting working fine.

    You’ll need to set it permanently to permissive as well - you would edit /etc/selinux/config to do that. If you don’t, it’ll stop working again at the next reboot.

  • Image size on server: 0,00 iB

    Solved
    6
    0 Votes
    6 Posts
    4k Views
    george1421G

    Moving thread to solved.

  • dhcp/bootp: ignoring delayed packet

    9
    0 Votes
    9 Posts
    3k Views
    R

    A lot faster now 👍

    Thanks for your help.
    Regards

  • Lenovo Ideapad 100 -15 IBY Model 80MJ Boot From LAN Failed

    Solved
    7
    0 Votes
    7 Posts
    6k Views
    Wayne WorkmanW

    @Sebastian-Roth Yes, because he found a boot file that worked, and because we gave him instructions on how to make both work at the same time.

  • Error: either "dev" is duplicate or "Server" is garbage...

    3
    0 Votes
    3 Posts
    4k Views
    Wayne WorkmanW

    although wasteful, this command should fix it:

    cd /;rm -rf /opt/svn;mkdir /opt/svn;cd /opt/svn;setenforce 0;systemctl restart firewalld;for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done;systemctl restart firewalld.service;systemctl enable firewalld;yum install svn -y;svn co https://svn.code.sf.net/p/freeghost/code/trunk;cd trunk/bin;./installfog.sh

    Also - you can permanently disable SELinux by editing the /etc/selinux/config file.

  • Standard storage nodes or multiple TFTP servers in MPLS cloud?

    Solved
    32
  • PXE-E11: ARP timeout

    14
    0 Votes
    14 Posts
    14k Views
    george1421G

    @Wayne-Workman said:

    Well if they don’t, they will. Today is a snow day so I get to dive in again tomorrow.

    No worries, stay warm and safe.

  • Cannot image/register

    8
    0 Votes
    8 Posts
    2k Views
    Scott AdamsS

    Thanks for all your help. I hope so as well.

  • Surface Pro 4 not able to image, no network device

    Solved
    4
    0 Votes
    4 Posts
    2k Views
    S

    @Scott-Adams And there is another thread where we got past the “No Network Interface Found” issue I think. Try adding has_usb_nic=1 the host’s kernel parameter (host settings)! But it depends on the USB NIC used. We have pretty much every USB NIC driver included in the kernel but I guess there are devices out there for which the kernel does not have a driver (yet). Just give it a try and let us know.

    And please see exactly which USB NIC you have. Read through this interesting discussion on Surface 3. The first couple if posts (page 3) we talk a lot about the two different MS surface adapters and the NIC chip they have.

    As well make sure to update to the very latest trunk version. There have been a lot of fixes!!

    Edit: Re-reading the surface3 posts I remembered that we needed to add the PCI IDs for the MS USB NICs to the kernel. As far as I know those should work if you upgrade to the latest trunk!

  • Failure during image deployment.

    Solved
    29
    0 Votes
    29 Posts
    18k Views
    S

    @Wayne-Workman said:

    I’d estimate that 5 to 10 percent of imaging issues encountered are due to a bad HDD.

    Yeah right! We’ve seen this “quiet often” lately… Good to know that it wasn’t FOG doing something wrong.

    So all issues here seam fixed now… solving this!

  • After deploye grub fog 1.2.0

    11
    0 Votes
    11 Posts
    8k Views
    B

    @Junkhacker This fixed it for me. I changed my exit from the default (Sanboot style) to ‘GRUB Style’. ‘exit style’ didn’t work either. Oddly, this FOG server is a new install post development (in the ‘IT service’ prep sense). During dev on the old test server we didn’t have this issue. Not sure what changed.

  • Host is NOT Registered! tasks not processed

    17
    0 Votes
    17 Posts
    6k Views
    E

    @Sebastian-Roth said:

    @Eldorado What you experience is perfectly fine. The clients shouts back to the server not when it starts a task but when it finishes! You need to cancel the task in the web interface to stop the client from booting into it again and again…

    innnnteresting.
    I’ll give it a try… this is great… lol thanks for everything!

  • Multi-Cast Task don´t start

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    BASURILLABAS2B

    It´s work fine I need to configure the name of the interface in the storage management:

    0_1456158978750_storage.jpg

  • Can't add "all" hosts under one group

    17
    0 Votes
    17 Posts
    6k Views
    Wayne WorkmanW

    @Hanz This script does what you want.

    # This script adds all fog hosts to the below specified group name. # the group name is case sensitive. groupName=My-caseSensitive-Test-group-Name fogsettings=/opt/fog/.fogsettings snmysqluser="$(grep 'snmysqluser=' $fogsettings | cut -d \' -f2 )" snmysqlpass="$(grep 'snmysqlpass=' $fogsettings | cut -d \' -f2 )" snmysqlhost="$(grep 'snmysqlhost=' $fogsettings | cut -d \' -f2 )" if [[ $snmysqlhost != "" ]]; then hostIDs=$(mysql -s -h$snmysqlhost -u$snmysqluser -p$snmysqlpass -D fog -e "Select hostID from hosts") groupID=$(mysql -s -h$snmysqlhost -u$snmysqluser -p$snmysqlpass -D fog -e "Select groupID from groups where groupName = '$groupName'") for i in ${hostIDs[@]}; do mysql -s -h$snmysqlhost -u$snmysqluser -p$snmysqlpass -D fog -e "insert into groupMembers (gmHostID,gmGroupID) values (${i},$groupID)" done elif [[ $snmysqlpass != "" ]]; then hostIDs=$(mysql -s -u$snmysqluser -p$snmysqlpass -D fog -e "Select hostID from hosts") groupID=$(mysql -s -u$snmysqluser -p$snmysqlpass -D fog -e "Select groupID from groups where groupName = '$groupName'") for i in ${hostIDs[@]}; do mysql -s -u$snmysqluser -p$snmysqlpass -D fog -e "insert into groupMembers (gmHostID,gmGroupID) values (${i},$groupID)" done else hostIDs=$(mysql -s -D fog -e "Select hostID from hosts") groupID=$(mysql -s -D fog -e "Select groupID from groups where groupName = '$groupName'") for i in ${hostIDs[@]}; do mysql -s -D fog -e "insert into groupMembers (gmHostID,gmGroupID) values (${i},$groupID)" done fi
  • Update Kernel fog 1.2.0 to SVN kernel

    2
    0 Votes
    2 Posts
    2k Views
    george1421G

    Just as an FYI, the bzImage and bzImage32 are the kenrels, the inits are (roughly) the virtual hard drives for the FOS (client) image. In your case you need to use the inits for 1.2.0 and then the newer kernels (bzImage). Tom is saying this should work, but the best chance is to just upgrade to the trunk if just copying the bzImages doesn’t work for you.

98

Online

12.7k

Users

17.6k

Topics

156.8k

Posts