Mounting file system: Failed. Uploading my first image
-
@Miguel-Palacios I believe it only gives output if there’s an error, so that’s good news already.
-
@Miguel-Palacios Please provide the output of
sudo iptables -L -n -v -
@Quazz I have executed other new capture task and the error is the same that my first post
On the other hand, of new, I have executed other new capture task (with debug activate) and I have executed the command mount but this again returned the same error.
In the side server, the command exportfs -r continues without show nothign… -
@Miguel-Palacios What’s the output of rpcinfo -p?
-
@george1421 here it’s
-
@Quazz the result for rpcinfo -p
-
@Miguel-Palacios said in Mounting file system: Failed. Uploading my first image:
@george1421 here it’s
Sorry for being stubborn here, but what you are seeing is not logical. I don’t doubt it is happening, its just confusing.
-
@george1421 I am in the same situation…
Say you that the FOG server is installed in a virtual machine on VMware ESXi 5.5.0 (3116895)… I don’t know if this detail shed light at problem…
-
@Miguel-Palacios I had my fog servers on centos 6.5 running on vmware 5.5 for over a year. This Jan I rebuilt the server using centos 7 and the current fog trunk. Both worked without issue. Now that I think about it, I have a dev fog server that is still running centos 6.5/6.7. I may need to power it on so we can compare services or what ever.
-
@Sebastian-Roth I attached the result for our test.
-
The PCAP file is showing a perfect connect form client to server on port 111 (portmap) to get the NFS port. Then… silence. After some more digging and testing it turns out that an intermediate cisco switch is causing the problem!
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
-
@Sebastian-Roth Probable, but unbelievable at the same time unless that cisco switch was doing some type of acl filtering this should not normally happen. This results make the first one for me at least…
Great find because I was lost on this one.
-
@Sebastian-Roth said in Mounting file system: Failed. Uploading my first image:
The PCAP file is showing a perfect connect form client to server on port 111 (portmap) to get the NFS port. Then… silence. After some more digging and testing it turns out that an intermediate cisco switch is causing the problem!
Can you give more details on exactly what was wrong with the switch?
-
Hi guys!
Thanks to the great help of @Sebastian-Roth we have managed to figure out the problem. This is a switch CISCO Small Business that had configured between the main switch and the client. I still have outstanding figure out the problem of switch CISCO because it is very rare, there are no complex configurations. If I find something I keep them informed…Connecting the client directly to the main switch no problem.
Thanks everyone for your help!
See you later!
-
@Miguel-Palacios Please give us the model and version of the middle problem switch please?
-
@Miguel-Palacios For some people updating the firmware helps, if that’s a possibility at all it might be worth giving it a go.
-
@Wayne-Workman Yes, this is a CISCO Small Business SG 200-08 (8-Port Gigabit Smart Switch). Version 1.0.6.2.
-
@Miguel-Palacios said in Mounting file system: Failed. Uploading my first image:
@Wayne-Workman Yes, this is a CISCO Small Business SG 200-08 (8-Port Gigabit Smart Switch). Version 1.0.6.2.
For the record, I have a SG100-D8 in the basement and it works fine with FOG. I also have a SD2005 5 port that also works fine.
I’ve got a newer (metal case) Cisco Small business 8 port gig switch at work that also works, it’s the newer style. Don’t know the exact model because I’m not in today.
-
@Wayne-Workman Yes… I also have other Cisco Small Business (same model) working with FOG but not yet know why some fail sometimes very silly things. It is strange and worth investigating.
-
@Miguel-Palacios To be honest, I really doubt it’s the switch… You should look intensely close at the patch cables that were being used as an uplink. Even a slightly loose connection can cause issues, a slightly deformed RJ-45 connector, slightly oxidized connectors, slightly loose connection at the main switch, or just a kink in the cable somewhere… It could even be interference on the patch cable itself, is it running parallel to power cables? That would cause major interference. Keep your patch cables away from power cables!
I really doubt it’s the unmanaged switches fault, and I’m willing to lay 99% odds it’s a cable.
