Displaying 7 results from an estimated 7 matches for "9c43".
Did you mean:
9943
2006 Sep 14
2
Forcing Marker bit, because SSRC has changed
Evnin...
Googled around for this strange error meesage with no
helpful results at all...
Does somebody has any idea what this means?
"Forcing Marker bit, because SSRC has changed"
At the same time I only get inbound audio but other
side can't hear me...sometimes I just hear my echo
and nothing from other side...
Asterisk version 1.2.9 and both participants with
public IP
2016 Jul 07
3
no boot, no message
...MENU LABEL Gentoo
LINUX ../gentoo/vmlinuz
APPEND root=/dev/sda2
# APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
#
#LABEL gentoo
# MENU LABEL Gentoo
# LINUX ../gentoo/vmlinuz
## APPEND root=/dev/sda1
# APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
#
LABEL gentoo_uuid
MENU LABEL Gentoo (UUID)
LINUX ../gentoo/vmlinuz
# APPEND root=/dev/sda2
APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
MENU SEPARATOR
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL poweroff...
2016 Jul 07
0
no boot, no message
...o/vmlinuz
> APPEND root=/dev/sda2
> # APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
>
> #
> #LABEL gentoo
> # MENU LABEL Gentoo
> # LINUX ../gentoo/vmlinuz
> ## APPEND root=/dev/sda1
> # APPEND root=PARTUUID=645c1577-e5d7-41eb-9c43-bfee52088197
> #
>
> LABEL gentoo_uuid
> MENU LABEL Gentoo (UUID)
> LINUX ../gentoo/vmlinuz
> # APPEND root=/dev/sda2
> APPEND root=UUID=b2bbb1f8-972f-401c-9515-df3483834185
>
>
>
>
> MENU SEPARATOR
>
> LABEL reboot
>...
2016 Jul 07
3
no boot, no message
I have syslinux 5.10 on a 32bit gentoo system. It boots fine. Now I
installed another linux system in other partitions of the same drive
(a 64 bit system), updated syslinux.cfg, setup the new system as
default, and the new entry appears in the menu. Problem is: it doesn't
boot. On timeout, it starts counting down again, and that's it. No
error message whatsoever. Selecting the old system
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 548ed660-d23b-470f-9e55-3d1be031d72a. sources=0 [2] sinks=1
[2017-10-25 10:40:22.193721] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on 2694b5e4-a7d9-4df6-9c43-9b97375f7803. sources=0 [2] sinks=1
[2017-10-25 10:40:22.223046] I [MSGID: 108026] [afr-self-heal-common.c:1327:afr_log_selfheal] 0-home-replicate-0: Completed data selfheal on d6fb0d65-5a09-4098-b46b-80577ab49845. sources=0 [2] sinks=1
[2017-10-25 10:40:22.226075] I [MSGID: 108026] [afr-self-h...