Hello, hope you’re all doing well today. I recently stood up a Pydio Cells installation in AWS and I’m experiencing a few problems that I’m hoping someone can help me with. My problems/questions are as follows:
I am unable to utilize any “additional” storage on the Pydio Server. Whenever I tried to add a new disk into the software, it caused major issues. (more details below)
Is there a way to make Pydio listen on more than one URL? For example, lets say I wanted to setup the website: downloads.kevin.com but I also wanted to setup downloads.kevin.org on the same server. Is there any way to have the server listen to both? Or would I need to put some kind of proxy or URL redirection in front of the server?
Problem Description for Problem 1:
I setup Pydio in AWS according to the Pydio cells guides located on the Pydio webpage. I am using an Ubuntu VM hosted in Amazon AWS. My original plan was to have the OS on one physical disk and to have any Pydio related file storage on another physical disk. This would obviously ease backups/snapshots/moving to new servers in the future.
For those who are unaware the typical disk on AWS is called an EBS(Elastic Block Storage). For all intents and purposes, this appears to the OS as a physically connected hard drive. Nothing special there that I am aware of. When operating with just the disk that the OS installed on, everything works fine. However, when I add a new disk and try to add a new datastore and workspace location in Pydio, the server no longer works properly. Uploading files appears to work but as soon as they are uploaded, they are immediately deleted and the server tries to re-upload them again. Just to be sure, I attempted to do this a few separate ways:
I attempted to mount the new drive in /mnt/testing/pydio (or something similar to that… basically I just wanted it to be enough layers deep into the filesystem that Pydio would be okay with it).
I attempted to copy the contents of one of the existing Pydio folders (cellsdata, pydiods1, etc) into the new drive. Then I mounted that drive into the filesystem at the proper location… same type of errors.
From a permissions perspective everything looks the same, from an ownership perspective all of the files are owned by the pydio user and group. Within the OS itself, the pydio user can create, delete, move files etc without any issues. I’m pretty sure it can’t be an incompatibility with EBS because the base OS disk is also an EBS.
Additionally, I’ve tried the same steps with whats called an EFS (Elastic File System). This winds up appearing to the OS as an NFS mounted disk. This had the same issues.
This has happened across several rebuilds of the entire server(aka, starting from scratch with a new AWS Instance).
Has anyone seen issues like this or have any ideas what else I can try? I would really like to build this server “properly” and not have to worry about things like the OS disk running out of space, difficult backups, etc.
OS: Ubuntu 18.04
App Version: Pydio Cells Home Edition 1.6.1