@george1421 Both are Debian 10 (buster) x86_64 GNU/Linux.
K
Best posts made by Kanja
-
RE: Interface not ready, waiting for it to come upposted in FOG Problems
-
RE: Interface not ready, waiting for it to come upposted in FOG Problems
Well, I feel stupid right now. I seemed to restart the services on the wrong server because when I restarted all the FOG services on both on my Node and Storage, the errors in the logs dissapeared. Even did a test multicast session, started imaging right away with WOL and PXE. So marking solved on my part.
Latest posts made by Kanja
-
RE: Interface not ready, waiting for it to come upposted in FOG Problems
Well, I feel stupid right now. I seemed to restart the services on the wrong server because when I restarted all the FOG services on both on my Node and Storage, the errors in the logs dissapeared. Even did a test multicast session, started imaging right away with WOL and PXE. So marking solved on my part.
-
RE: Interface not ready, waiting for it to come upposted in FOG Problems
@george1421 Both are Debian 10 (buster) x86_64 GNU/Linux.
-
RE: Interface not ready, waiting for it to come upposted in FOG Problems
Adding myself to the list as another victim. The same error appeared after upgrading to 1.5.8. Now at 1.5.8.5 (dev-branch) and the error is exactly the same as @lewisreid01 mentioned with no IP address in the end. I have 1 node and 1 storage where the separate storage is the master and only storage. Didn’t change my configuration file after upgrade.