Not working on Centos7
davetbo opened this issue · 3 comments
Hello,
I believe I followed all the instructions correctly. I had this working properly on Centos6. However, due to another software incompatibility I'm now switching to Centos7 and I can't get this to work. Specifically, when I try to mount the folder the mount point ("uploads" in the list below)looks like this:
-rw-r--r--. 1 owner group 28 Jan 8 2012 index.php
drwxr-xr-x. 16 owner group 4096 Apr 27 04:28 plugins
drwxr-xr-x. 4 owner group 4096 Apr 14 00:21 themes
??????????? ? ? ? ? ? uploads (with the background color black and the font red...which is traditionally what happens when you have a symlink to a non-existent file).
Before I try to mount it, it looks like this:
drwxr-xr-x. 5 owner group 63 May 6 19:27 .
drwxr-xr-x. 8 owner group 4096 Apr 27 18:15 ..
-rw-r--r--. 1 owner group 28 Jan 8 2012 index.php
drwxr-xr-x. 16 owner group 4096 Apr 27 04:28 plugins
drwxr-xr-x. 4 owner group 4096 Apr 14 00:21 themes
drwxr-xr-x. 2 root root 6 May 6 19:27 uploads
I'm trying to use this to store my WordPress uploads folder. Any advice as to what might be going wrong? Here's the command I'm running and the output I'm getting:
[root@dev2 wp-content]# yas3fs s3://$BUCKET $MOUNTDIR --topic $TOPIC --queue $QUEUE --region $REGION --cache-on-disk $CACHEONDISK --cache-path $CACHEDIR --uid $UID --gid $GID
2016-05-06 22:13:07,160 INFO Version: 2.3.2
2016-05-06 22:13:07,160 INFO s3-retries: '3'
2016-05-06 22:13:07,160 INFO s3-retries-sleep: '1' seconds
2016-05-06 22:13:07,160 INFO S3 bucket: 'bucketname'
2016-05-06 22:13:07,160 INFO S3 prefix (can be empty): ''
2016-05-06 22:13:07,161 INFO AWS region for SNS and SQS: 'aws-region-num'
2016-05-06 22:13:07,161 INFO SNS topic ARN: 'aws-topic-arn'
2016-05-06 22:13:07,161 INFO SQS queue name: 'aws-queue-arn'
2016-05-06 22:13:07,161 INFO SQS queue wait time (in seconds): '20'
2016-05-06 22:13:07,161 INFO SQS queue polling interval (in seconds): '0'
2016-05-06 22:13:07,161 INFO Cache entries: '100000'
2016-05-06 22:13:07,161 INFO Cache memory size (in bytes): '134217728'
2016-05-06 22:13:07,161 INFO Cache disk size (in bytes): '1073741824'
2016-05-06 22:13:07,161 INFO Cache on disk if file size greater than (in bytes): '0'
2016-05-06 22:13:07,161 INFO Cache check interval (in seconds): '5'
2016-05-06 22:13:07,161 INFO Cache ENOENT rechecks S3: False
2016-05-06 22:13:07,161 INFO AWS Managed Encryption enabled: False
2016-05-06 22:13:07,161 INFO AWS Managed Encryption enabled: False
2016-05-06 22:13:07,161 INFO Number of parallel S3 threads (0 to disable writeback): '32'
2016-05-06 22:13:07,161 INFO Number of parallel downloading threads: '4'
2016-05-06 22:13:07,161 INFO Number download retry attempts: '60'
2016-05-06 22:13:07,161 INFO Download retry sleep time seconds: '1'
2016-05-06 22:13:07,162 INFO Number read retry attempts: '10'
2016-05-06 22:13:07,162 INFO Read retry sleep time seconds: '1'
2016-05-06 22:13:07,162 INFO Number of parallel prefetching threads: '2'
2016-05-06 22:13:07,162 INFO Download buffer size (in KB, 0 to disable buffering): '10485760'
2016-05-06 22:13:07,162 INFO Number of buffers to prefetch: '0'
2016-05-06 22:13:07,162 INFO Write metadata (file system attr/xattr) on S3: 'True'
2016-05-06 22:13:07,162 INFO Download prefetch: 'False'
2016-05-06 22:13:07,162 INFO Multipart size: '104857600'
2016-05-06 22:13:07,162 INFO Multipart maximum number of parallel threads: '4'
2016-05-06 22:13:07,162 INFO Multipart maximum number of retries per part: '3'
2016-05-06 22:13:07,162 INFO Default expiration for signed URLs via xattrs: '2592000'
2016-05-06 22:13:07,162 INFO S3 Request Payer: 'False'
2016-05-06 22:13:07,162 INFO Cache path (on disk): '/tmp/yas3fs-cache'
2016-05-06 22:13:07,215 INFO Unique node ID: 'unique-node-id'
2016-05-06 22:13:07,352 INFO SQS queue name (new): 'aws-queue-arn'
Any thoughts as to why this isn't working? When I had it working under Centos6 it seemed like the perfect solution for storing wordpress uploads across multiple web servers in a load balanced situation.
Best,
Dave
Well, I just figured out a work-around because of this other issue:
#120
In my start script I issue
yas3fs --recheck-s3 s3://$BUCKET $MOUNTDIR before issuing the start command. This seems to work. I'm not sure why the problem exists in the first place, though. Let us know if you figure it out! :) Also, thanks for all your hard work on an otherwise great tool!
Are you trying to mount a bucket over a folder that already has things in it?