Could not mount images folder /bin/fog.upload


  • Hi,

    I run Fog on a debian 10.5 with dhcpmasq in proxmox container.

    When i try to upload my image from my host to the server…

    alt text

    Here is my cat /etc/exports

    /images                        *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
    /images/dev                    *(rw,async,no_wdelay,no_root_squash,insecure)
    

    I think the bug is relative to NFS but i cant find what goes wrong…
    So when i run service nfs-kernel-server status

    * nfs-server.service - NFS server and services
       Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset:
       Active: inactive (dead)
    
    Jan 08 12:47:12 fogSIS systemd[1]: Dependency failed for NFS server and services.
    Jan 08 12:47:12 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
    Jan 08 12:54:51 fogSIS systemd[1]: Dependency failed for NFS server and services.
    Jan 08 12:54:51 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
    Jan 08 12:55:23 fogSIS systemd[1]: Dependency failed for NFS server and services.
    Jan 08 12:55:23 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
    Jan 08 12:55:38 fogSIS systemd[1]: Dependency failed for NFS server and services.
    Jan 08 12:55:38 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
    Jan 08 13:14:29 fogSIS systemd[1]: Dependency failed for NFS server and services.
    Jan 08 13:14:29 fogSIS systemd[1]: nfs-server.service: Job nfs-server.service/start
    

    service nfs-kernel-server restart

    A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
    

    journalctl -xe

    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- The unit run-rpc_pipefs.mount has entered the 'failed' state with result 'exit-c
    Jan 08 13:16:11 fogSIS systemd[1]: Failed to mount RPC Pipe File System.
    -- Subject: A start job for unit run-rpc_pipefs.mount has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit run-rpc_pipefs.mount has finished with a failure.
    --
    -- The job identifier is 764 and the job result is failed.
    Jan 08 13:16:11 fogSIS systemd[1]: Dependency failed for RPC security service for N
    -- Subject: A start job for unit rpc-gssd.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit rpc-gssd.service has finished with a failure.
    --
    -- The job identifier is 763 and the job result is dependency.
    Jan 08 13:16:11 fogSIS systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start fai
    Jan 08 13:16:11 fogSIS systemd[1]: Dependency failed for RPC security service for N
    -- Subject: A start job for unit rpc-svcgssd.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- A start job for unit rpc-svcgssd.service has finished with a failure.
    --
    -- The job identifier is 767 and the job result is dependency.
    Jan 08 13:16:11 fogSIS systemd[1]: rpc-svcgssd.service: Job rpc-svcgssd.service/sta
    Jan 08 13:16:11 fogSIS systemd[1]: nfs-config.service: Succeeded.
    -- Subject: Unit succeeded
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- The unit nfs-config.service has successfully entered the 'dead' state.
    Jan 08 13:16:11 fogSIS systemd[1]: Started Preprocess NFS configuration.
    -- Subject: A start job for unit nfs-config.service has finished successfully
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    

    thank you in advance

  • Moderator

    @nil If you are interested in helping start out by writing a tutorial in the tutorial forum. Then once others have a chance to prove it out it will be converted to a wiki page.

    Thank you for helping the FOG Project move forward by adding new options for installing FOG.


  • @george1421

    I don’t know if I have a COMPLETE solution (At the moment I’m just cloning and deploying images and it works great)

    I haven’t tried all of the functionality Fog offers yet, but I will be doing so very soon.

    I am a student in computer science and currently in internship, I have already written a tutorial (in French for my internship) but for me it would be very interesting to help the fog community so I will write one in English for the LXC containers .

    The LXC container part in the wiki is outdated (2018), I mean there are a lot easier now. how is it going? I write it and then I send it to you?

  • Moderator

    @nil Do you have a complete working solution now?

    If so I think it would be very valuable if you could write a tutorial on the setup from beginning to running, since you have advanced knowledge of how the LXC containers work together.


  • @Sebastian-Roth you were right the problem came from the LXC container.
    @george1421 I have run showmount -e 127.0.0.1 and he return me

    clnt_create: RPC: Program not registered
    

    Debian firewall was disabled and the firewall checkbox in the proxmox was unchecked.

    So I went to see the LXC container, I did a lot of research and I found 🙂

    LXC Container in proxmox are created in unpriviled (see checkbox)

    3ddbd238-1504-43b8-98d0-3d992d10a4ec-image.png

    It is necessary to uncheck this box to be able to activate the NFS
    Then in the container options (see screen)

    294eb582-80b4-4dfa-aabc-413d4b3c70ca-image.png

    Go to “Features” and Edit, here you can activate NFS in the WebUI (You can also in cmd line but i dont recommand to that).
    Check “NFS” for the NFS … and also “Nesting” otherwise you will get a MySQL error like

    Setting up and starting MySQL...............................Failed!
    

    (during the installation process) or the MySQL system will not start on an existing installation

    d9964c8c-a687-480c-881d-0ade52903991-image.png

    If like me you have an existing installation and you dont want to recreate all the ct from the start, in proxmox go to backup and backup your LXC Container, next restore it and be careful to uncheck the checkbox “Unpriviliged container” (see screen)

    031cd9b4-20f8-48b1-b7ad-b70c7a25d0bb-image.png

    Now uploading and deploying image works perfectly
    English is not my native language, I may have expressed myself poorly, do not hesitate to point it out to me.

    Thanks for your help guys.
    Have a nice day

  • Moderator

    @sebastian-roth Sorry I missed the part about LXC container. While this is now a bit off topic, I built another FOG VM last night and I happened to notice that on the network adapter tab there was a checkbox for “firewall” that was enabled by default. Because of the color scheme proxmox uses it looks like the option is disabled (gray) even though the box is checked. I don’t know what this option does at the moment, but it sounds like proxmox itself can restrict network access to a VM. I need to look a bit deeper into this option.

    If the showmount command is not providing results then NFS is not working right on the computer. You can run showmount command against a remote computer too, just replace the loopback address with the address of the remote computer running NFS.

  • Senior Developer

    @nil said in Could not mount images folder /bin/fog.upload:

    And maybe I will try to redo an installation on another LXC container and if it does not work I will do it on a VM…

    I am fairly sure the issue comes from using LXC container… read through the forum post I mentioned earlier.


  • @george1421 Thanks for your answers

    Yes I hand edit the exports file, i have seen that fsid=0 and fsid=1 was missing so I added it and retry the upload and it was the same result. Can it come because I edited the exports file ?
    I dont have access to my server now, i will have acces Monday so i am gonna try showmount -e 127.0.0.1 but in my memory when i run showmount -e x.x.x.x
    that return me a things like that

    clnt_create: RPC: Program not registered
    

    And also i will look to the firewall.
    And maybe I will try to redo an installation on another LXC container and if it does not work I will do it on a VM…

  • Moderator

    @sebastian-roth I have FOG server(s) running on proxmox on my home lab. If you use the full VM mode there is nothing you have to do FOG just works, If you use the lxc containers… I don’t know.

  • Senior Developer

    @nil said in Could not mount images folder /bin/fog.upload:

    I run Fog on a debian 10.5 with dhcpmasq in proxmox container.

    Possibly Proxmox setup is causing NFS to fail.

    There was a brief discussion on Proxmox containers in the forums just a few weeks ago: https://forums.fogproject.org/topic/14996/fog-on-proxmox

  • Moderator

    @nil Just looking at the exports line the fsid=0 and fsid=1 stanza missing from each line. Did you hand edit the exports file?

    Also you can run the showmount -e 127.0.0.1 to show the nfs exports.

    Also make sure the debian firewall is disabled.

260
Online

7.8k
Users

14.8k
Topics

139.4k
Posts