Updated from .32 to 1.1.0 to 1.1.2 to 1.2.0 - User Login Hist page blank
-
[quote=“Wolfbane8653, post: 38547, member: 3362”]I would suggest you change your memory to 256mb should accelerate the page load and still accommodate your history file. I have 736 machines with 984 users. My report works fine with 256M.[/quote]
I upped mine to 1536M just to see. I still could not get my login history to load.
-
Just for clairification this is the file you changed right?
/etc/php5/apache2/php.ini
changed memory_limit = 256M
the restarted apache
RIGHT? -
Well I doubt it will fix the problem would you be willing to try persistent database connection rather than just create a new thread and connect to the database
-
If that is the only thing I should be modifying… yep. Just tried 256M for the fun of it. No dice.
[ATTACH=full]1470[/ATTACH]
[url=“/_imported_xf_attachments/1/1470_phpini.png?:”]phpini.png[/url]
-
[quote=“Tom Elliott, post: 38553, member: 7271”]Well I doubt it will fix the problem would you be willing to try persistent database connection rather than just create a new thread and connect to the database[/quote]
I’m willing to try anything, just let me know what I have to do.
-
The file /var/www/fog/lib/fog/Conffig.class.php
Change the database_host field so it states p:ip.of.fog.srv if it’s the local host try p:127.0.0.1
-
Current entry is:
define(‘DATABASE_HOST’, ‘localhost’);Changing to:
define(‘DATABASE_HOST’, ‘p:127.0.0.1’);Restarting FOG server…
No dice. Blank page…
-
[quote=“UpACreek, post: 38550, member: 24526”]I upped mine to 1536M just to see. I still could not get my login history to load. :([/quote]
I’ve tried the same. I run fog in a ESXi VM. It used to run on a total of 512mb ram and 1 cpu just fine, but trying to resolve this I’ve increased to 2gb ram and Dual CPU. I have 1.72 million records in my user tracking table, going back to the 12-31-2013. I used to have record back to 2011 I think but I purged those out, at least 4 million or so that I deleted.
Looking at the table I wonder if there is a way to ignore a user from the logs. We have a few automatic logon labs that restart frequently. I would like to keep tracking enabled on the machine to log any bypasses of the autologon, but for now I’m disabling tracking on those computers.
-
I’m taking a quick look at the way php and mysql is handled. It shouldn’t be a problem no matter the number of results, but php defaults to a buffered set which should only be used in a case were we must know the number of results or we know it’s going to be limited, unbuffered should allow much large return sets. I’m testing.
-
I’m game to try other ideas. Just let me know. We’re fumbling around quite a bit without this report. You don’t realize how important a feature is, until it suddenly isn’t available.
-
Take a look at the current svn.
You can update your memory_limit right in fog gui.
I’m also taking an approach to use MYSQLI_USE_RESULT for the results page to allow, hopefully, a better size in the variable that’s stored, though it’s not likely to fix all issues.
That said, you no longer need to, nor will it affect fog anymore, set the memory_limit in the php.ini file as it’s set in FOG and uses that value specifically. It defaults to 128 and will never go lower than that. Nice part is you don’t need to restart apache either for the changes to take effect.
-
I’ll give it a go. crosses fingers I’ll let you know.
-
Bummer… still a blank page after going to Login History.
Even tried changing the memory in the GUI to 1024, but still no dice. -
How large is your userTracking Table in mysql?
-
[quote=“Wolfbane8653, post: 38679, member: 3362”]How large is your userTracking Table in mysql?[/quote]
Login records span from 2012 to now, and there are ~614,000 records just in the login history table.
-
SVN 2705 released, should fix the memory problem for even the simplest of sortable data.
Alright,
SVN should contain the fix for this pressing problem. While I can’t fix huge lists and “Hosts and Users” will still be broken as it’s pulling all the data at once, it should work for all the other “timed” reports as my method was all screwed up. I had to add a new element to the find method to get it to work, but it seems to work properly now.
Basically (and you all can slap me if you want) as this wasn’t added before, my mechanism for sorting out the proper datasets was to pull the entire set of entries. This was/is where the problem exists. I’ve added a new feature to allow me to adjust the find parameter’s Compare element. Because of this, I can now test anything I want so long as I know the syntax. It’s intended purpose, for now, is to simply use BETWEEN ‘$date1’ AND ‘$date2’ calls, but it has potential for much more down the road.
Please test and let me know.
-
Thank you for your continued work on this! Will test after Thanksgiving. gobble gobble
Happy Thanksgiving everyone!
-
I’d love to report positive results… But…
Both ‘Login History’ and ‘Hosts and Users’ result in a blank page after updating to SVN 2721. FOG_MEMORY_LIMIT is set to 1024.
-
Or you simplifying the dates, or trying to grab all of them?
-
I can’t even do a dates query. I click on either link, and it blanks out. I don’t get to a page where it will even begin to allow me to specify a query.
