An issue was found in 1.5.6 that calls for an early next release to fix that. Find the details here if you run into problems with FTP connections on kernel updates or storage nodes in 1.5.6: https://github.com/FOGProject/fogproject/issues/311
@george1421 nevermind i found what i was looking for…this is all i wnated to do
FOG image queue size too small
By default, FOG unicast is set to image no more than 10 machines at a time. Other devices will be placed in a queue and wait for another machine to complete. If you want to increase this queue number, you have to do it in two places.
First, under Storage Management > Select your Default Member > Change the figure in Max Clients to the desired number.
Second, under FOG Settings > Expand General Settings > Change the figure in FOG_QUEUESIZE to the desired number.
I ran a Disk Surface Test (DST) and noticed that it sits at the “* Disk Surface test for /dev/sda” line with no status output. I researched online, found that the status is given at the end of the test, and that it automatically reboots, so I followed the instructions to force a keypress prior to the reboot.
This morning I came in, and the line quoted above finished with “…Done” and then the line below that was “* Task Complete” - no explicit confirmation of pass or fail. I suppose it could be following the Linux way of saying nothing if nothing went wrong?
Several people have commented in the past, and I agree with them - it would be nice to link the test results to the Reports section, as well as some field on the host somewhere, perhaps the top or bottom of the Inventory details (ex: Disk Surface Test: [Passed / Failed]).
@Tom-Elliott Ok, I understand. That’s a problem to me because all the server’s ip on the service vlan’s are protected. Then i must have the StorageNode on the Management VLAN.
By the moment i’ve solved the problem like i said on the last post. It’s a valid solution for me. But when i have time i try to implement a plugin to handle this dinamically from the interface.