Reinstalling Backing up Database Failed
-
@jackiejack from your second picture dnsmasq / what ever is working because the next server and boot file name is making to the client computer. what it looks like is its timing out trying to download the file. Is 192.168.1.39 the current IP address of your fog server?
-
@george1421 Yes, static
-
@jackiejack Then can you do this.
sudo netstat -an|grep 69this will see if the tftp server is running.ls -la /tftpboot/undi*to see if you have the boot files in the right spot -
@george1421 I will do those steps but now when I pxe boot vm it can’t see x.x.1.39
-
@george1421
udp listening on 693 files in undi*
-
@jackiejack This is an interesting puzzle.
you have a pxe booting client on the same subnet as the fog server that is getting a timeout trying to download undionly.kkpxe, yet the tftp service is running and we can assume undionly.kkpxe is listed in the /tftpboot directory.
If you have a working windows 7 or newer computer on the same subnet, install the tftp client feature on the windows computer. Then open a windows command prompt and try to get undionly.kkpxe using the tftp client program.
Just for my sanity, you did disable the firewall on that ubuntu server right?
-
@george1421 running centos - disabled firewalld and setenforce 0
I can get a windows 10 on the same subnet not windows 7
Now I am NOT getting contact with 1.39 when pxe boot on vm
-
@jackiejack Something weird:
on ubuntu
systemctl stop ufw
systemctl status ufw
inactivepxe vm and it got the fog menu. I was on the first line “boot from harddrive” for a split second and then it boot into windows.
I loaded up a snapshot (sysprepping) then pxe boot. Now not even finding 1.39.
Puzzle indeed
The time when the fog boot menu came up, it asked me just before for tftp server. So I put 192.168.1.39. Then it went to the fog menu (it was only up for a split second). An SELinux alert/denial thing came up on fog server
-
@jackiejack uploading my sysprepped image from vm! But it asks me for tftp server address. It not automatic.
-
@jackiejack deployed sysprepped image unto real host on private switch. dnsmasq looks like it’s working well with my home router.
Target went into OOBE.BUT pxe boot process asked for tftp server ip addr.
Target computer legacy boot and disable pxe boot in order to boot from hard drive. It didn’t seamlessly go to OOBE as soon as deployment tasked finished.Feelin good.
-
@jackiejack said in Reinstalling Backing up Database Failed:
BUT pxe boot process asked for tftp server ip addr.
If I remember correctly this can happen if both the normal DHCP (in your case the home router) and dnsmasq provide next-server information. So there is not much we can do about it. You’d need to change your DHCP setup to get rid of that issue. I’d say play with that stuff for a bit longer over Christmas and then see if you wanna change to a different DHCP server and toss dnsmasq altogether.
I am marking this solved now. Please open a new thread if you have any further questions or issues. Better to not discuss too many different things in one thread as it makes it very confusing for people who search the forums for answers to their questions.
-
@sebastian-roth Yeah, my supervisor is satisfied with the process. It is working. Thanks so much for your help guys!
