Posts made by AndrewG78

@Sebastian-Roth
I think I found the reason(s).
There are 3 things I would like to clarify.
1.
Although replication services are disabled, there is still some replication done between storage groups.
In my case, I have two storage groups, every group has one storage node.
Both Nodes were master ones.
The image from the new group(2) was replicated to the old default group(1).
I have unchecked replicate checkbox in the image, and also disabled Master Node for the old default group. So there is only one master node. The old group has no master node at all.
After this, all seems to be fine now.
a)
The question is, was this a proper behaviour?
I thought replication is done only within the storage group members(nodes).
b)
Are there any other services that could do this replication?


2.
The high cpu load(kworker and vsftpd) was related to replication and lack of disk space. Replication processes did not stop even if there was 0% of free space.
I think this is a bug.
3.
I can see a bunch of multicast log files.
a)
Should there be some smarter log rotation ?
b)
"No new tasks found "is logged every 10s - Can we change this time somehow ?

@Sebastian-Roth
So after disabling replication services, FOG UI became super responsive.
No more kworkers and vsftps deamons.
Perhaps an issue in the newest version?
Does anyone have similar setup and can confirm this bad behaviour ?

@Sebastian-Roth
Thx for the update. Yes I have read this before I started.
I have updated my node to the FOG server version at the same time, but I did not stop the replication.
I’m not sure if this scenario is realted to my setup.
I have two separate starge groups with only one master node in each of these groups.
So there are no nodes in the groups in which Master would replicate.
I will disable FOGImageReplicator and FOGSnapinReplicator on the server, but Im not sure if this is the right way to solve the issue.

Hi,
I recently added server master node(as a new storage group) to the fog server and upgraded FOG from 1.5.4 to 1.5.7. I have high CPU load 80% of the time, even if there are no any tasks to do. There are two vsftpd daemons consuming 20% of the CPU + kworker from time to time. How can I debug this ?

@Sebastian-Roth @george1421
Hi.
After quite a long time, I found free time to test filtering through the mac table configuration file.
It is working!!! Thx for the tips here.
However, I’d like to understand strange dnsmasq logs I noticed in the messages.

1. There are several identical broadcast responses.
2. There is tftpd error - Error code 8: User aborted the transfer
   Beside of above, it works

available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
PXE(ens160) <MAC> proxy
tags: team1, ens160
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
PXE(ens160) <MAC> proxy
tags: team1, ens160
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
PXE(ens160) <MAC> proxy
tags: team1, ens160
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
PXE(ens160) <MAC> proxy
tags: team1, ens160
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003016
PXE(ens160) <MAC> proxy
tags: team1, ens160
bootfile name: ipxe.efi
server name: <IP>
next server: <IP>
sent size:  1 option: 53 message-type  5
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
in.tftpd[27886]: Error code 8: User aborted the transfer
in.tftpd[27887]: Client <machine_IP>finished ipxe.efi
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
PXE(ens160) <MAC> proxy
tags: ipxe, team1, ens160
bootfile name: filenotneeded
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
PXE(ens160) <MAC> proxy
tags: ipxe, team1, ens160
bootfile name: filenotneeded
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
PXE(ens160) <MAC> proxy
tags: ipxe, team1, ens160
bootfile name: filenotneeded
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
PXE(ens160) <MAC> proxy
tags: ipxe, team1, ens160
bootfile name: filenotneeded
next server: <IP>
broadcast response
sent size:  1 option: 53 message-type  2
sent size:  4 option: 54 server-identifier  <IP>
sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
sent size: 17 option: 97 client-machine-id  
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
available DHCP subnet: <IP>/255.255.255.0
vendor class: PXEClient:Arch:00007:UNDI:003010
user class: iPXE
localhost in.tftpd[27997]: Client <machine_IP>finished default.ipxe

@Sebastian-Roth
Gr8 news. Thx a lot

@george1421 @Sebastian-Roth
Thank you for your valuable input. My idea is to separate not only the hosts but also snapins/images/literally everything. What I want to achieve is to have dedicated Fog server per team. The process of MAC address separation must be fully automatic.
I will develop the script that will:

1. Query database for hosts in the 60s loop
2. Write MAC list to temp_mac file.
3. If there is no amac_table.conf file, write temp_mac file as amac_table.conf
4. If amac_table.conf exists, do diff on these files
5. If files are same, do nothing
6. If files differ, copy temp_mac over the amac_table.conf and restart dnsmasq service.
   My only concern is, how to tell dnsmasq to read this particular file and how data should be formatted inside this MAC conf file?
   May you shed some light on it ?
   Obviously I will share my work here.

@Sebastian-Roth
HI. Thanks for this.
Looks very promising. Will tests this method soon.

@Sebastian-Roth said in Multiple FOG servers in one network:

Why using dnsmasq anyway? What DHCP server do you have right now that cannot be modified to do PXE boot?

I have no access to DHCP server. Company’s policy.

@Wayne-Workman
@george1421
Would this be possible to use dnsmasq as a MAC address filter?
I imagine this kind of setup:

• Existing dhcp server in the network
• Fog server 1 with dnsmasq
• Fog server X with dnsmasq
  dnsmasq will respond with dhcp offer as it does right now, but only to the machines included on MAC address list.
  Simple query to FOG’s mysql will get registered hosts from DB and update the list automatically.
  If this is not possible with dnsmasq I thought iptables could be used instead?
  Obviously, we will lost the ability to register new machines from the FOG boot menu.

@Sebastian-Roth
Are there any news regarding refind_ia32.efi? Will this 32 bit version of refind be included in the FOG installer ?

@Sebastian-Roth
1.
This is a very new idea. Did not have chance to test wimlib yet. Next week will do so for sure.
I have Samba NAS , will try with centos.
2.
Another interesting wim usage scenario:
WIM keeps in the A-image base Windows + B-snaphot with drivers + C-snaphot with sql server.
And you decide what you want to restore after the Base. So for a host1 u have A+B. For host2 A+B+C.
Instead of 3 images you must keep only one image +2 deltas.

@george1421
Thank you for your input.
1.
Format is opened to anyone.
https://www.microsoft.com/en-us/download/details.aspx?id=13096
Microsoft says:
This paper defines the internal format of a Windows Imaging (WIM) file format. This information may be used to build .wim file creation or extraction tools, or other WIM-enabled applications.
2.
Wim is not for backuping only. From wimlib site "
imlib can be used to back up, install, or restore Windows operating systems; to create customized images of Windows PE; or to archive files on either Windows or UNIX/Linux.
"
3.
Although I’m a java guy I could take a look on wimlib integration. Could anyone point me out where to start?

@Joe-Schmitt @george1421
I’d like to mention here, that WIM is something more the just another imaging format.
It could be used to provide something like snapshoting. I remember people were asking on this forum for backup feature. From wimlib site - WIM allows storing multiple “images” in a single archive, automatically deduplicates all file contents.
It means we capture base image, and then after some changes to the system, second capture will store only the Delta to the base image. Images are kept inside single wim file, so we can call a given image through its index.
I can see wimlib project is actively developed(11.2018).
Is there any chance to have WIM supported in ver 1.x?

@Sebastian-Roth
OK, I have re-downloaded 1.5.5 binaries and have NO errors, so my conclusion was wrong- new 32bit init and kernel are OK.
So, the question in my mind is, how did it happen?
I try to recreate events from the memory.
During first installation I had an error, saying that Installer is not able to unzip binary files. I found that the zip had wrong size, so I removed it by hand and started the installation again and it was succeeded this time.
So, I suspect that the installer only checks if the files exist, but does not check if the checksums match.
I know it is to much works with md5sum, so I think all files should be overwritten(except configs) every time I run the installer.
What do you think?

@george1421
Hi George,
Puzzle is solved now
Unfortunately version 1.5.5 has some issue /bug with 32bit version of init and kernel files.
I have manually downloaded binaries1.5.4.zip and overwrote bzImage32 and init_32.xz in the ipxe folder and all is working fine!!!
Could anyone check it and confirm my words?

@george1421
Hi, I have another puzzle to solve
I had to run FOG server on another hardware. I obviously ran nmtui-edit and updateIP.sh community script.
And this time I have in logs
in.tftpd[12096] Error code 8. User aborted the transfer
in.tftpd[12097] Client 192.168.1.18 finished i386-efi/ipxe.efi

and Tablet freezes on this screen

@george1421
It works now.
Im not sure what was that.
I have updated centos through the yum update
Then it did not even load fog interface on 192.168.1.1/fog but on localhost/fog only.
So I have installed FOG again like an update, it has finished with an error “DB backup failed”
But, surprisingly all works correctly now.
Thx again for your time,
I think something was not up to date in the system, but why did it work with regular laptop but didn’t with the tablet? Strange a bit.

@george1421
Hi.
I have new FOG server with the newest 1.5.5 version(centos 7 ), but this time acting as a DHCP server(no dnsmasq anymore).
It works fine with regular laptop, but again on this Tablet I got strange tftp behavior.
I have checked tftp from windows machine and this file could be downloaded with no issues.
But on the tablet I got:

There is nothing in the /var/log/messages

Thank You @Wayne-Workman . We can close this topic.
I have also found this link explaining how to incorporate GPL-covered software in the proprietary system.
Maybe someone will find it useful
https://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem