could not mount images folder (/bin/fog.upload)

[Trev-lchs]

I am seeing the above error followed by, Args Passed: reason: Mounting 10.10.2.35:/images/dev on /images failed: No such file or directory.
Anyone got any idea?

[Sebastian Roth]

@Trev-lchs Please run the following two commands on your FOG server console and post full output here:

cat /etc/exports
showmount -e

By the way, which version of FOG do you run?

[Trev-lchs]

Hi Sebastian thanks for the reply i am running 1.5.7.2 just about to use putty to get onto the server to run those commands, that is what you mean by console?

[Trev-lchs]

root@fog-03:~# cat /etc/exports
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

root@fog-03:~# showmount -e
Export list for fog-03:
/images/dev *
/images *
root@fog-03:~#

[Sebastian Roth]

@Trev-lchs Ok, the NFS shares look fine!

Is the IP address of your FOG server 10.10.2.35?

[Trev-lchs]

@Sebastian-Roth yes it is giving the correct address

[Sebastian Roth]

@Trev-lchs Then probably the firewall is not disabled/setup to allow NFS.

iptables -L -n -v
systemctl status firewalld
firewall-cmd --state
getenforce

Are you on CentOS?

[Trev-lchs]

@Sebastian-Roth said in could not mount images folder (/bin/fog.upload):

iptables -L -n -v
systemctl status firewalld
firewall-cmd --state
getenforce

Hi Sabastian, the firewall is not installed.

root@fog-03:~# iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
root@fog-03:~# systemctl status firewalld
● firewalld.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
root@fog-03:~# firewall-cmd --state
The program ‘firewall-cmd’ is currently not installed. You can install it by typing:
apt install firewalld
root@fog-03:~# getenforce

Centos?

[Sebastian Roth]

@Trev-lchs Ok seems like you use Ubuntu or Debian. Which Version??

Firewall seems off. Can you please take a picture of the error on the screen where it fails. Guess we are missing some information here.

[Trev-lchs]

we can deploy images correctly though, just not upload them

[Sebastian Roth]

@Trev-lchs Deploy via multicast or on single machines. Please provide all the information requested!

[Trev-lchs]

@Sebastian-Roth to 10 or more PCs please see the attached picture of the error

[Trev-lchs]

@Sebastian-Roth i mean 10 or less at once, not more.

[Trev-lchs]

@Sebastian-Roth I seem to remember that fog stopped working after an unbuntu update, the webpage would not work and system locked up when rebooted as they could not get the ipex file i seem to remember a thread call Unbuntu updates the ememy of fog

[Trev-lchs]

@Sebastian-Roth this one https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy/22?lang=en-US&page=2

I think i would have followed those instructions, could this be the issue?

[george1421]

@Trev-lchs Its probably not the ubuntu enemy post. That would deal with database issues. This appears to be an nfs issue.

What is the output of showmount -e 127.0.0.1 also ip addr show

Edit: OK looking at previous posts I see the showmount command being issued. So lets try something else (in next post)

[Trev-lchs]

@george1421

root@fog-03:~# showmount -e 127.0.0.1
Export list for 127.0.0.1:
/images/dev *
/images     *

root@fog-03:~#
root@fog-03:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:21:5a:d1:d2:20 brd ff:ff:ff:ff:ff:ff
    inet 10.10.1.26/16 brd 10.10.255.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::221:5aff:fed1:d220/64 scope link
       valid_lft forever preferred_lft forever
3: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:21:5a:d1:d2:1e brd ff:ff:ff:ff:ff:ff

[george1421]

Is the target (pxe booting) computer on the same IP subnet as the fog server? The question is around if there are any screening routers or firewalls between the two devices.

We may need to setup a debug deploy test. This is where you schedule a capture but before hitting the schedule task button you tick the debug checkbox. Then schedule the task. PXE boot the target computer and it will boot into the debug console. You will have several screens of text you need to clear by pressing the enter key. Eventually you will be dropped to a linux command prompt. This is the FOS Linux debug environment. At this point we need to key in a few commands.

The first will be a ping to see if the target computer and ping the fog server by its IP address.

These next steps are optional but will help with copy and pasting into the debug console. These next few steps will allow you to connect to the target computer using putty or ssh. From putty or ssh you can paste in the mount command exactly without having to key it in. These commands need to be executed on the target computer not the FOG server.

Setting up a remote debugging session to FOS Linux.

1. At the FOS Linux command prompt key in ip addr show and get the IP address of the target computer.
2. Give the root user a known password with passwd This will be a one time password so make it simple like hello
3. From a putty or ssh session connect to the target computer using the IP address collected in step 1.
4. Login as root with the password you set in step 2

From there lets issue these two commands. The first will create the /images directory on the target computer and the second will map the share on the fog server to the target computer’s mount point.

1. mkdir /images
2. mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime "10.10.1.26:/images/dev" /images

That should connect the directory. If it connects without error issue this command and post the results (note you can copy and paste from putty)

ls -la /images

[Trev-lchs]

yes the PC is on the same subnet as fog.

[george1421]

@Trev-lchs I’ve added some additional comments to my previous post.