I had posted a question about why the deployment was not working, where the temporary password validation file would upload correctly but then not read correctly. I loaded a version of Debian 8 as a Virtualbox instance. The same install process and deployment procedure worked correctly.
What I found out is that my VPS provider was using a very old kernel in the 2.x line rather than the current kernel which is at 3.16. Apparently, deployment does not work with the older kernels, even if the file permissions are set correctly.
------------------------------------------------------------------------
The provider explained it as follows:
The virtualization we use for our regular Linux VPS, OpenVZ, does not allow you to run your own kernel, it's a kernel-based virtualization. The kernel seen inside your VPS is inherited from the host node. While it's based on 2.6, it's in active development and getting backports and patches from upstream. You can see the latest release here: [openvz.org]
Our Premium VPS offering runs its own kernel as it is KVM virtualization, and additionally supports Docker and other containerization technologies. There's additional benefits such as daily backups too. Here's more information:
---------------------------------------------------------------------------
So, what I am finding with Linux is that you need to be aware of what kernel is being used. With this provider, even if I installed a very recent version of Ubuntu, I was actually getting an old kernel that had been patched. Apparently it created problems with a file being released for reading after a write.
What I found out is that my VPS provider was using a very old kernel in the 2.x line rather than the current kernel which is at 3.16. Apparently, deployment does not work with the older kernels, even if the file permissions are set correctly.
------------------------------------------------------------------------
The provider explained it as follows:
The virtualization we use for our regular Linux VPS, OpenVZ, does not allow you to run your own kernel, it's a kernel-based virtualization. The kernel seen inside your VPS is inherited from the host node. While it's based on 2.6, it's in active development and getting backports and patches from upstream. You can see the latest release here: [openvz.org]
Our Premium VPS offering runs its own kernel as it is KVM virtualization, and additionally supports Docker and other containerization technologies. There's additional benefits such as daily backups too. Here's more information:
---------------------------------------------------------------------------
So, what I am finding with Linux is that you need to be aware of what kernel is being used. With this provider, even if I installed a very recent version of Ubuntu, I was actually getting an old kernel that had been patched. Apparently it created problems with a file being released for reading after a write.