• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Fog Imaging Log Report Not Working 1.2.0

Scheduled Pinned Locked Moved Solved
FOG Problems
2
7
2.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    dustindizzle11
    last edited by Jun 4, 2015, 9:22 PM

    This might be a quick one, but I cannot seem to get the FOG imaging log report to show anything in the web GUI. What happens is I will click the “Imaging Log” button in the GUI, then it will proceed to “(server)/fog/management/index.php?node=report&sub=imaging-log” I have version 1.2.0, which was upgraded from .31. I tried to search for any documentation about this, but came up empty. Has anyone experienced this problem with the FOG reports? If anyone has any ideas let me know, Thanks!

    Dustin Olson

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jun 4, 2015, 9:22 PM

      Check your /etc/php.ini (redhat) /etc/php/apache2/php.ini (ubuntu) for the memory limit. Likely it’s very small (128M) and the amount of logs you’re trying to see is much larger than that.

      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

      1 Reply Last reply Reply Quote 0
      • D
        dustindizzle11
        last edited by Jun 4, 2015, 9:26 PM

        Hi Tom,
        Just checked it and you are right, it is 128M. I am assuming I can safely increase this because this is the default limit. Is that correct? Thanks for the quick reply!

        1 Reply Last reply Reply Quote 0
        • T
          Tom Elliott
          last edited by Jun 4, 2015, 9:28 PM

          Yes, it’s safe to update, but you will also have to restart apache once updated.

          I usually start small increments of double the last (e.g. 256M,512M, etc…)

          To restart apache service apache2 restart (ubuntu) service httpd restart (redhat)

          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

          D 1 Reply Last reply Jun 4, 2015, 9:40 PM Reply Quote 0
          • D
            dustindizzle11 @Tom Elliott
            last edited by Jun 4, 2015, 9:40 PM

            @Tom-Elliott
            I increased it to 256M, and it is working perfectly fine now, Thanks so much! I did notice after running a report though, that it said all the past “downloads” are “uploads”. Unless I am misunderstanding it, I would think they should be downloads. (picture attached) . I may be looking at it wrong, and it’s not a big deal, I just thought I would throw it out there incase this is incorrect. The image is showing times when I sent an image to a computer, “downloaded” to it. In the picture it shows as “Upload”.

            Upload.PNG

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by Jun 4, 2015, 9:42 PM

              some of that is to be expected.

              1.0.0 (and higher) use actual names in the type field, where before (0.32 and below) the type field was a letter and/or number.

              The checks only really care about the upload and download. The check is specific, if not download, must be upload. Hopefully that makes sense.

              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

              D 1 Reply Last reply Jun 4, 2015, 9:43 PM Reply Quote 0
              • D
                dustindizzle11 @Tom Elliott
                last edited by Jun 4, 2015, 9:43 PM

                @Tom-Elliott
                Makes perfect sense. Thanks again Tom!😃

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                1 / 1
                • First post
                  5/7
                  Last post

                200

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project