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

    Just upgraded to 1.2.0 and iPXE gives operation not permitted

    Scheduled Pinned Locked Moved
    FOG Problems
    6
    23
    13.5k
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      At first I thought access rights seem ok. But luckily I didn’t trust my eyes and starting setting rights on my system just to make sure I didn’t miss something. And there it is…
      [CODE]sudo ls -al /var/www/fog/service/ipxe
      total 34188
      drwx------ 2 fog www-data 4096 2015-03-26 11:54 .
      …[/CODE]
      The directory itself is not accessible by the webserver. AFAIK all those files and the directory should be owned by www-data and execution rights are not needed:
      [CODE]sudo chown -R www-data /var/www/fog/service/ipxe
      sudo chmod 755 /var/www/fog/service/ipxe
      sudo chmod 644 /var/www/fog/service/ipxe/*[/CODE]
      Boot up the client and see if things work!

      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

      F 1 Reply Last reply Reply Quote 0
      • T
        Tim.Trageser
        last edited by

        That worked!!!

        Thanks you guys are great and now begins the process of exploring the features we are not using yet and convincing my bosses that we should be.

        This is an awesome tool thanks for making it, updating it and helping those of us new to linux and FOG.

        1 Reply Last reply Reply Quote 0
        • F
          fredrick.pettiford @Sebastian Roth
          last edited by

          @sebastian-roth This fixed my issue as well…set permissions to 777 🙂 I’ll tighten here in a minute.

          1 Reply Last reply Reply Quote 0
          • 1
          • 2
          • 2 / 2
          • First post
            Last post

          178

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project