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

images on separate nfs server

Scheduled Pinned Locked Moved Solved
FOG Problems
3
6
1.8k
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.
  • M
    MarkusK
    last edited by Mar 3, 2017, 8:39 AM

    Server
    • FOG Version: 1.3.4
    • OS: Ubuntu 14.04
    Description

    I have a fog server x.x.x.59 and an NFS/FTP server x.x.x.155 where i store the images.

    When I define the IP of the DefaultStoreageNode as x.x.x.59 the client boots, creates the image, updates the database and fails connecting to the NFS server. It tries x.x.x.59:/fog/dev, but it should x.x.x.155:/fog/dev

    When I define the IP of the DefaultStorageNode as x.x.x.155 the client boots, creates the image, and fails updating the database. It tries probably tries x.x.x.155, which is not the database server, it’s the NFS server.

    How can I work around this problem? I think when updating the database, fog should always use x.x.x.59 like it was in fog 1.2.0

    Thanks for your help and suggestions to solve this problem.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Mar 3, 2017, 10:36 AM

      What manufacturer is device x.x.x.155?

      You will need these shares on your nfs/ftp server /images and /images/dev. They need to be shared via nfs and have ftp access to move the images from /images/dev to /images on the storage node.

      If the remote ftp/nfs server is a nas like synology you can add this device as a storage node and then direct the images to that storage node.

      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!

      M 1 Reply Last reply Mar 3, 2017, 12:21 PM Reply Quote 2
      • M
        MarkusK @george1421
        last edited by MarkusK Mar 3, 2017, 6:22 AM Mar 3, 2017, 12:21 PM

        @george1421 The nfs server is not the problem, it works. The problem is, that the IP for the database server (fog server?) changes, when I change the IP of the DefaultStorageNode.

        G T 2 Replies Last reply Mar 3, 2017, 12:35 PM Reply Quote 0
        • G
          george1421 Moderator @MarkusK
          last edited by george1421 Mar 3, 2017, 6:36 AM Mar 3, 2017, 12:35 PM

          @MarkusK Again, what is your nfs device?

          That device must have FTP service enabled or you will get a database update error. The error is a bit misleading. Since FOG moves the captured image from /images/dev/<mac_address> to /images/<image_name> just before it updates the database in the fog server.

          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!

          M 1 Reply Last reply Mar 6, 2017, 2:00 PM Reply Quote 2
          • T
            Tom Elliott @MarkusK
            last edited by Mar 3, 2017, 12:36 PM

            @MarkusK Your statement makes 0 sense. Please clarify?

            @george1421 isn’t saying that NFS is the issue, he’s saying what manufacturer is the device? Is the NFS Server laid out properly as expected by fog?

            The IP for the database isn’t changing one bit.

            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 1
            • M
              MarkusK @george1421
              last edited by Mar 6, 2017, 2:00 PM

              @george1421 Thanks for clarifying. The ftp server was the problem. The “Updating Database” confused me into thinking, the fog database fails to update.

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

              161

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project