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

Bugs in FOG 0.33

Scheduled Pinned Locked Moved Solved
Bug Reports
49
308
376.1k
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.
  • T
    Tom Elliott
    last edited by Feb 11, 2014, 9:33 PM

    So it was a sort of configuration issue?

    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
    • B
      BigMan99211
      last edited by Feb 11, 2014, 9:50 PM

      I guess so. I saw where the Fog install adds the index.php with a redirect to “./management/index.php”, but apache2 didn’t recognize it. It just kept showing the default apache “It Works!” page. But, once you remove the default “index.html” page, everything seems to work just fine. Perhaps a Fog installer oversight? 😉

      "Failure is not an option. It come pre-installed on Windows…" - Anonymous

      "Life is hard; It's harder if you're stupid" - John Wayne

      1 Reply Last reply Reply Quote 0
      • T
        Tom Elliott
        last edited by Feb 11, 2014, 9:52 PM

        No it’s more an apache2 installation thing on Debian systems.

        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
        • J
          Jaymes Driver Developer
          last edited by Feb 12, 2014, 12:26 PM

          BigMan99211, You need to adjust apache to look for php before html, or remove the html file as you described above. This is not a bug.

          That “This works!” page is a default created by apache as a courtesy to check on localhost to make sure your folder is accessible. I theory we could add a “remove index.html if exists” line, but for those of us that use our FOG servers as web servers (internal or external) this could cause a HUGE headache if your index.html went missing.

          WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

          1 Reply Last reply Reply Quote 0
          • B
            BigMan99211
            last edited by Feb 12, 2014, 3:51 PM

            I can understand that. But, couldn’t you just put in a simple question during install, asking if you have any other websites or software that utilizes Apache? If yes, it skips. If no, it deletes the .html file. Seems pretty simple.

            "Failure is not an option. It come pre-installed on Windows…" - Anonymous

            "Life is hard; It's harder if you're stupid" - John Wayne

            1 Reply Last reply Reply Quote 0
            • J
              Jaymes Driver Developer
              last edited by Feb 12, 2014, 4:46 PM

              I’m sure it could, would be easier to attack the apache config file and add .php extension to the file so it looks for the php file first 🙂

              Besides it tells you after you finish installation to navigate to the “[url]http://ipaddressofserver/fog/management[/url]”.

              Hell, if I remember correctly the link is even clickable in the terminal window so you don’t actually HAVE to type or copy anything, just make a shortcut.

              WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

              1 Reply Last reply Reply Quote 0
              • B
                BigMan99211
                last edited by Feb 12, 2014, 10:25 PM

                I’ve always been a proponent of making installations easier, or even more customizable through the installer. Ask a bunch of questions at first, and make the setup and configuration a lot more seamless.

                "Failure is not an option. It come pre-installed on Windows…" - Anonymous

                "Life is hard; It's harder if you're stupid" - John Wayne

                1 Reply Last reply Reply Quote 0
                • J
                  Jaymes Driver Developer
                  last edited by Feb 13, 2014, 12:52 PM

                  I like your stance, but I feel differently about the said subject.

                  I could climb on a soapbox, but my final words to utter are “this is not a bug, and does not need to be addressed.” and that’s my two cents. If others feel the same way as you do, you need to twist Tom’s arm to get what you need 🙂

                  WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                  1 Reply Last reply Reply Quote 0
                  • P
                    pmonstad
                    last edited by Feb 13, 2014, 7:59 PM

                    Could there be some kind of option during the installation wether to choose clamav and htmldocs or not? Installing these packages on Redhat/Centos needs editing in the config file as it will not work out of the box.

                    1 Reply Last reply Reply Quote 0
                    • J
                      Jaymes Driver Developer
                      last edited by Feb 13, 2014, 8:26 PM

                      That is because FOG 0.32 is sorely outdated and was meant to run on the older versions of linux. Since then newer and updated packages are being used in the later distributions. Tom is working on FOG 0.33b and I’m sure when all is said and done he will iron out the issues with htmldocs and clamav by updating the repositories and versions it uses/installs.

                      In the mean time please use the work arounds found on the forum to install and configure the services.

                      Tom started working on FOG here recently he wasn’t always the maintainer so he doesn’t have access to edit the old FOG 0.32 files and NOR should he.

                      WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

                      1 Reply Last reply Reply Quote 0
                      • P
                        pmonstad
                        last edited by Feb 13, 2014, 8:31 PM

                        Sorry I forgot to mention I refer to 0.33 beta…

                        1 Reply Last reply Reply Quote 0
                        • P
                          pmonstad
                          last edited by Feb 13, 2014, 8:43 PM

                          The deploy date in host management, as proposed/discussed here some days ago. Here is an example of how I think this could be (in red font): [url]http://awesomescreenshot.com/03a2cmvxc2[/url]

                          This way it is really easy to find “old” hosts which I have to get to my office for imaging.

                          1 Reply Last reply Reply Quote 0
                          • T
                            Tom Elliott
                            last edited by Feb 14, 2014, 12:39 AM

                            This isn’t really a bug, but a request. That’s okay though. It will require a minor schema change, but I have to do so anyway to enable shutdown to work with iPXE.

                            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
                            • F
                              falko Moderator
                              last edited by Feb 15, 2014, 8:47 AM

                              Whilst I think it would be good for deploy date, that still leaves the issue of having to find what image version you deployed. Of course maybe each deploy date could have the image version with it.
                              For this (and other benefits) I have bginfo installed (connected to sql, and then MS Access for reporting) and have a reg key that bginfo picks up. The reg key gets updated to corresponde with the fog image it will become once uploaded

                              1 Reply Last reply Reply Quote 0
                              • P
                                pmonstad
                                last edited by Feb 15, 2014, 2:15 PM

                                Another missing feature is a date when an image was last uploaded: (red font) [url]http://awesomescreenshot.com/0682cwm8e6[/url]

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tom Elliott
                                  last edited by Feb 15, 2014, 10:58 PM

                                  While I don’t mind the suggestions, I would prefer if you refrain from using the word “missing” when requesting a “New Feature” as missing, at least in my eye’s, implies it was there to begin with, but then was removed. Once again, it will require a schema update, but ultimately you could actually use the “imaging” log to check when an image was uploaded/deployed last.

                                  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
                                  • B
                                    BigMan99211
                                    last edited by Feb 17, 2014, 3:05 PM

                                    @falko - Do you have any sort of guide on how to have FOG update bginfo. We currently have to do this manually, and it would be so helpful to have it automated! Right now, we run bginfo, update the date and image name, then have a small batch that uses mini irfanview to change from bmp to jpg, then copies to the oobe folder for the lock screen. (this is for Win7).

                                    "Failure is not an option. It come pre-installed on Windows…" - Anonymous

                                    "Life is hard; It's harder if you're stupid" - John Wayne

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      Gilou
                                      last edited by Feb 17, 2014, 4:36 PM

                                      It could also be based on the info on the date of the file/directory itself, rather than stored in the db!

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        BigMan99211
                                        last edited by Feb 17, 2014, 6:55 PM

                                        So, I don’t know if this is a bug or not, but I just came across an interesting issue when the PXE menu comes up on Dell Optiplex 790 machines. I have PXE set to default to the HD after 3 seconds (I think that is standard), but when the 790 model tries to boot to the HD, it just reboots, thus and endless reboot cycle ensues… The odd thing is, the 780 and 7010 (older and newer model) boots to the HD just fine. I’ve also confirmed that all have the most updated BIOS and all have the same mobo settings, with regards to boot/HD options.

                                        Any ideas?

                                        "Failure is not an option. It come pre-installed on Windows…" - Anonymous

                                        "Life is hard; It's harder if you're stupid" - John Wayne

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          Tom Elliott
                                          last edited by Feb 17, 2014, 8:37 PM

                                          I’ve been seeing this issue on and off again. Would you be willing to try the workaround fix for this issue through ipxe? I ask because, as you state, this isn’t really a big with fog but more a bug with the particular bios usually from dells.

                                          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
                                          • 1
                                          • 2
                                          • 11
                                          • 12
                                          • 13
                                          • 14
                                          • 15
                                          • 16
                                          • 13 / 16
                                          13 / 16
                                          • First post
                                            251/308
                                            Last post

                                          275

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project