@m-fitzgerald Can we mark this solved?

@JGallo Interesting suggestion…

@wayne-workman That should be it

IP address The name of the new card as known by linux.

Fix the .fogsettings file and rerun the installer.

I might just look at the webgui in the fog configuration as well as the storage node settings for this fog server to ensure the name of the network interface matches what is now defined in linux.

Just throwing my 2 cents worth in because we also have 2 domains, but segmented networks with the exception of FOG talking over both networks. But that shouldn’t matter for this.

I have set up my primary domain information in FOG as a default. I then created Locations (Using the Location plugin) and host groups for each remote location. I then placed the machines into each of their respective host groups and applying the specifics there.

Once you have the machines you want on one domain placed into the host group for your Old domain, you can apply the AD information to that group allowing the Host that needs to remain on your Old domain to re-join it. You can do the same for the New domain as well.

Simply put: Create 2 Host Groups. “Old_Domain” and “New_Domain”. Place the hosts you want to keep on the old domain in the “Old_Domain” group and apply the AD information to that group. Then Place the hosts you want to be on the New Domain in the “New_Domain” group and apply the AD information to that group. Your hosts will stay on the domain you specified to each group.

Re: Can’t image from storage node
Not sure what happened but it seems to be working now. Well imaging from the storage node works when I tried it last week in another group of computers from a separate image that’s stored on the server. I saw the storage node IP on the client computer when imaging.
I have not touched or updated neither the main or node servers.
I have not tried to image from LABGEN from storage node. so 50% working from the main issue. Will follow up or capture a new iamge for LABGEN image soon.

thank you everyone!

@george1421 said in Uncompleted multicast:

This fix is interesting too.

$ sysctl -w net.core.rmem_max=16777216 $ sysctl -w net.core.rmem_default=16777216

rmem* changes helped when I was testing directly with udp-sender/receiver and when the received data was directed to /dev/null. Successful test deploy with 1 vCPU VM hosts (additional writing to the disk) that I mentioned in previous posts was with half-duplex mode which I forgot to change back to full-duplex. Full-duplex on Xen VM host is still problematic, high number of re-xmits and aborted multicast.

Xen servers’s internals switches are difficult to debug and I’m not sure where the packets are being dropped but there are some lost packets on Xen servers’s internal switches too. Xen VM booted in debug mode was still dropping RX packets too when full-duplex multicast was used. I’ll try to consult our Xen Server support to check settings on the Xen Servers. From few posts I have seen, Xen’s Open vSwitch has very small queues by default which could be a problem for UDP cast.

On the physical host, before changing rmem*, there were dropped packets on the Extreme switch on the port connected to the PC so my conclusion was that the problem was (mainly) on the receivers.

In my environment, I think I’ll stick to half-duplex mode which allows receivers to sync more often so that buffers are not maxed out. I did not find another udp-sender parameter which would allow control of how many packets are sent without the confirmation from the receiver.

After creating the /home/fog directory, run the mkdir /home/fog
chmod 755 /home/fog
chown fog: fog /home/fog
and fix the FTP passwords, everything went back online.
Thanks Sebastian

@sjensen said in Selected boot device failed:

So basically i need to try the different bios setups combined with the different binaries in order to capture an Image of this Dell XPS13?

As I said, it’s probably a lot easier than debugging why undionly.kpxe doesn’t work at all and undionly.kkpxe has transfer issues…

So it’s all about the combination of Laptop, firmware and USB dongle. Here is a forum thread where someone was able to PXE boot in BIOS legacy (undionly.kpxe) with a USB dongle also based on the RTL8153 network chip. But as I said, it’s always a bit different as soon as you change one component in the equation.

And here Dell is saying that “The XPS 13 with BIOS A05 or higher, supports PXE boot with LAN7500 chipset based USB NICs.”

Just want to show you that there are many different ways and people were able to PXE boot the XPS13 but you can only know for sure when you test with the components you have at hand.

Edit: Hope this is not causing too much confusion. Just wanted to show you that there are different solutions out there and trying to do plain UEFI might be the easiest one or at least worth a try. Here is a thread where the same issue as yours is described and was solved by switching to UEFI.

I found the mistake. The service configuration of FOG contained the fully qualified name as hostname. I replaced it with the IP address and it worked and the menu looked different too.

@dsloan-ethra So just to recap what was done here to adjust Debian 9 (where the referenced article also implies it is an issue for any Debian variant like Ubuntu) for others that might find the thread:

Edit /etc/mysql/mysql.conf.d/mysqld.cnf
vi /etc/mysql/mysql.conf.d/mysqld.cnf Insert the following line in the [mysqld] section
max_connections = 8000 Copy the systemd service descriptor file so you can customize it
cp /lib/systemd/system/mysql.service /etc/systemd/system/ Append the following lines to this file: /etc/systemd/system/mysql.service LimitNOFILE=infinity LimitMEMLOCK=infinity Reload systemd processor
systemctl daemon-reload Reload the mysql service
systemctl restart mysqld Login to mysql as root and run the following command.
mysql> show variables like 'max_connections'; The response should be something like +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 8000 | +-----------------+-------+ 1 row in set (0.01 sec) Done.

These are not my words, only restated from the accepted solution here that Sebastian found and referenced: https://www.rfc3092.net/2017/06/mysql-max_connections-limited-to-214-on-ubuntu-foo/

I was also facing the same problem from a long time and I was not getting any solution for this.
But after visiting this forum, I get my questions solved, answers shared in this forum are very good and very easy to implement.

[Moderator’s note: removed link to commercial website]

@NatLanis Have you deployed that image to a machine yet?

@greventlv said in How do I FOG my FOG server?:

I know that’s something that I can do, but I have a bunch of other stuff on the server and during production breakdowns, it would be a lot faster to hit a few buttons and get everything back to the original state without having to deal with a new install, restore and etc.

Then really you should build a fog server in a VM and just snapshot it. That’s literally ‘a single button click’ to restore from a past state.

@m-fitzgerald Good to hear this fixed the issue for you. Though from my point of view it’s only partly solved. If you capture the image again you will need to edit that file again. So question remains why it does not recognize your boot partition as such. Usually this happens if Windows is not installed as English version or partition labels have been modified by hand. As I said, take a screen shot of the disk management view in Windows and post here. I am fairly sure we can figure out why that is.

Follow on question though. How do I edit the order of Storage Nodes?

We try to keep topics separate. Please open a new thread for this! Won’t answer here.

Okay so I finally figured out the issue. Whenever this error came up the storage didn’t show up on the main page. Once I was able to get the storage node figured out and the pie chart came up on the main page I was able to create a snapin just fine.

@george1421 GEORGE THANK YOU SO MUCH!!! YOU HELPED SO MUCH

If there are not important files on the hard drive, you can repartition it. During partitioning a hard disk, you can select partition table type, partition numbers, sizes, etc. After that, you’ll be able to get a valid partition table. If you do not try repartitioning, you can try rebuilding MBR using an installation disc. You can refer steps here to rebuild MBR manually:eassos.com/how-to/how-to-fix-invalid-partition-table.php

Thanks Sebastian,

I have read it a while ago, but looks like I missed your edits…
Unfortunately I just lost access to these servers just now as I moved a company (last day), as a workaround, we just changed the bios to boot from local hard drive after we fogged them.

Thanks for your help,

Aviram

Thanks Guys, I can confirm its working now.

Aviram