Starting sshd: touch: cannot touch '/var/lock/sshd' : No such file or directory

[Alan Lim]

I have created a new storage node (Node 1) and some machines cannot perform image deployment from this new node. The following are the errors that appeared during the deployment.

---

Starting sshd: touch: cannot touch ‘/var/lock/sshd’ : No such file or directory
OK

• Running post init scripts … (after few minutes)

Reason: mount: mounting xxx.xxx.xxx.xxx:/image failed: Connection timed out.

---

It happened only on one of the VLAN and let’s call it VLAN10. It is strange that the VLAN 10 has no problem deploying images from the master node. But another VLAN has no problem deploying images from Node 1.

Which log file that I investigate?
Has anyone encountered such a problem?
Appreciate it if someone could guide me. thank you

[jfernandz]

I’m having the very same problem but with automatic registration processes (quick and full) from the FOG’s grub menu.

I’d say the problem is actually the ‘/var/lock’ folder as it makes no sense to me that ‘touch’ cannot create a file, so I’m guessing it’s the actual path what doesn’t exist. But where? … the path exists in the FOG server so … not sure where should this path be created …

I’d appreciate some help from FOG devs

[george1421]

@jfernandz Will you provide a screenshot of the error? I’m thinking this error is coming from FOS Linux (not the fog server host OS), but not sure what its doing to require the lock file.

[Sebastian Roth]

@Alan-Lim @jfernandz The message Starting sshd: touch: cannot touch '/var/lock/sshd' : No such file or directory is normal with the buildroot version currently used for the FOS inits. While it’s not nice it’s not causing any kind of issue and can be ignored.

The mount error seen after that is probably caused due to a router or firewall now allowing all the traffic needed to mount an NFS share.