Displaying 6 results from an estimated 6 matches for "4a05".
Did you mean:
405
2020 Feb 04
2
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...k and face
problem on incoming calls: they are ended like in Asterisk 16
[2020-02-04 19:19:48] ERROR[3768][C-00000001]: stasis_bridges.c:199
bridge_topics_init: Bridge id initialization required
[2020-02-04 19:19:48] WARNING[3768][C-00000001]: bridge.c:809
bridge_base_init: Bridge da3bd3d1-cdea-4a05-8b3d-0ded8c561c5f: Could not
initialize topics
Asterisk 13
[2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c: Bridge
id initialization required
[2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
0e8746e2-43e4-4c7c-9df8-32d7fe6e3727: Could not initialize topics
Swi...
2020 Feb 04
0
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...incoming calls: they are ended like in Asterisk 16
>
> [2020-02-04 19:19:48] ERROR[3768][C-00000001]: stasis_bridges.c:199
> bridge_topics_init: Bridge id initialization required
> [2020-02-04 19:19:48] WARNING[3768][C-00000001]: bridge.c:809
> bridge_base_init: Bridge da3bd3d1-cdea-4a05-8b3d-0ded8c561c5f: Could not
> initialize topics
>
> Asterisk 13
>
> [2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c: Bridge
> id initialization required
> [2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
> 0e8746e2-43e4-4c7c-9df8-32d7fe6e372...
2020 Feb 04
1
Asterisk 13.31.0 and 16.8.0 - Bridge problem on incoming calls
...they are ended like in Asterisk 16
>
> [2020-02-04 19:19:48] ERROR[3768][C-00000001]: stasis_bridges.c:199
> bridge_topics_init: Bridge id initialization required
> [2020-02-04 19:19:48] WARNING[3768][C-00000001]: bridge.c:809
> bridge_base_init: Bridge da3bd3d1-cdea-4a05-8b3d-0ded8c561c5f:
> Could not
> initialize topics
>
> Asterisk 13
>
> [2020-02-04 19:16:14] ERROR[17133][C-0000002b] stasis_bridges.c:
> Bridge
> id initialization required
> [2020-02-04 19:16:14] WARNING[17133][C-0000002b] bridge.c: Bridge
&g...
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
...F97CDA584D59D516B269323521CC3936D496 (e02a8b9b-6b93-4f12-abdf-cf716e2bc652) on home-client-2
[2017-10-25 10:14:12.310381] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/B3857D3BD45085F6DA0FF3A502CF388A5764A052 (1ac15de5-7f4b-44da-9f76-974e92b94d16) on home-client-2
[2017-10-25 10:14:12.330767] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/ADFFEFF5C34202705A66703CF4A3A372BC83C369 (6981b1d5-c775-49ad-94f7-8a5e...