Stuck on "running post init scripts
-
Hi again, I add 2 screenshorts to see if someone can gide me in the right direction:
-
@Numa09 I am not sure how this is related to post init scripts. Can you please give some more context and also post this contents of the scripts if you have those in place?
The error on mount points to an issue with NFS not being possible to connect in your network. Are the client machine and the FOG server on the same subnet? Can’t be sure from the IPs seen in the screenshot because we are missing the subnet mask used.
-
Hi @Sebastian-Roth In first place thanks for your help
They are in the same network 172.16.0.0/27
Server IP is 172.16.5.1 and clients are 172.16.0.x
I enable the DHCP serve during Fog instalation so PXE-DHCP setting should be correct.
My school has many small building and each one has a switch (all of them are the same model-firmware, ect.) all of them conneted to a main one where the server is .
Installation work in some building but not in others.
Logic sais that it must be a network issue but i’ve compared switch configurations and i can’t find any diference.
I´m completly lost -
@Numa09 said in Stuck on "running post init scripts:
They are in the same network 172.16.0.0/27
According to what I know about subnet masks this is a pretty narrow one separating the server from the clients and making it necessary to have a router/gateway in between. You need to look at those to see if network traffic is being filtered.
-
@Sebastian-Roth
Sorry my mistake… it’s a /19… Mask is 255.255.224.0
Subnet goes from 172.16.0.1 to 172.16.31.254
As I told you other computers in the same network are working fine.
I’m now going to move a non working cpu to a working building to see what happen.
Let see if is a pc harware issue or a network one.
I keep you updated
Regards -
Finally if i move the computer to another building it work so it must be a switch issue.
Let see now if i find what it is -
Hi @Sebastian-Roth were can i find logs to see what is failing? I’ve check every thing and every where and can’t find config difereces between locations that work and the ones that doesn’t.
-
@Numa09 Unfortunately there aren’t any logs for the NFS mount part of FOG. But it’s surely a network filtering issue I guess as other network traffic is going through no problem. The whole PXE bootup uses several different protocols and they all seem to work fine up to that point where NFS comes into play. So you might want to search the web for NFS and your switch model.
Other than that you could search this forum for an extensive post by @george1421 about using NFSv4 on a single port which is more network friendly. Be aware this is bleeding edge testing and not officially supported.
-
@Numa09 said in Stuck on "running post init scripts:
’ve check every thing and every where and can’t find config difereces between locations that work and the ones that doesn’t
If you want we can try to debug this.
- Manually register this computer with FOG server if it is not already.
- Schedule a capture/deploy doesn’t matter, but before you press the schedule task button tick the debug checkbox.
- Now pxe boot the target computer from the failing location.
- After several screens of text that you must clear with the enter key you will be dropped to the FOS Linux command prompt on the target computer.
- Now we are going to see if you can first ping the fog server’s IP address. (This should succeed because you were able to pxe boot into FOS Linux.
- Next lets create a directory so we can see if we can mount the fog server via NFS.
mkdir /test - Now lets see if we can connect to the fog server via NFS (this command might/should show you the true error here.
mount -o nolock,proto=tcp,intr,noatime "<fog_server_ip>:/images" /testReplace “<fog_server_ip>” with the IP address of the fog server. Don’t leave the greater than and less than symbols behind.
Lets see if you can mount that directory.
Also post the output of these commands after you try the mount.uname -a ip a s df -hOn the fog server make sure you are not running any kind of firewall to block nfs traffic.
-
I think I have it:
link text
Confirmed this on a 1810G-24 GE, using the last firmware (P.2.22 at this time). The “Auto DoS” feature blocks NFS : ip packets come in, but never come out from the switch.And to notice : disabling the feature is not sufficient to make it work again. I had to do a hard factory reset (factory reset from the web gui did nothing) to make it work again.
It seems that this option is stickying somewhere in the configuration, even after disabling it !
-
@Numa09 Nice find, well done!
-
[[undefined-on, S Sebastian Roth, ]]
