similar to: Segfaults after upgrade to GlusterFS 3.10.9

Hi Frank, It will be very easy to debug if u have core file with u. It looks like crash is coming from gfapi stack. If there is core file can u please share bt of the core file. Regards, Jiffin On Thursday 18 January 2018 11:18 PM, Frank Wall wrote: > Hi, > > after upgrading to 3.10.9 I'm seing ganesha.nfsd segfaulting all the time: > > [12407.918249] ganesha.nfsd[38104]:

Hello All, I am trying to setup a three way replicated Gluster Storage which is exported by NFS Ganesha. This 3 node Ganesha cluster is managed by pacemaker and corosync. I want to use this cluster as a backend for several different web-based applications as well as storage for mailboxes. The cluster is working well but after triggering the failover by stopping the ganesha service on one node,

I am trying to get up geo replication between two gluster volumes I have set up two replica 2 arbiter 1 volumes with 9 bricks [root at gfs1 ~]# gluster volume info Volume Name: gfsvol Type: Distributed-Replicate Volume ID: c2fb4365-480b-4d37-8c7d-c3046bca7306 Status: Started Snapshot Count: 0 Number of Bricks: 3 x (2 + 1) = 9 Transport-type: tcp Bricks: Brick1: gfs2:/gfs/brick1/gv0 Brick2:

On 09/29/2017 09:30 PM, rick sanchez wrote: > I am trying to get up geo replication between two gluster volumes > > I have set up two replica 2 arbiter 1 volumes with 9 bricks > > [root at gfs1 ~]# gluster volume info > Volume Name: gfsvol > Type: Distributed-Replicate > Volume ID: c2fb4365-480b-4d37-8c7d-c3046bca7306 > Status: Started > Snapshot Count: 0 > Number

Just installed Nexenta and I''ve been playing around with zfs. root at hzsilo:/tank# uname -a SunOS hzsilo 5.11 NexentaOS_20070105 i86pc i386 i86pc Solaris root at hzsilo:/tank# zfs list NAME USED AVAIL REFER MOUNTPOINT home 89.5K 219G 32K /export/home tank 330K 1.78T 51.9K /tank tank/iscsi_luns 147K

Team, **Please respond to me and my coworker listed in the Cc, since neither one of us are on this alias** QUICK PROBLEM DESCRIPTION: Cu created a dataset which contains all the zvols for a particular zone. The zone is then given access to all the zvols in the dataset using a match statement in the zoneconfig (see long problem description for details). After the initial boot of the zone

I bought a UTStarcom F1000 WiFi IP Phone from http://www.luxoncomm.com and tested it with Asterisk. This is a my first impression of the device. The F1000 supports SIP. It looks and operates like a cell phone, and connects to the Internet through WiFi, so you can use it at any WiFi hotspot. I set up a 802.11b wi-fi network with a Linksys BEFW11S4 Wireless-B broadband router with no security

Hi list, I bought two UTStarcom F1000 phones, pre-equipped with the latest firmware, including WPA support. Those are configured to register to an asterisk server on the internet (not LAN), and registration works. Calling and being called also, with transfer and all bells and whistles. After a few minutes up to 5 hours (varies widely), the display tells me that an Accesspoint is not available

The Gluster community is pleased to announce the release of Gluster 3.10.9 (packages available at [1]). Release notes for the release can be found at [2]. We are still working on a further fix for the corruption issue when sharded volumes are rebalanced, details as below. * Expanding a gluster volume that is sharded may cause file corruption - Sharded volumes are typically used for VM

Has anyone had any luck configuring the UTStarCom F1000 with asterisk? I get the wireless to work but the sip registration is a problem. Below is my SIP Debug. The server is 192.168.0.80 and the phone is 192.168.0.166. Sip.conf: [f1000_1] type=friend host=dynamic defaultip=192.168.0.166 port=5060 secret=mysecret ;auth=md5 username=f1000_1 qualify=yes

Hi all, I' m currently testing a Wifi UT Starcom F1000 and for my taste even with the audio volume level even on max. setting, the speaker is not loud enogh. Is there a way to raise the audio-level specifically for a concrete SIP device via a sip.conf setting or something like that ?? TIA, Bruno

Hi Jiffin, On Fri, Jan 19, 2018 at 09:19:45AM +0530, Jiffin Tony Thottan wrote: > It will be very easy to debug if u have core file with u. It looks like > crash is coming from gfapi stack. > > If there is core file can u please share bt of the core file. I'm sorry, there are no core files. :( Is there something I could do to trigger the creation of core files? Or anything else

What's /proc/sys/kernel/core_pattern set to for you? For me it is % cat /proc/sys/kernel/core_pattern core which will drop a core file in the working directory of the process. On 19/01/2018 12.56, Frank Wall wrote: > Is there something I could do to trigger the creation of core files?

Can anybody help me on configuring utstarcom F1000 on asterisk? Is there a way to do it or is it impossible? ___________________________________________________________________________ Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o

I have 8 - F1000G utstar phones. on a couple of them I can configure them by the WEB interface with no problem. On a couple of the them I cannot. I get no response when I point the browser to them. THe units work. keypad is fine. I can examine the network values - specifically the DHCP address. etc... Just cant get the web interface to do anything. Has anyone had this issue and know how to

Hi there, I am trying desperatly to register my WiFi Phone UTStarcomm F1000 with my asterisk server. I already changed the name of the user to "anonymous" since it looks like the phone sends that name. The WiFi Phone's IP is 192.168.1.217, the asterisk server's IP is 192.168.1.200 What is it that I am missing? Any help very much appreciated!!! The error message I get is: Jan

Before I undertake this upgrade I thought I would see if anyone has any advice on how to do this on a production system. Maybe someone has already "fought this dragon". Current config Gluster V3.0.0. This has been in production for over 16 months: 2 servers with 8 x 2TB hard drives (bricks) replicated svr1:vol1 <-> srv2:vol1 -> rbrick1 svr1:vol2 <-> srv2:vol2 ->

Pretty close to what i have that : [global] workgroup = PRIVATE server string = %h server log file = /var/log/samba/log.%m max log size = 1000 log level = 0 ####### Authentication ####### ## stand alone everything open. security = user guest ok = yes map to guest = bad password ## map id's outside to domain to tdb files. idmap config * : backend = tdb idmap

Hello, I`m experiencing major problems after having migrated from Novell to SLES 9. My server configuration: - SLES 9.0, running on an Intel XEON machine - Samba 3.0.14a, standard bin package with ACL support - XFS as filesystem, with ACL support - Users are members of max. 40 Groups My client configuration: - running Windows 98 up to Windows XP SP2, everything included - Office 97 up to 2003

On 20/07/2020 14:53, L.P.H. van Belle via samba wrote: > Pretty close to what i have that : > > [global] > workgroup = PRIVATE > server string = %h server > log file = /var/log/samba/log.%m > max log size = 1000 > > log level = 0 > ####### Authentication ####### > ## stand alone everything open. > security = user > guest ok = yes