Displaying 6 results from an estimated 6 matches for "last_success".
Did you mean:
last_access
2017 Jan 23
2
WERR_SEM_TIMEOUT
...transport_obj_guid :
00000000-0000-0000-0000-000000000000
tmp_highest_usn :
0x0000000000002575 (9589)
highest_usn :
0x0000000000002575 (9589)
last_success : Mon Aug 22
18:50:30 2016 BRT
last_attempt : Mon Jan 23
16:49:24 2017 BRST
result_last_attempt : WERR_SEM_TIMEOUT
consecutive_sync_failures: 0x00000d46
(3398)
Thanks...
2012 Mar 13
2
libvirt with sanlock
...ds (default = 10), because
the sanlock dir is on a GFS2 volume and can be blocked for some time while
fencing and journal recovery takes place.
With the default sanlock io timeout, I get lease timeouts because IO is
blocked:
Mar 5 15:37:14 raiti sanlock[5858]: 3318 s1 check_our_lease warning 79
last_success 3239
Mar 5 15:37:15 raiti sanlock[5858]: 3319 s1 check_our_lease failed 80
So far, all fine, but when I restart sanlock and libvirtd, it takes about 2
* 30 seconds = 1 minute before libvirtd is usable. "virsh list" hangs
during this time. I can still live with that...
But it gets w...
2017 Jan 23
0
WERR_SEM_TIMEOUT
...ansport_obj_guid :
> 00000000-0000-0000-0000-000000000000
> tmp_highest_usn :
> 0x0000000000002575 (9589)
> highest_usn :
> 0x0000000000002575 (9589)
> last_success : Mon Aug
> 22 18:50:30 2016 BRT
> last_attempt : Mon Jan
> 23 16:49:24 2017 BRST
>
> result_last_attempt :
> WERR_SEM_TIMEOUT consecutive_sync_failures: 0x00000d46
> (3398)
You need t...
2017 Jan 24
2
WERR_SEM_TIMEOUT
...>> 00000000-0000-0000-0000-000000000000
>> tmp_highest_usn :
>> 0x0000000000002575 (9589)
>> highest_usn :
>> 0x0000000000002575 (9589)
>> last_success : Mon Aug
>> 22 18:50:30 2016 BRT
>> last_attempt : Mon Jan
>> 23 16:49:24 2017 BRST
>>
>> result_last_attempt :
>> WERR_SEM_TIMEOUT consecutive_sync_failures: 0x00000d46...
2017 Jan 23
3
WERR_SEM_TIMEOUT
Am 23.01.2017 um 12:59 schrieb Carlos A. P. Cunha via samba:
> Em 20-01-2017 18:19, Carlos A. P. Cunha escreveu:
>>
>> Hello
>> I have about 10 Dcs Samba 4.4.4 running on Debian 8, in distinct
>> networks, one of them presents the error:
>>
>> Result 121 (WERR_SEM_TIMEOUT)
>>
>> When I execute the command to check the DRS.
>>
>> Any
2018 Mar 21
3
Replication Failure Issue
Thanks Carlos,
The thing is, that I did not upgrade the version of Samba - that is the next step, so the ports used would not have changed. I only updated the OS.
> On 21/03/2018, at 10:04 PM, Carlos Alberto Panozzo Cunha <carlos.hollow at gmail.com> wrote:
>
> Hi,
> I have same problem after update for samba.
> I allow new ports in firewall.
>
>