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

Type: 8, File: /var/www/html/fog/lib/fog/fogcontroller.class.php, Line: 1046, Message: Undefined offset: 3

Scheduled Pinned Locked Moved Solved
FOG Problems
3
4
740
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
    SKasai
    last edited by Jul 13, 2018, 4:44 PM

    I ran into this error when I was trying to submit in a snapin on our FOG server.

    I saw the suggestion for fix here:

    https://forums.fogproject.org/topic/11202/fogcontroller-class-php-undefined-offset-3-line-1046

    However, I tried that and still getting the error message.

    Wondering if there is anything else I can look at?

    1 Reply Last reply Reply Quote 0
    • S
      SKasai
      last edited by Jul 13, 2018, 9:24 PM

      I believe I found the cause of the issue.

      We are running CentOS 6 with FOG version 1.4.3

      I was forced to restrict the iptables to not advertise NFS to the rest of our campus and only to our subnets.

      In that process, I did not allow for iptables to allow lo (loopback, 127.0.0.1) to be accepted, which will also cause this error.

      While I did allow for 127.0.0.1 being the source, which fixed nfs having issues with RPCBind, it does not solve the trying to submit a snapin to FOG as it appears to use -i lo interface path.

      This issue should be considered resolved.

      G 1 Reply Last reply Jul 14, 2018, 5:47 PM Reply Quote 0
      • G
        george1421 Moderator @SKasai
        last edited by Jul 14, 2018, 5:47 PM

        @skasai In addition/instead of using iptables once could restrict nfs access on the nfs share level too. I understand you have a working build so don’t change just because of this, but be aware that with NFS v3 you can restrict mounting the NFS share based on ip address/subnet range.

        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!

        1 Reply Last reply Reply Quote 0
        • Y
          ynixon
          last edited by Sep 20, 2018, 4:00 PM

          Hi,
          I tried the password fix and it didn’t help.
          Did you manage to overcome this issue?

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

          151

          Online

          12.1k

          Users

          17.3k

          Topics

          155.3k

          Posts
          Copyright © 2012-2024 FOG Project