Displaying 6 results from an estimated 6 matches for "8cc9".
Did you mean:
8c99
2006 Mar 02
2
TIMESTAMP, DATETIME not working
...utput of certain variables, for use in file
naming etc, certain key ones appear to fail.
exten => 5555,1,NoOp(${EPOCH})
Returns
-- Executing NoOp("SIP/200-638c", "1141352935") in new stack
exten => 5556,1,NoOp(${TIMESTAMP})
Returns
-- Executing NoOp("SIP/200-8cc9", "") in new stack
exten => 5557,1,NoOp(${DATETIME})
Returns
-- Executing NoOp("SIP/200-83ca", "") in new stack
Epoch works fine, however none of the other "human" readable timestamps
seem to be working. Is there anything else required to initia...
2017 Oct 24
2
brick is down but gluster volume status says it's fine
.../vols/digitalcorpora/run/gluster-2-export-brick7-digitalcorpora.pid
> -S /var/run/gluster/f8e0b3393e47dc51a07c6609f9b40841.socket --brick-name
> /export/brick7/digitalcorpora -l
> /var/log/glusterfs/bricks/export-brick7-digitalcorpora.log --xlator-option
> *-posix.glusterd-uuid=032c17f5-8cc9-445f-aa45-897b5a066b43 --brick-port
> 49154 --xlator-option digitalcorpora-server.listen-port=49154)
> [2017-10-24 17:18:59.285279] I [MSGID: 101190]
> [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread
> with index 1
> [2017-10-24 17:19:04.611723] I
> [rpcsvc...
2017 Oct 24
0
brick is down but gluster volume status says it's fine
...ter-2-
>> export-brick7-digitalcorpora.pid -S /var/run/gluster/
>> f8e0b3393e47dc51a07c6609f9b40841.socket --brick-name
>> /export/brick7/digitalcorpora -l /var/log/glusterfs/bricks/
>> export-brick7-digitalcorpora.log --xlator-option *-posix.glusterd-uuid=
>> 032c17f5-8cc9-445f-aa45-897b5a066b43 --brick-port 49154 --xlator-option
>> digitalcorpora-server.listen-port=49154)
>> [2017-10-24 17:18:59.285279] I [MSGID: 101190] [event-epoll.c:629:event_dispatch_epoll_worker]
>> 0-epoll: Started thread with index 1
>> [2017-10-24 17:19:04.611723] I [...
2017 Oct 26
0
not healing one file
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
2017 Oct 26
3
not healing one file
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
2017 Oct 26
2
not healing one file
...n.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed metadata selfheal on 06df930e-6bb5-49ff-aac4-fccf21db9061. sources=0 [2] sinks=1
[2017-10-25 10:40:25.425776] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 8451e180-330e-49b4-8cc9-dd341fbf97ac. sources=0 [2] sinks=1
[2017-10-25 10:40:25.427280] I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do] 0-home-replicate-0: performing metadata selfheal on 8451e180-330e-49b4-8cc9-dd341fbf97ac
[2017-10-25 10:40:25.430449] I [MSGID: 108026] [afr-self-heal-common...