autopilotpattern / nfsserver Goto Github PK

The health checks implemented here are not nearly as thorough as it should be.

A better example may be found in https://exchange.nagios.org/directory/Plugins/Operating-Systems/Linux/check_nfs_health-2Esh/details. That, or something else should be implemented here.

Following from TritonDataCenter/containerpilot#218: When a Consul agent running as a co-process in a ContainerPiloted application exits, it is not de-registered from the Consul cluster.

@fitz123 suggests the leave_on_terminate Consul option will fix that. This ticket proposes implementing that option in this repo and for others in https://github.com/autopilotpattern.

Following the Testing section in the README.md file, the NFS share won't mount.

When running mount -t nfs -v -o nolock,vers=3 nfs:/exports /nfs, I get the following output:

mount.nfs: timeout set for Tue May  1 01:02:04 2018
mount.nfs: trying text-based options 'nolock,vers=3,addr=172.17.0.3'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 172.17.0.3 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 172.17.0.3 prog 100005 vers 3 prot TCP port 1892
mount.nfs: Protocol not supported

When running ls -al /nfs, I get the following output:

total 8
drwxr-xr-x  2 root root 4096 May  1 00:59 .
drwxr-xr-x 41 root root 4096 May  1 00:59 ..

Execing into the nfsserver container, I can see that the /exports directory has the date file created.

I've tried troubleshooting the nfsserver, but all online help that I could find doesn't seem to apply since the NFS server is a custom NodeJS app and not the linux kernel.

Any help resolving this would be greatly appreciated.

https://github.com/bahamas10/node-manta-sync would be an easy addition with huge value:

• on-demand sync to Manta
• ability to pull down content from Manta before starting
• automatic backups to Manta

All those would be optional, of course.

Some prior Manta client configuration examples:

• Using Manta creds: https://github.com/autopilotpattern/mysql/blob/master/_env-example#L8-L15
• Better approach to injecting the private key: https://github.com/autopilotpattern/jenkins/blob/master/setup.sh#L121

ContainerPilot 2.0 introduced a telemetry feature that would be very useful for monitoring this application.

The most useful metric for scaling is probably the available disk space. The following reports used space as a decimal value between 0 and 1:

df -h -P /exports | awk 'NR==2 {print $5/100}'