Posts made by eliaspereira

@Tom-Elliott

Could you help with this problem?

Update post:

Last night I updated to version 1.5.10.1639, but this morning we sent some more tasks, 31 in total, and after finishing the first 10, it keeps waiting endlessly.

The strange thing is that all the machines in the queue say that there are, for example, 15 before me. Is that correct?

It shouldn’t be like that:

1. the first 10 start
2. The message on the 11th: “Are slots open, but 10 before me”?
3. The message on 12: “Are slots open, but 11 before me”?
   … and so on?

@tian same problem here!!!
https://forums.fogproject.org/topic/17815/deploy-tasks-not-continuing-after-first-batch

Hello,

I am experiencing an issue with deployment tasks in FOG. I have groups of hosts, for example, LAB02.

• I click on LAB02, go to the Basic Tasks tab, and select Deploy.
• I enable:
  Wake on LAN
  Schedule Instant
• I click the button to create the deployment tasks.
• In the Task Management menu, I see that the first 6 machines start deploying.
• However, once those 6 machines complete the deployment, no new machines start, even though the group has more hosts.

Troubleshooting steps I have tried:

• I checked Max Clients in the Storage Management, and it is set to 10.
• Restarted the services:

systemctl restart FOGImageReplicator FOGScheduler FOGSnapinReplicator

• Checked Task Management, but no new tasks are created automatically.
• Ensured that the PXE boot settings on the remaining machines are correct.

Additional notes:

• I noticed that the FOG_QUEUESIZE setting seems to have been removed in the latest version. Could this be related to the issue?
• Is there any way to force the queued machines to start once the first batch finishes?
• Am I missing any settings to allow the next hosts to start deployment after the first batch completes?

Any guidance on this would be greatly appreciated. Thanks!

---

You are not running the most current version of FOG!
You are currently running version: 1.5.10.1629
Latest stable version is 1.5.10.1639
Latest dev-branch version is 1.5.10.1639
Latest alpha-branch version is 1.6.0-beta.2166

@george1421 said in Host status is unknow 2:

@eliaspereira So does it work now that you fixed name resolution on the FOG server?

At first, yes.

Thanks again for the great help!!!

@george1421 said in Host status is unknow 2:

@eliaspereira OK, lets find out a bit more about your network setup.

1. What device is your dhcp server?

We use pfsense as firewall and dhcp server.

2. Can you resolve the computers by DNS?

Now, yes. I configured the samba4 AD DNS on resolv.conf from fogserver.

3. Are the host names registered in FOG match the physical host name on the target computer?

Yes.

@george1421 said in Host status is unknow 2:

@eliaspereira No fog is configured to only use the hostname because often the IP address is assigned by dhcp.

Ok.

How many computers are you trying to manage here?

Over 365 computers.

@george1421 said in Host status is unknow 2:

@eliaspereira Ok this issue is totally a name resolution issue based on the testing you have done so far.

FOG uses port 445 to query the target system.

So to start debugging this see if you can ping lab04pc02 If unable to resolve the name lab04pc02 (as named in the fog host definition) then that is your problem. Depending on the linux distro you use you need to use the network manager application to point the FOG Server’s DNS server value towards you internal DNS resolver. So that the FOG server can map lab04pc02 to an IP address.

Hello @george1421 , Thank you for your help!

Can I set fog to ping the IP address instead of the domain name?

hi,

I have searched the forum and found a few topics, but none of them solved the problem.

The logs show that everything is ok, but anyway, it still shows that the host is unknown.

Your version of FOG is up to date.
You're running the latest stable version: 1.5.9
Versões do kernel
bzImage Version: 5.10.71
bzImage32 Version: 5.10.71

ping

root@fogserver:/opt/fog/service/etc# ping 10.10.4.119
PING 10.10.4.119 (10.10.4.119) 56(84) bytes of data.
64 bytes from 10.10.4.119: icmp_seq=1 ttl=127 time=0.770 ms
64 bytes from 10.10.4.119: icmp_seq=2 ttl=127 time=0.796 ms
64 bytes from 10.10.4.119: icmp_seq=3 ttl=127 time=0.715 ms
64 bytes from 10.10.4.119: icmp_seq=4 ttl=127 time=0.770 ms
^C
--- 10.10.4.119 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.715/0.762/0.796/0.044 ms

telnet on 445 port

root@fogserver:/opt/fog/service/etc# telnet 10.10.4.119 445
Trying 10.10.4.119...
Connected to 10.10.4.119.
Escape character is '^]'.

tail on pinghost.log

root@fogserver:/opt/fog/service/etc# tail -f /opt/fog/log/pinghost.log 
[05-09-22 8:51:01 am]  * Attempting to ping 369 hosts
[05-09-22 8:51:01 am]  * All hosts updated
[05-09-22 8:56:01 am]  * FOG Web Host IP: 200.132.218.150
[05-09-22 8:56:01 am]  * This servers ip(s)
[05-09-22 8:56:01 am]  |	127.0.0.1
[05-09-22 8:56:01 am]  |	127.0.1.1
[05-09-22 8:56:01 am]  |	200.132.218.150
[05-09-22 8:56:01 am]  |	fogserver.sertao.ifrs.edu.br
[05-09-22 8:56:01 am]  * Attempting to ping 369 hosts
[05-09-22 8:56:01 am]  * All hosts updated

[05-09-22 9:01:01 am]  * FOG Web Host IP: 200.132.218.150
[05-09-22 9:01:01 am]  * This servers ip(s)
[05-09-22 9:01:01 am]  |	127.0.0.1
[05-09-22 9:01:01 am]  |	127.0.1.1
[05-09-22 9:01:01 am]  |	200.132.218.150
[05-09-22 9:01:01 am]  |	fogserver.sertao.ifrs.edu.br
[05-09-22 9:01:01 am]  * Attempting to ping 369 hosts
[05-09-22 9:01:01 am]  * All hosts updated

Any ideas?

@george1421 said in wake on lan not working:

The target computer must be on the same subnet as the FOG server

We work with vlans and the fogserver is in a different vlan from the vlans of the computer labs, which we want to activate the wol.

I created a rule in our pfsense allowing the fogserver to go to the labs’ vlans, but it didn’t work.

Is there any other way to make this work?

@george1421 said in wake on lan not working:

@eliaspereira Is pfsense your dhcp server? If yes it will work with FOG. I say this from memory so I might not have the exact menus, but in the dhcp server settings you need to enable netboot option. In that section there will be four boxes. One may be labeled next-server or boot server. That should be the IP address of the fog server. Then there are 3 fields. One for bios, that should be this value: undionly.kpxe one for 64 bit uefi: ipxe.efi and one for 32 bit uefi: i386/ipxe.efi Once that is set and you have net booting enabled you should be able to pxe boot into the FOG iPXE menu.

now if this is already configured correctly, make sure you turn off “Secure boot” in the pxe booting computer’s bios (firmware).

If all above fails, please give us a clear screen shot of the error taken with a mobile phone and post it here so we can see where it stops.

I think you misunderstood my question.

This configuration I already have and it works correctly.

My problem is with the wake on lan via fogserver.

hi,

I did all the configuration on the client machine and via wake on lan from pfsense, I can start the machine, but from fog, it doesn’t work.

Your version of FOG is up to date.
You're running the latest stable version: 1.5.9
Versões do kernel
bzImage Version: 5.10.71
bzImage32 Version: 5.10.71

Is there any extra configuration to be done?

@george1421

In Boot Exit settings menu I changed “Exit to Hard Disk Type” to GRUB.

Apparently it worked.

@george1421

If I change in BIOS or skip pxe boot, windows boots normally. I had already taken the test.

In which fog settings can we check?

hi,

I formatted a PC with windows 10 and when it boots from the network and falls into the fog options screen, I left the option “start from hard drive (HD)”, but after that, the pc is in a reboot loop and does not enter in the windows 10 installation.

In the bios the boot (legacy) is for:

1. nic
2. hd

fog version:

• 1.5.9
• bzImage Version: 4.19.145
• bzImage32 Version: 4.19.145

Any ideas or tips?

@george1421

It’s a dell or fogserver side known issue?

UPDATE POST:
Adapter: Intel 82579LM Gibabit Network Connection

Hello,

Dell Optiplex 9010
BIOS: A30
Windows 10

I configure dhcp options on pfsense as follow:

It even loads the file correctly at boot via UEFI, but stays in that message for a while and then restarts the computer.

Is this model compatible?

@wayne-workman

That’s exactly what I did. I wrote a shell script and put it in rc.local. It checks through the mac if the computer is in the fogserver database and from there it makes the change of hostname and join in our domain.

Thanks to all for your help!!!