Topics created by pmonstad

@sebastian-roth There seems to be an issue with php-fpm and apache on Centos 6.9. For now the quick fix is to disable the link between php-fpm and apache to return php control back to apache. ref: https://forums.fogproject.org/topic/11722/problem-during-upgrade-from-1-5-0-to-1-5-2/18

If you do the add host to a group element, as soon as you press the “process changes” button, and scroll back to the top of the page, I’ll bet you see the “Loader bar” telling you “Group created successfully” or something similar.

The loader is only present for 5 seconds.

The idea of the move to ajax in case you must ask is so you could process many hosts in one sitting area rather than have to recycle the load time every time you click process changes.

I fail to see how this is a bug. This has been the case since 1.3.0 was released and discussed on numerous occasions.

I feel I need to add this, so people stumbling across the post understand.

The UNIQUE key for the hostMAC table is one key with two columns (hmMAC, hmHostID). Basically this means, a MAC cannot exist multiple times for the SAME host, but they can appear multiple times for different hosts. The idea is to allow the mac’s to show up with the hosts they reside in, but when it comes to identifying a host based on the MAC address, this becomes much more of a “no man’s land”.

This, we hope, will not be the case for much longer. One, MAC Addresses can be spoofed (and the same mac can exist on different machines even) so we’ve kind of lost the MAC Address as a unique identifier for a host. It probably doesn’t help that it’s not uncommon for a Laptop to have 2 or 3 MAC Addresses on it. Image an organization with only 1000 laptops. That’s potentially 2000 to 3000 MAC Addresses. Now I realize the unique identifier number is extremely high (each manufacturer has a potential of 16,777,215 addresses available) but as you see you can have the same mac address on multiple systems, it’s not very good for the hometeam.

It is uncommon to see the error itself, but when it has come up it’s usually because of a VM or TUNNEL adapter that is embedded as a part of the image. This, more or less, is where the pending filter comes in though.

While this field was, I think, only intended to filter any incoming “pending” mac addresses, it really should be applied to any mac address and it has been made to do exactly that.

@Tom-Elliott typing error, Now it works. Client updated to 0.11.5 a few second after installing svn.

Running very latest svn 5829, client 0.11.2 on Win 7 32 bits. Framework 4.0.

Works again after updating to svn 7713

@pmonstad It won’t hurt to reset all the hosts, even if they are not having the issue.

@Quazz True, I didn’t look up part numbers, just trying to understand.

Guess I’m trying to see if it ALL hdd’s of the same part number or maybe just a bad batch of HDD’s that were created, or something on the drives is actually stopping things from happening.

@Tom-Elliott running r6815 now.

Creating and editing snapins works fine now.

Thanks!

@pmonstad https://forums.fogproject.org/topic/6738/not-possible-to-delete-active-tasks/2#

It clearly says all tasks were active tasks. Which is it?

@Sebastian-Roth I’m marking it as solved. I cannot replicate.

I set multiple systems up for ONLY All Snapin Tasks.

@Sebastian-Roth I see. A coincidence this was the IP address of my old server, so that is the reason I asked.

I’m fairly sure this is fixed. Could use confirmation though, but i’ve not been seeing an issue for quite some time.

This has been sorted out in latest svn 6018. Thanks!

Fix pushed, i confirmed and fixed it. Please update.

I’ve solved this thread as I’m limited to cell phone. If somebody could move this to a more appropriate area it’d be much appreciated. This issue is not a bug. This is more like a feature request buys it not one in going to add. It’s simple enough sure, but can also be accomplished using a hook and/or plugin.

@Tom-Elliott Now it works as expected. Thanks!

I think I had this problem with fog 0.32 also. Does fog stay logged in when you let a tab with the logged in fog home screen (with the graphs) run all the time and open new/other tabs for working with fog? (Didn’t monitor fog 1.2 and svn versions for this problem yet)