Pavan Vilas Sondur wrote: > Hi Ilya, > Can you send us the log files of the nodes in use and also the perl script which triggers this problem. > > Pavan > > On 28/08/09 10:19 +0400, Ilya Galanin wrote: > >> Hello Everyone. >> I am using gluster 2.0.6 on my ftp-cluster on RHEL5. It contains 3 nodes. >> >> This is package list from one node. Other nodes have the same packages >> installed. >> =============================================== >> [ftp1:~]:999# rpm -qa | grep gluster >> glusterfs-common-2.0.6-1.el5.x86_64 >> glusterfs-server-2.0.6-1.el5.x86_64 >> glusterfs-client-2.0.6-1.el5.x86_64 >> [ftp1:~]:1000# rpm -qa | grep fuse >> fuse-libs-2.7.4glfs11-1.x86_64 >> kernel-module-fuse-2.6.18-128.1.1.el5-2.7.4glfs11-1.x86_64 >> fuse-2.7.4glfs11-1.x86_64 >> fuse-devel-2.7.4glfs11-1.x86_64 >> =============================================== >> >> My configuration files: >> Server config: >> =============================================== >> volume posix >> type storage/posix >> option directory /home/automat >> end-volume >> >> volume locks >> type features/locks >> subvolumes posix >> end-volume >> >> volume brick >> type performance/io-threads >> option thread-count 8 >> subvolumes locks >> end-volume >> >> volume server >> type protocol/server >> option transport-type tcp >> option auth.addr.brick.allow * >> subvolumes brick >> end-volume >> =============================================== >> >> Client Config: >> =============================================== >> # file: /etc/glusterfs/glusterfs-client.vol >> # >> volume remote1 >> type protocol/client >> option transport-type tcp >> option remote-host 10.7.69.145 >> option remote-subvolume brick >> end-volume >> >> volume remote2 >> type protocol/client >> option transport-type tcp >> option remote-host 10.7.69.146 >> option remote-subvolume brick >> end-volume >> >> volume remote3 >> type protocol/client >> option transport-type tcp >> option remote-host 10.7.69.147 >> option remote-subvolume brick >> end-volume >> >> volume replicate >> type cluster/replicate >> subvolumes remote1 remote2 remote3 >> end-volume >> >> volume distribute >> type cluster/distribute >> subvolumes replicate >> end-volume >> >> volume writebehind >> type performance/write-behind >> option block-size 128KB >> option cache-size 100MB >> subvolumes distribute >> end-volume >> >> volume cache >> type performance/io-cache >> option cache-size 1024MB >> subvolumes writebehind >> end-volume >> =============================================== >> >> Also I have a perl script that check all files in some folders of >> ftp-server every 10 minutes and >> caclulate their control sum, then write it in xml format to one new file >> on ftp (index.xml) >> >> PS: I run this script on node1 using cron. >> >> Sometimes after deploying some new files on ftp server (node one). >> I see that md5sum of file(index.xml) is different from one node to others. >> Usually node one give right md5sum. Others give wrong ... or one of >> others gives wrong .... >> >> May be someone see that different cluster nodes give different files? >> Any other suggestions and advices are welcome too. >> >> PS. Excuse me for my English, I am not a native speaker. >> >> Thanks in advance. >> Ilya. >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> Crontab line is [ftp1:/var/log/glusterfs]:1006# crontab -lu ftpw */10 * * * * /usr/local/bin/interface-xml-collector-1.sh 1&> /var/log/collector.log Script: #!/bin/bash set -x ROOT_PATH="/home/ftp/automat/" XML_NAME="/index-test.xml" if [ ! -f /tmp/collector.busy ] then touch /tmp/collector.busy cd /usr/local/bin for f in `ls -I *.html $ROOT_PATH` do rm -f $ROOT_PATH"$f"$XML_NAME /usr/bin/perl /usr/local/bin/crc32-collect-1.pl "$ROOT_PATH"$f "$ROOT_PATH"$f"$XML_NAME" diff -I "update lastchange=" -I index.xml "$ROOT_PATH"$f"$XML_NAME" "$ROOT_PATH"$f"/index.xml" if [ $? -ne 0 ] then mv "$ROOT_PATH"$f"$XML_NAME" "$ROOT_PATH"$f"/index.xml" fi; done rm -f /tmp/collector.busy fi Perl script and logs is attached. There was a described problem on ftp2 two days ago (2009-08-25). Also I found some error-s in ftp2-logs at that time after your pointing to see logs. The problem was eliminate by ftp-daemon stop, restarting gluster(client and server) on node2 and startup ftp-daemon again. But I can't do it permanently especially when ftp-cluster is working... Thanks. Ilya. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: crc32-collect-1.pl URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0004.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: home-ftp.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0003.asc> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: -etc-glusterfs-glusterfs-server.vol.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0005.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: -etc-glusterfs-glusterfs-server.vol-ftp2.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0004.asc> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: home-ftp-ftp2.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0006.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: home-ftp-ftp3.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0005.asc> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: -etc-glusterfs-glusterfs-server.vol-ftp3.log URL: <http://gluster.org/pipermail/gluster-users/attachments/20090828/9ceeb21d/attachment-0007.txt>
