@Sebastian-Roth Sorry, I completely forgot about this. Just updated to latest kernel on my server and tested on 1803, worked perfect. Thanks for the update.

@Sebastian-Roth I tried imaging and it works! Thanks for all of the work you guys do!

@Wayne-Workman Here is an updated working centos boot code that works for using your own downloaded repo as well as the online repo. I downloaded my own repo using command <wget -r -l 0 ./LOCAL-DIR WEBSITE-URL> in Ubuntu. once downloaded I then copied the repo from my home directory to the /bootimgs folder. I then modified the boot code originally provided by @george1421 from: :centos initrd http://${fog-ip}/bootimgs/centos/images/pxeboot/initrd.img chain http://${fog-ip}/bootimgs/centos/images/pxeboot/vmlinuz initrd=initrd.img method=http://${fog-ip}/bootimgs/centos/ devfs=nomount ip=dhcp boot || goto MENU to initrd http://${fog-ip}/bootimgs/centos/images/pxeboot/initrd.img chain http://${fog-ip}/bootimgs/centos/images/pxeboot/vmlinuz initrd=initrd.img root=live:http://${fog-ip}/bootimgs/centos/LiveOS/squashfs.img ip=dhcp repo=http://192.168.1.109/bootimgs/centosrepo/mirror.nodeshosting.com/centos/7.2.1511/os/x86_64 splash quiet – || read void boot || goto MENU the end result is that now I have my own home repo that works even if my machine is not connected to the internet. I assume this is good for corporate or environments where the admin is not wanting to use much data from or restrict the net. it also makes short work of the install time. I hope this makes someone’s life a bit more easier

@tom-elliott :D It works perfectly now Problem: image task not going to completion, getting error could not complete tasking /bin/fog.upload on host Solution: configure password - fog user account, tftp in fog settings and storage node - to match that in .fogsettings file https://forums.fogproject.org/topic/10892/could-not-complete-tasking-bin-fog-upload/2 AND configure SELinux policy (CentOS/Red Hat) To make it permissive all the time: https://wiki.fogproject.org/wiki/index.php?title=Fedora_25_Server#Continue_pre-config Particularly the two lines dealing with SELinux.

we have moved to partclone for compatibility reasons. you do not want to use partimage for new images.

Good news, I have my 1.2.0 Fog server up again. After building my own ipxe kernel most of my machines can pxe boot properly. I used the bios and uefi @Sebastian-Roth made in that post and both seem to work. Its not asking me for the tftp IP any more and just registered/imaged/deplayed a few machines :D

@wayne-workman Very true but making the change in the live DB is a great plan B until a long term plan A is found. I checked the mysql mem calc link and I compared the mysqld.cnf settings for those calculations but many of those variables are not there. I think at this point it works and I don’t foresee needing many more storage nodes in the future for this fog server. I’m happy it’s working now. Thank you both for all your help.

@george1421 Thanks for all your help on this. Next time I will make sure I am running the same branch.

Finally got a chance to get back to this! Setting the usb nic flag doesn’t make a difference.

@BedCruncher said in Multicast Issues on Centos 7: @Wayne-Workman Using one of the links, can’t remember which. I was able to get the server and client to send using the udp-sender and udp-receiver. So I know they can talk, but I had to use the command. udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 32 --nopointopoint --interface em2 if I dropped the last bit off then it would still try to grab em1 instead of em2. An example now exists in two different places in the wiki. I want to merge the articles but it will be an involved process to do that - I’ll get it done. For now, here are the two articles: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast 2. https://wiki.fogproject.org/wiki/index.php?title=Multicast

@cojohnson said in FOG Registration Error. Hostname with that name already exists: It renamed and started working properly after i reset encryption data. However, I have had to do that every time This time isn’t the same if you followed what I asked, because you said you previously had to press the reset button twice, I asked you to press it once.

@Tom-Elliott clearly i have posted this in the wrong thread :0

Thanks Tom S

@Sebastian-Roth I will try this in about ten days when we are back in session. Thanks!!

@Joe-Schmitt Yep I had bat for some reason…No idea how because I used to have.cmd

@george1421 The image transfer is complete! I had to touch the .mntcheck file to the /images and /images/dev directory. But other than that, I’m up and rolling again! Woo Whooo! I can’t wait to start fresh with Debian and clean up my server a bit. That’ll be next month’s project!! Thanks everyone who’s contributed!! I appreciate all the advice! :D Cheers, Joe Gill Townsend K-12 Schools

[SIZE=6][B]newbie here[/B][/SIZE] [SIZE=6][B]How do i change the fog server ip in 1.2.0?[/B][/SIZE]

It was not a problem of Timeout FTP…But it doesn’t matter, i can do cp -a /images/dev/@MAC /images/name :) [QUOTE]What user does the FreeNAS use? [/QUOTE] I’m only one user of FreeNAS The download is ok to the new client. I will write the tutorial ! :)

We were able to get the stuff figured out. YAY! The connection is now operational. FOG Interface displays properly.