Camelia, the Perl 6 bug

IRC log for #gluster, 2013-06-15

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:08 Hchl joined #gluster
00:20 badone joined #gluster
00:28 Hchl joined #gluster
00:41 rb2k_ joined #gluster
01:06 a2_ joined #gluster
01:07 y4m4_ joined #gluster
01:09 a2 joined #gluster
01:12 y4m4 joined #gluster
01:15 rb2k joined #gluster
01:44 satheesh joined #gluster
01:44 brosner joined #gluster
02:14 bulde joined #gluster
02:17 rb2k_ joined #gluster
02:36 vpshastry joined #gluster
02:39 rb2k joined #gluster
02:45 bala joined #gluster
02:48 rb2k_ joined #gluster
03:18 brosner joined #gluster
03:46 Hchl joined #gluster
03:53 vpshastry left #gluster
04:06 hagarth joined #gluster
04:09 bambi23 joined #gluster
04:16 bulde joined #gluster
04:45 roo9 joined #gluster
05:11 hajoucha joined #gluster
05:48 al joined #gluster
06:07 bambi23 joined #gluster
06:13 bambi23 joined #gluster
06:41 FilipeMaia joined #gluster
07:02 Hchl joined #gluster
07:19 vshankar joined #gluster
07:20 vshankar joined #gluster
07:35 ramkrsna joined #gluster
07:38 ramkrsna_ joined #gluster
07:42 joelwallis joined #gluster
08:15 dewey_ joined #gluster
08:30 FilipeMaia joined #gluster
08:38 rb2k joined #gluster
08:41 Hchl joined #gluster
09:21 rb2k_ joined #gluster
09:22 realdannys1 joined #gluster
09:35 Hchl joined #gluster
09:53 Hchl joined #gluster
09:57 rb2k_ joined #gluster
10:10 vpshastry joined #gluster
10:10 vpshastry left #gluster
10:25 Hchl joined #gluster
10:28 FilipeMaia joined #gluster
10:45 Hchl joined #gluster
10:47 FilipeMaia joined #gluster
11:02 FilipeMaia joined #gluster
11:11 kevein joined #gluster
11:18 FilipeMaia joined #gluster
11:21 Hchl joined #gluster
11:39 rb2k joined #gluster
11:45 mohankumar__ joined #gluster
11:46 FilipeMaia joined #gluster
11:50 Goatbert joined #gluster
11:54 vpshastry joined #gluster
11:57 vpshastry left #gluster
12:10 bala joined #gluster
12:56 ccha2 joined #gluster
13:21 rb2k joined #gluster
13:29 yinyin_ joined #gluster
13:29 charlescooke joined #gluster
14:02 RangerRick2 joined #gluster
14:13 bala joined #gluster
14:16 vpshastry1 joined #gluster
14:21 vpshastry1 left #gluster
14:23 mohankumar__ joined #gluster
15:25 Cenbe joined #gluster
15:26 ujjain joined #gluster
15:32 luis_silva joined #gluster
15:35 luis_silva Anyone know if when removing a brick that has a replica peer, if you should run peer detach first or can you just remove the brick while they still have peers?
15:45 Hchl joined #gluster
16:22 Hchl joined #gluster
16:26 rb2k joined #gluster
16:47 vpshastry joined #gluster
16:47 vpshastry left #gluster
16:52 fcami joined #gluster
17:13 xymox joined #gluster
17:23 jag3773 joined #gluster
17:31 hajoucha joined #gluster
17:34 brosner joined #gluster
17:50 rb2k joined #gluster
17:58 vpshastry joined #gluster
18:00 vpshastry left #gluster
18:07 hagarth joined #gluster
18:22 MrNaviPacho joined #gluster
18:44 realdannys1 joined #gluster
18:49 realdannys1 Argh I'm back :( now with the gluster volume successfully mounted on my client, when I publish a post I'm having issues writing to it - i'm getting this...
18:49 realdannys1 Error: Could not create path: ../wp-content/uploads/gravity_forms/1-9e​5dc27086c8b2fd2e48678e1f54f98c/2013/02/g​luster/temp_TMS_51bcb6f7de2e81.01656220
18:50 realdannys1 yet if I navigate to the folder than Gluster is mounted to via my FTP i'm able to uploads folders to it and it has the same 755 permission as my S3 mounted fuse folder next to it which works fine..
18:54 lbalbalba joined #gluster
18:58 mohankumar__ joined #gluster
19:08 andreask joined #gluster
19:11 [1]lbalbalba joined #gluster
19:12 [2]lbalbalba joined #gluster
19:17 realdannys1 anyone?
19:22 lbalbalba realdannys1: i dount i am able to help, but ... i dont understand. please clarify : 'when I publish a post' and 'via my FTP i'm able to uploads folders' ?
19:22 lbalbalba realdannys1: s/dount/doubt
19:23 lbalbalba realdannys1: sounds like : 'when i make a native client glysterfs mount it fails, but when ftp'ing to the same location it works '
19:23 lbalbalba realdannys1: s/glysterfs/glusterfs
19:23 realdannys1 To cut a long story short, users upload files via our website which runs on wordpress they go into the a gluster volume. We then go into the post and click publish - the files on the gluster volume should then be unzipped, processed and uploaded to S3 for when the post goes live. Gluster acts as universal storage solution for uploads between all our EC2 instances keeping the uploads all in sync.
19:24 realdannys1 when I publish or upload a file now, wordpress can seem to put it on gluster - but if I sFTP into my server, I can put things into the gluster folder manually and it works fine
19:25 lbalbalba realdannys1: and wordpress uses ftp 'under the hood' ?
19:26 realdannys1 No I don't think so, but wordpress is just hosted on the server, it should see and be able to write to the folder where gluster is mounted the same as any other folder
19:26 realdannys1 we use fuse to mount S3 on the server too and its able to write and read for that folder fine
19:27 lbalbalba realdannys1: would you be 'emulating' wordpress behaviour by logging on to the host, and copy files to the gluster mountpoint ? or unzipping them there ?
19:28 lbalbalba realdannys1: i havent got a clue, im just trying to see what goes wrong in more detail
19:28 realdannys1 Ok - well if I make the gluster mounted folder on my client have 777 permissions it works with wordpress fine
19:29 realdannys1 however as I said the S3 folder I use which is mounted with fuse too, that works with 755 permissions
19:29 realdannys1 so it seems some permission issue here, Im not comfortable leaving fluster to have 777 permissions
19:30 lbalbalba realdannys1: but wordpress isnt writing to the 'S3 folder' (whatever that is) ?
19:30 realdannys1 yes it is
19:30 realdannys1 it was doing the exact thing we now want to use gluster for
19:32 lbalbalba realdannys1: so 'manually' copying files to the 's3 folder' works, and wordpress access to the s3 folder fails ?
19:32 realdannys1 No
19:32 realdannys1 no, no
19:33 lbalbalba oh
19:33 realdannys1 S3 (as in Amazon S3) is mounted to our server like a drive via Fuse
19:33 realdannys1 basically the same way that Gluster is
19:33 realdannys1 We were using S3 to store the uploads, so they'd be in sync across multiple instances, but S3 is dumb storage, you can't unzip or manipulate files on there without downloading them to your server.
19:34 lbalbalba ok. so: wordpress writing to Amazon S3 works, and wordpress writing to the gluster native client mounted volume fails ?
19:34 realdannys1 so step up Gluster, where we wanted to store uploads but then also trigger the script on the server with gluster server on, where we would unzip the files, process them with FFmpeg if need be and make new zip files then move it all to S3 - taking this burder away from our web server instances.
19:34 realdannys1 yes exactly
19:35 realdannys1 so imagine I have a folder for each, one puts files on Amazon S3, one puts them on Gluster
19:35 realdannys1 Wordpress fails to write to Gluster unless I set the folder as 777, but it'll write to S3 if its at 755
19:35 realdannys1 so somewhere I must be able to change my gluster permissions or something so that I can put the folder to a safer 755 but allow wordpress to write whatever data it wants to Gluster
19:36 lbalbalba long shot: what user (and groups) is the wordpress process running as, and what group is the gluster mount point
19:39 realdannys1 I wish I could find out what user wordpress is running as
19:39 realdannys1 that would probably be my answer right there - I'm trying to google to find out
19:40 lbalbalba uuhhmm... log ojn to to the host using ssh and run 'ps -ef | grep wordpress' or something similar ?
19:41 lbalbalba or perhaps its just http or jboss or something
19:44 lbalbalba or... wordpress is using the userid of the person that logged into wordpress to write to the filesystem ?
19:44 realdannys1 root      5224  4906  0 15:44 pts/0    00:00:00 grep wordpress
19:44 realdannys1 would suggest wordpress is just running as root then?
19:44 lbalbalba no. thats your 'grep' command. you logged in as 'root' ?
19:45 realdannys1 oh yeah I am
19:46 lbalbalba perhaps we should take another approach. can you retreive the permissions of the Amazon S3 folder ?
19:46 lbalbalba and then apply then to the gluster mount, of course
19:50 realdannys1 Yes its 755
19:50 realdannys1 both it and the gluster amount were 755
19:51 realdannys1 Wordpress could only write to the S3 folder though
19:51 lbalbalba no i mean user and group 'ls -al s3 folder'
19:56 ctria joined #gluster
19:56 realdannys1 ok, so I've got this for the gluster folder (which is currently set to 777) [root@ip-10-202-210-190 glusterfs]# ls -al /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/gluster
19:56 realdannys1 total 6683
19:56 realdannys1 drwxrwxrwx 4 root  root      192 Jun 15 15:27 .
19:56 realdannys1 drwxr-xr-x 6 nginx nginx    4096 Jun 12 14:45 ..
19:57 realdannys1 and the S3 mounted folder just starts returning file names straight away
19:57 realdannys1 [root@ip-10-202-210-190 glusterfs]# ls -al /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/mixtape2
19:57 realdannys1 total 54
19:57 realdannys1 ---------- 1 root root 54960 Apr 26 06:49 1cbc07014cc4e998724ecbd70830f7e4.jpeg
19:58 realdannys1 drwxr-xr-x 1 root root     0 Apr 26 06:38 TMS_517a5933b44f70.84241273
19:59 lbalbalba ok, lets see. your glusterfs mountpoint is 'nginx:nginx', and the amazons3 folder 'root:root' ?
20:00 lbalbalba 'chown -R root:root glystermountpoint' ?
20:00 lbalbalba logged in as root, of course. but you have that
20:03 lbalbalba it 'appears to be' a 'simple' file permission issue. but i cant seem to find the right userid/group permissions
20:04 realdannys1 ok I just ran chown
20:04 realdannys1 and then ls -al again
20:04 realdannys1 but its still reporting
20:04 realdannys1 [root@ip-10-202-210-190 glusterfs]# ls -al /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/gluster
20:04 realdannys1 total 6683
20:04 realdannys1 drwxrwxrwx 4 root  root      192 Jun 15 15:27 .
20:04 realdannys1 drwxr-xr-x 6 nginx nginx    4096 Jun 12 14:45 ..
20:05 lbalbalba 'ls -al /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/gluster' is the mountpoint ? try 'ls -ald mountpoint'
20:06 realdannys1 as in 'ls -ald gluster' ??
20:06 lbalbalba yeah
20:06 realdannys1 that full file path is the gluster mount point yet
20:06 realdannys1 *yes
20:07 realdannys1 so you want me to just run 'ls -ald' with just the end folder name in it not the full path?
20:07 lbalbalba full path is good
20:07 lbalbalba guess its root:root
20:08 realdannys1 ah ok, got you
20:08 realdannys1 [root@ip-10-202-210-190 var]# ls -ald /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/gluster
20:08 realdannys1 drwxrwxrwx 4 root root 207 Jun 15 16:04 /var/www/vhosts/i-16852366/wp-content​/uploads/gravity_forms/1-9e5dc27086c8​b2fd2e48678e1f54f98c/2013/02/gluster
20:08 realdannys1 yes its root:root
20:09 lbalbalba its likely a 'simple' file permission issue. but i cant figure it out. sorry, its been too long ago since i had to deal with unix file permissions.
20:10 lbalbalba anybody else ? help ?
20:10 manik joined #gluster
20:11 lbalbalba it looks like the entire dir path needs to be writable for the root user. but im not about to lket you run that command
20:12 realdannys1 yeah - its weird that nginx:nginx shows up for .. and root:root for . I don't even know what that means
20:12 realdannys1 I'm not experienced enough in linux to know
20:13 lbalbalba .. is the parent dir
20:14 lbalbalba tjhe entiure path needs to be group root , it seems 'ls -ald /var', 'ls-ald /var/www/', ls -ald /var/www/vhosts/', etc. all need root:root, it seems
20:16 lbalbalba but you shouldnt run those chown commands yet. i may fuck up your system, and i dont want to do that ;)
20:17 lbalbalba . is the current dir
20:18 lbalbalba root:root mean user:group, as in root is the user owning the dir, and root the group owning the dir
20:19 lbalbalba or in nginx:nginx, nginx user ownership of the dir/file, and nginx the group ownership of the dir/file
20:23 lbalbalba but your web/http server may be running as 'nginx', so just changing the permissions to root will probably not help you (the http/nginx server may nit have access after that)
20:24 lbalbalba oh. how about adding 'root' to the 'nginx' group ?
20:25 brosner joined #gluster
20:30 lbalbalba 'usermod -a -G nginx root'
20:30 lbalbalba when ssh log into the wordpress system as root
20:33 lbalbalba that should work
20:42 lbalbalba perm 755 group nginx, adding root to group nginx
20:43 lbalbalba or perm 775 group nginx, adding root to group nginx
20:44 lbalbalba oh, well. sorry i wasnt able to solve this for you. perhaps someone else can. im gonna crawl back under the rock i came from now.
20:45 * lbalbalba crawls back under rock
20:59 hagarth joined #gluster
21:45 realdannys1 haha sorry Ibalbalba: I didn't see your further suggestions until now - thanks for your help, I will try adding root to nginx suggestion
22:01 ccha2 joined #gluster
22:06 bennyturns joined #gluster
22:44 realdannys1 Well, if anyone else knows why I have to set my gluster mounted folder to 777 permissions on my client to allow wordpress to write to it, please let me know, above suggestions didn't work, don't like leaving it at 777
23:06 badone joined #gluster
23:24 brosner joined #gluster
23:31 StarBeast joined #gluster
23:42 MrNaviPa_ joined #gluster
23:59 brosner joined #gluster

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary