similar to: I gonna understand one day

On 4/11/2018 11:54 AM, Alex K wrote: Hey Guy's, Returning to this topic, after disabling the the quorum: cluster.quorum-type: none cluster.server-quorum-type: none I've ran into a number of gluster errors (see below). I'm using gluster as the backend for my NFS storage. I have gluster running on two nodes, nfs01 and nfs02. It's mounted on /n on each host. The path /n is

I've run into a problem with Gluster stability with the RDMA transport. Below is a description of the environment, a simple script that can replicate the problem, and log files from my test system. I can work around the problem by using the TCP transport over IPoIB but would like some input onto what may be making the RDMA transport fail in this case. ===== Symptoms ===== - Error from test

Dear Timo et all, I wanted to put dovecot on production on my real server but, be it with the beta1 you left on my machine yesterday on beta2, when I launch dovecot, I have tons of messages in syslogs like : imap-login: can't connect to auth server at default: Connection refused. What did I do wrong?? TIA -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des

I am trying to run GlusterFS on only my internal interfaces. I have setup two bricks and have a replicated volume that is started. Everything works fine when I run with no transport.socket.bind-address defined in the /etc/glusterfs/glusterd.vol file, but when I add it I get: Transport endpoint is not connected My configuration looks like this: volume management type mgmt/glusterd

Hello, I'm having problems when write-behind is enabled on Gluster 3.8.4. I have 2 Gluster servers each with a single brick that is mirrored between them. The code causing these issues reads two data files each approx. 128G in size. It opens a third file, mmap()'s that file, and subsequently reads and writes to it. The third file, on sucessful runs (without write-behind enabled)

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

Hi, I run a fully updated CentOS 4.4 machine. This morning I got the errors below in my daily Logwatch report (Sendmail part). What has happend? Just some new bogus spammer that cant get the protocol right or is the server under attack? I have googled around but cannot fins any answer or I just suck at googleing... Any ideas ? Jens --------------------- sendmail Begin

Hi, I'm running a mixed Debian Woody/Sarge system with Dovecot version: (0.99.12-1) I can't seem to be able to get dovecot working with mysql. It seems to authenticate successfully then crash. This happens when I use the Debian package and also when I've compiled from source. dovecot: Jan 06 12:21:14 Info: Dovecot starting up dovecot-auth: Jan 06 12:21:15 Info: MySQL: connected to

On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > Hello Atin, > > I've gotten around to this and was able to get upgrade done using 3.7.0 > before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really made optional and > nfs-ganesha is being recommended. We have plans to

Hello folks. We've got a wierd Problem at a customer server. The Server was running fine until tomorrow morning... My problem is that i have no idea where to begin my search for a solution. The Server is used as a Primary Domain Controller and worked just fine. here you see what cat /var/log/message | grep smbd is trying to tell me: First i have a lot of lines like this: Nov 20 04:04:12 dc

Hi list , I'm doing some tests with asterisk 13.4 and tls, and failed to make it work, all my terminals spa Cisco 5XX look my cli [Jul 8 11:09:16] ERROR[14733]: pjsip:0 <?>: tlsc0x7f539801 TLS connect() error: Connection refused [code=120111] [Jul 8 11:09:16] WARNING[14733]: pjsip:0 <?>: tsx0x7f53a8008 Failed to send Request msg OPTIONS/cseq=48024 (tdta0x7f53c000dcb0)!

I believe the peer rejected issue is something we recently identified and has been fixed through https://bugzilla.redhat.com/show_bug.cgi?id=1544637 and is available in 3.12.6. I'd request you to upgrade to the latest version in 3.12 series. On Mon, Feb 19, 2018 at 12:27 PM, <rwecker at ssd.org> wrote: > Hi, > > I have a 3 node cluster (Found1, Found2, Found2) which i wanted

Hi, I'm running glusterFS 3.3.1 on Centos 6.4. ? Gluster volume status Status of volume: glustervol Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick KWTOCUATGS001:/mnt/cloudbrick 24009 Y 20031 Brick KWTOCUATGS002:/mnt/cloudbrick

Sorry for big attachment in previous mail...last 1000 lines of those logs attached now. On Mon, May 29, 2017 at 4:44 PM, Pawan Alwandi <pawan at platform.sh> wrote: > > > On Thu, May 25, 2017 at 9:54 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: > >> >> On Thu, 25 May 2017 at 19:11, Pawan Alwandi <pawan at platform.sh> wrote: >>

Fwd.ing to Gluster users, in the hope that many more people can see this and hopefully can provide any clues thanx, deepak -------- Original Message -------- Subject: [Gluster-devel] Seeing non-priv port + auth issue in the gluster brick log Date: Sat, 11 May 2013 12:43:20 +0530 From: Deepak C Shetty <deepakcs at linux.vnet.ibm.com> Organization: IBM India Pvt. Ltd. To: Gluster

Hi, our window file server running 3.0.25b-33 (X64) (Sernet rpm) on SLES 9 SP3 has been stoped working. The log file shows nothing new. No error ... Only the clients can not connect to the server. After a restart of smbd it seems to work for a while. Any idea ? Any help is welcome !! ---------The last logline before was 10:39; at10:42 no connection was possible----- Jan 7 10:42:30 modena

I just finished setting up a test Dovecot server (1.0-rc15, Solaris 10) and noticed upon start of Dovecot (after rebooting the server) that the imap-login and pop3-login processes spew errors as follows, which I can only assume is due to the fact that dovecot-auth has not fully initialized yet... it seems to me that these login processes are getting started too early, or should at least be

Hi, I have a 3 node cluster (Found1, Found2, Found2) which i wanted to upgrade I upgraded one node from 3.8.15 to 3.12.5 and now i am having multiple problems with the install. The 2 nodes not upgraded are still working fine(Found1,2) but the one upgraded has Peer Rejected (Connected) when peer status is run but it also has multiple brick that have "Transport endpoint is not connected"

Hello Atin, I've gotten around to this and was able to get upgrade done using 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. On 3.11 though I notice that gluster/nfs is really made optional and nfs-ganesha is being recommended. We have plans to switch to nfs-ganesha on new clusters but would like to have glusterfs-gnfs on existing clusters so a seamless upgrade

I was trying to configure postfix, mysql with dovecot. The postfix part is fine, but dovecot seems cannot cannot read the mail directory dovecot: Apr 09 16:22:37 Info: Dovecot starting up dovecot-auth: Apr 09 16:22:38 Info: MySQL: connected to localhost dovecot-auth: Apr 09 16:22:38 Info: Login process 7 connected dovecot-auth: Apr 09 16:22:38 Info: Login process 8 connected dovecot-auth: Apr 09