Tasks show up.
Setting a check mark to select all active tasks doesn’t work.
Posts made by mp12
-
RE: build 7142 Task Management broken
-
RE: Dashboard free slots
I have configured two nodes with 5 max. clients. The result should be 10 free slots in the dashboard.
But the dashboard only shows 5 free slots.
When the nodes have unequal number max. clients (e.g. 4 and 5) the free slots where sum up correctly. -
RE: build 7142 Task Management broken
Same problem in scheduled tasks.
Having two active scheduled tasks. None of them is displayed.
-
RE: Dashboard free slots
Ubuntu 14.04, FOG r7142
Problem occurs in above version.
-
Report Managment > Imaging Log
fog r6885
When I search for entries in the imaging log I get the following output plus the list of imaged computers.
Strict Standards: Only variables should be passed by reference in /var/www/fog/lib/fog/fogcontroller.class.php on line 284
-
RE: not possible to edit snapin
@Tom-Elliott same problem. Double checked passwords.
Using WinSCP as ftp client connection to ftp works and I can see the snapins.
Using Linux cmdline the ftp server redirects me to the users home directory.fog r6809
Here the error I get when trying to edit snapins in browser.
[Fri Mar 18 13:41:20.467648 2016] [:error] [pid 16486] [client x.x.x.x:60355] PHP Fatal error: Call to a member function chdir() on null in /var/www/fog/lib/fog/fogbase.class.php on line 73
-
RE: Deploy (Unicast): Wrong number of client per node.
@Wayne-Workman said:
I am working with the location plugin now. The splitting works fine. -
RE: Deploy (Unicast): Wrong number of client per node.
@Tom-Elliott for me a correct splitting (using more then one node) would be, the client connects to a node and the node checks if “max_clients” is exceeded. Then the node only replys to its configured number of “max_clients”. The rest gets queued.
Maybe I will give multicast another shot.
-
RE: Deploy (Unicast): Wrong number of client per node.
@Wayne-Workman first of all I am very thankful.
I am using FOG now for six-seven years. It’s a wonderful piece of software. Sure I want to help make FOG better. Thats why I am testing all these different configurations.
My only problem is that the imaging now takes twice the time.
I can handle this but I think a correct splitting would be great for the whole community. -
RE: Deploy (Unicast): Wrong number of client per node.
Yes they do.
When I start single deploys with one client and a delay of 10 seconds between, everything works fine. Group deploys won’t work without the splitting error.
-
RE: Deploy (Unicast): Wrong number of client per node.
@Tom-Elliott said:
@mp12 do all 5 systems actually start receiving the image, or does only three receive the image, and the other 2 wait in line?
They all recieved the image at the same time. Yesterday I ran 4 Clients on node1. No split between both nodes.
See, splitting between multiple nodes is not a straightforward thing. You can still queue many systems to receive an image.
I see splitting is not as easy as I thought
Just remembered in fog 0.32 I never had problems with the splitting.Now I am running another test with the same node config as before.
Started four group deploy (unicast) where each group has two clients.
Between each group deploy there is a delay of some minutes. I thought that the clients now can find a proper node.
In my “Active Tasks” I see eight tasks (six of them are running and two are queued). So far so good.When I log into the shell of both nodes I see:
node1: six connected clients receiving images via nfs.
node2: zero clients. -
RE: Deploy (Unicast): Wrong number of client per node.
Yes 100% sure. Just did an upgrade when I read your post from yesterday.
I will test with two and four clients tomorrow. -
RE: Deploy (Unicast): Wrong number of client per node.
No multicast!
Just a normal deploy “type=1” -
RE: Deploy (Unicast): Wrong number of client per node.
I am running a instant group deploy (basic tasks). The group has six clients.
-
RE: Deploy (Unicast): Wrong number of client per node.
FOG r6439
Still having problems.
node1 max client: 3
node2 max client: 3
number of clients in the deployed group: 6–> node1 deploys five clients.
–> node2 deploys zero clients.
–> one client is queued. -
RE: Bug with SNAPIN
@Tom-Elliott also having some “Ghostsnapins”.
I could replicate the error by creating a snapin, add the snapin to a host and then delete the snapin by marking the checkbox and push “delete all selected snapins?”
It seems that the snapin is deleted but still associated to the host (mysql table snapinAssoc). I removed the row in the table snapinAssoc and it’s done.By the way. The delete button next to the edit button seems to work fine.
-
FOG Imaging Log
Ubuntu 14.04, FOG r6315
In my “FOG Imaging Log” each deploy has a duration of 1 minute and 1 second.
In my case a normal deploy takes around 20 - 30min.
-
RE: Snapins ftp failed error
@theWizard try removing special characters and try again.