1.6 Issues/Reporting
-
@tom-elliott No worries, just trying to contribute
Thanks for the response! Hope things are working out for you. -
I love the look and feel of the new interface. I can tell you and the group have put in a ton of effort in creating 1.6. Thank you!
One small thing I just noticed is the icon on the browser tab needs to be updated. Ha! I liked having the FOG icon to get to in my many open tabs. Small!
The next thing I noticed was when you open Groups/Associations/Hosts, it displays All hosts. It would be great if it showed just the hosts associated with the group with the option to display hosts that are not associated with the group. (like 1.5 did.)
I’ll put it to the test!
Again thanks!!
Cheers!
-
@joe-gill I could change the group host by sorting by the association field. The idea here for all things is to kind of be “less” is more of that makes sense. I’ll work to sort first by associated.
-
I agree. Less is more here. I like the idea of sort by associated first. That would certainly work.
Have you tested Multicast? I am testing that now. I get Attempted to check in failed.
Thanks!
-
@joe-gill We need more tabs!!!
-
@joe-gill what’s the error you’re seeing in apache?
-
/var/log/apache2/error.log?
What I am seeing is this… Yet I have tasks listed in tasks…
-
Found the issue through a remote session.
The problem was I forgot to add MULTICAST tasks to the Deploy grouping. Once added, hosts started checking in and even started imaging YAY!.
Found another issue in regards to the unisearch and non https. Hopefully this is all corrected for now too.
Associated items are also now sorted in a “Associated, Name” method as opposed to just “Name” as it was before.
-
One other feature that would be nice is when you check / un-check hosts from certain things, for instance groups, that it would recognize that as selecting the item. Right now you have to highlight the whole thing to select it.
Thanks!
-
@joe-gill I’m aware of this. The functionality idea, however:
Individual checkboxes work only on that one element. Selected items work “en mass”. I just haven’t gotten around to making that function appropriately yet.
-
No problem! I’ll keep that in mind. I’m testing multicasting now.
I discovered a few things that could have been effecting multicasting performance. If this works, I’ll have to unicast most of the lab. Basically, we have some small low end consumer switches that some of these hosts are plugged in to. I had 4 hosts in that lab that are directly wired in to our smart switches (cisco). We did check to see if we had any packet loss during the previous multicast session and we did not and the cable checked out fine. So we’ll see.
-
Favicon icon is missing (although you may have known that since it’s in working)
-
@tom-elliott Hi Tom, memory_limit, post_max_size and upload_max_filesize are all at 1900M in php.ini. But one of these 3 values were at 0 on fog interface with new 1.6 (I don’t remenber which one and forced it to 1900 in FOG web interface as in php.ini didn’t change my snapin problem)
Thanks and once again , you’re doing great job
Matthieu -
@matthieu-jacquart are the snapins 1900M or smaller?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@tom-elliott nop, very much smaller, I tried to create a powershell script snapshot…
But even tried to update existing snapshot (few MB) didn’t change anything (snapin file in opt/fog/ is not updated) -
@matthieu-jacquart then I think it’s safe to say, for right now at least, uploading weapons isn’t working. This isn’t surprising to me though I will work to get it fixed as soon as I can.
-
@Tom-Elliott So far everything that we have thrown at 1.6 as far as functionality wise is going well so far. I have noticed that at times the disk activity becomes abnormally active and causes the CPU % to get at 100. I had set CPU cores to 2 so i gave it two more and now up to 4. Granted I haven’t ran a git pull since I first installed it but running that now. I don’t have any storage nodes defined yet and I know there is no active tasks when this is occurring. Any thoughts what would cause this? I rebooted server and as soon as it comes back 100% again on CPU and disk i/o active. FYI this VM is also on a Hyper-V host that also has a production fog server that is working fine. I don’t think it’s a HD but could be related to my VHD. Thanks.
-
This post is deleted! -
@Tom-Elliott
I can’t seem to get 1.6 to do a Wipe task. It will PXE boot the host but it never creates the task. -
@Tom-Elliott OK something to notate. So I did confirm with my coworkers that they are indeed imaging but on the tasks page they do not show up as actually imaging. This would explain why I noticed HD I/O spiking as well as the outbound on the NIC lol but strangely they are using a separate account I created in the FOG web UI. Maybe any other account than FOG doesn’t display the activity and hosts that have been registered under that account. I found this to be weird because it was working before and we have a project imaging 100 computers but we have probably only imaged about 25 and this is when it started happening. Hopefully this makes sense.
