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

NFS error

Scheduled Pinned Locked Moved
General
4
6
809
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
    mass
    last edited by Jun 8, 2023, 2:13 PM

    I tried to install a Fog server with a static IP address in a virtual network that I manage from a Proxmox server. On this Proxmox server, I have pfSense, Windows Server, and a GLPI server. I also have multiple clients, and everything is working well (local DNS, DHCP, etc.), except for when I try to set up my Fog server (version 1.5) on an LXC container running Ubuntu Server 20.04.

    I am encountering a problem with the NFS Server. I want to mention that I am setting up this network for a school and professional environment.

    For my installation, I followed these steps:

    What DNS address should DHCP allow? [192.168.1.1] 192.168.1.10
    Would you like to use the FOG server for DHCP service? [y/N] n
    This version of FOG has internationalization support, would you like to install the additional language packs? [y/N] y
    Would you like to enable secure HTTPS on your FOG server? [y/N] n
    Which hostname would you like to use? Currently is: SrvFOG.lan
    Would you like to change it? If you are not sure, select No. [y/N] y
    Which hostname would you like to use? fog.mass.lan
    FOG would like to collect some data...
    What is this information used for?
    

    Any help or suggestions would be greatly appreciated.
    error :

    • Setting up and starting NFS Server…Failed to get unit file state for nfs.service: No such file or directory
      Failed!
    M 1 Reply Last reply Jun 9, 2023, 8:42 AM Reply Quote 0
    • ?
      A Former User
      last edited by Jun 9, 2023, 7:29 AM

      Hello,
      When ou create your container, try to uncheck “Unprivileged container”.
      After, go to “Options” on your container params and enable “Nesting” and “NFS” options.

      M 1 Reply Last reply Jun 9, 2023, 9:16 AM Reply Quote 0
      • M
        mass @mass
        last edited by Jun 9, 2023, 8:42 AM

        @mass Thank you very much for your help, I understand better why it caused issues on Proxmox but not on virt-manager (QEMU).
        Thank you for your response, I did indeed uncheck “Unprivileged container” and I checked “NFS” and “Nesting” under Options > Features.

        1 Reply Last reply Reply Quote 0
        • M
          mass @A Former User
          last edited by Jun 9, 2023, 9:16 AM

          @glequeau Thank you very much for your help, I understand better why it caused issues on Proxmox but not on virt-manager (QEMU).
          Thank you for your response, I did indeed uncheck “Unprivileged container” and I checked “NFS” and “Nesting” under Options > Features.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Jun 11, 2023, 12:49 AM Jun 11, 2023, 6:47 AM

            @mass said in NFS error:

            … set up my Fog server (version 1.5) …

            Hope you mean 1.5.10 and not 1.5.0?!?!?

            @glequeau Great hint on this!

            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
              Brysonzv
              last edited by Jul 18, 2023, 9:09 AM

              Make sure your Proxmox server is set up with a static IP address on the physical network interface. For the virtual network, ensure that it is set up correctly, and all VMs and LXC containers are attached to this network. Assign static IP addresses to all your servers and clients to avoid conflicts with DHCP. Reserve these IP addresses in your DHCP server configuration (pfSense) to prevent accidental IP allocation conflicts. Ensure that your LXC container (running Ubuntu Server) has the correct network configuration. Use a bridged network interface so that the container can get its IP address directly from the physical network. Double-check that the LXC container’s network settings are consistent with your Proxmox virtual network setup.

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

              197

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project