similar to: total outage - almost

Hi, I checked the attributes of one of the files with I/O errors root at chastcvtprd04:~# getfattr -d -e hex -m - /data/glusterfs/Server_Standard/1I-1-14/brick/Server_Standard/CV_MAGNETIC/V_1050932/CHUNK_11126559/SFILE_CONTAINER_014 getfattr: Removing leading '/' from absolute path names # file:

http://guides.rubyonrails.org/getting_started.html#getting-up-and-running create a controller called PostsController. You can do this by running this command: $ rails g controller posts That results in an error. >rails g controller posts Usage: rails new APP_PATH [options] Options: What am I missing? -- You received this message because you are subscribed to the Google Groups

On Sat, 14 Oct 2017, Rowland Penny via samba wrote: > On Sat, 14 Oct 2017 05:33:31 -0400 (EDT) > me at tdiehl.org wrote: > >> On Fri, 13 Oct 2017, Rowland Penny via samba wrote: >> >>> On Fri, 13 Oct 2017 11:45:43 +0200 >>> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: >>> >>>> Hai, >>>>

Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and having a problem with call transfers using the cmds AgentCallBackLogin and AgentLogin First Case (using cmd AgentCallbacklogin): When the incoming call comes and enters the queue, the agent logged in answer the call. But when I try to transfer this call to another agent, the incoming call is dropped. I don?t receive any error

Which kind of transfer do you use? Try using the # transfer. Hope that helps.. Guido Hecken -----Urspr?ngliche Nachricht----- Von: Diego Magalh?es [mailto:diego@redetaho.com.br] Gesendet: Mittwoch, 2. Februar 2005 17:21 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] AgentLogin / AgentCallbackLogin transfer problem Hello guys, I?m running Asterisk CVS-HEAD-02/01/05-12:22:46 and

Hmm i found the problem... I?m using a Grandstream BT100. The transfer just works in a queue if I first acknowledged the call using the # key, and then press the TRANSFER key in the Grandstream. In the asterisk console I receive a: -- SIP/4002-4563 acknowledged Then I can transfer the call... Weird because i?m using ackcall=NO in agents.conf ... Diego Magalh?es diego@redetaho.com.br +55 24

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

This is fresh install of CentOS v6 and Xen v4.1 on a new Dell server following the tutorial posted at: http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial   Every thing went just fine, yet virbr0 won''t work and when I run brctl show I get the following error message:   [root@pe1950 ~]# brctl show bridge name     bridge id               STP enabled     interfaces virbr0         

Hi, Thanks for your reply . I am attaching the files needed by you herewith. The NAT device is called Pronto gateway which has two interfaces , namely eth0 and eth1. ''eth0'' has an ip address of 203.124.152.66 and eth1 has an ip address of 192.168.1.3 . All the client PCs are in 192.168.1.0 network [behind the NAT, the Pronto gateway] and use 192.168.1.3 as the default

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp