Posts made by UpACreek

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.

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=“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.

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=“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 utilized the database backup option located under Fog Configuration > Configuration Save and it dropped a 43mb sql file. Login records span from 2012 to now, and there are ~614,000 records just in the login history table.

Thank you for the info.

I’m running Ubuntu 12.04 with 2gb of RAM. I switched the memory amount from 128mb to 1024mb, and attempted the report again. This time, it acted like it was going to do the report, as it sat there processing the request for close to 10 seconds, but then ultimately displayed a blank page.

I’ve got 466 hosts on this box, that track over 500 users on a daily basis. I’m guessing my login report is huge…

Apologies if I was supposed to put this in a bug report in another section.

[quote=“John Sartoris, post: 38526, member: 24837”]Any update on this? Version 1.2 released before this issue and is still current . We used to frequently use this report and are now stuck with less reliable methods.[/quote]

Somehow I missed that there were previous replies. I have not received any information on a fix, but am tempted to pursue the memory issue just to see if that does anything. I’ll see what happens…

Thank you for the information. I look forward to the upcoming updates.

xxxxx@LHSfog:/var/www/fog/management/reports$ ls
Hosts and Users.php User Login Hist.php

The User Login Hist.php was copied from the .32 installation folder.

The User Login Hist link has not worked since my first update from .32
lhsfog/fog/management/index.php?node=report&sub=user-track shows a blank page.

The Apache error log shows the following:

[CODE][Fri Aug 01 11:16:07 2014] [error] [client 192.168.11.17] PHP Warning: require_once(./lib/ReportMaker.class.php): failed to open stream: No such file or directory in /var/www/fog/management/reports/User Login Hist.php on line 26, referer: http://lhsfog/fog/management/index.php?node=report
[Fri Aug 01 11:16:07 2014] [error] [client 192.168.11.17] PHP Fatal error: require_once(): Failed opening required ‘./lib/ReportMaker.class.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/management/reports/User Login Hist.php on line 26, referer: http://lhsfog/fog/management/index.php?node=report[/CODE]

On a whim, I copied the user login hist.php from .32 into /var/www/fog/management/reports/User Login Hist.php but that didn’t seem to do anything.

Help??

Thank you for your quick response. Problem solved once again.

I went to do this on a newly installed 1.2.0 server. The option under fog settings general for legacy is no longer present. Is this still an option?

Thank you.

Thank you for the information. I did a 3rd option not realizing that you had responded. I re-copied the image from backup to the server, and it worked ok. I did not verify or check the image path prior to doing this. It could well be that the path got a bit mixed up. Regardless, the test worked.

Now onto doing the upgrade on the production server! I’ll keep your information for any other ‘uh oh’ situations I might have.
Thanks!

[LIST]
[]Built a .32 test server.
[]Did a usb sneakernet of two .32 images from a known working server.
[]Did a Full inventory on an ‘unknown system’ and assigned it an image.
[]Deployed image without error to system.
[*]Performed update to 1.1.0
[/LIST]
Going to the Image under Image Management, I associated the image with the correct OS version.

Went to the host, and tried to initiate a deployment task, and encountered the error attached. I’ve attached a screen grab of the image management screen, as well as the host management screen.

What did I miss??

[ATTACH=full]934[/ATTACH][ATTACH=full]935[/ATTACH][ATTACH=full]936[/ATTACH]

[url=“/_imported_xf_attachments/0/934_Unable.png?:”]Unable.png[/url][url=“/_imported_xf_attachments/0/935_host.png?:”]host.png[/url][url=“/_imported_xf_attachments/0/936_image.png?:”]image.png[/url]

Thank you for the timely response. I’ve done as you said, and am now deploying an image from this test server on our newest hardware that was not working under .32.

Thank you for your help!

I’m having difficulty with our current .32 setup - I can’t seem to get our newest batch of hardware to correctly PXE boot to it.

I’ve built a test FOG 1.1.0 server on another box, used the IP address of the former system (powered the .32 off for the time being).

Now, I want to grab an image I created on .32 and drop it on the new server.

In .32, I could grab the image from the /images folder on one server, ‘sneakernet’ it to another server, paste the file to the /images folder, create a new image in the web UI, and point the new image to that folder I pasted.

In FOG 1.1.0 I tried that, but when I told FOG to image the newly inventoried system using that image I created, and pointed to the already pasted folder/file it said I had to upload an image first.

Process has changed, so… how do I go about doing this?