On Срд, 09 жні 2023, Harry G Coin wrote:
On 8/9/23 01:00, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
Thanks for your help. Details below. The problem 'moved' in I
hope a diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrot
On 8/9/23 21:13, Harry G Coin wrote:
On 8/9/23 12:05, Thierry Bordaz wrote:
On 8/9/23 18:55, Harry G Coin wrote:
Theirry asked for a recap summary below, so forgive the 'top post'.
Here it is:
4.9.10 default install on two systems call them primary (with
kasp.db) and secondary but other
On 8/9/23 12:05, Thierry Bordaz wrote:
On 8/9/23 18:55, Harry G Coin wrote:
Theirry asked for a recap summary below, so forgive the 'top post'.
Here it is:
4.9.10 default install on two systems call them primary (with
kasp.db) and secondary but otherwise multi-master, 1g link between
them
On 8/9/23 18:55, Harry G Coin wrote:
Theirry asked for a recap summary below, so forgive the 'top post'.
Here it is:
4.9.10 default install on two systems call them primary (with kasp.db)
and secondary but otherwise multi-master, 1g link between them,
modest/old cpu, drives, 5Gmemory, with
Theirry asked for a recap summary below, so forgive the 'top post'.
Here it is:
4.9.10 default install on two systems call them primary (with kasp.db)
and secondary but otherwise multi-master, 1g link between them,
modest/old cpu, drives, 5Gmemory, with dns/dnssec and adtrust (aimed at
local
On 8/9/23 17:15, Harry G Coin wrote:
On 8/9/23 01:00, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
Thanks for your help. Details below. The problem 'moved' in I hope
a diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrote:
On 8/9/23 01:00, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
Thanks for your help. Details below. The problem 'moved' in I hope
a diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrot
On 8/9/23 2:00 AM, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
Thanks for your help. Details below. The problem 'moved' in I hope
a diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wr
On Аўт, 08 жні 2023, Harry G Coin wrote:
Thanks for your help. Details below. The problem 'moved' in I hope a
diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
On 8/8/23 02:43, Alexander Bokovoy wrot
Thanks for your help. Details below. The problem 'moved' in I hope a
diagnositcally useful way, but the system remains broken.
On 8/8/23 08:54, Alexander Bokovoy wrote:
On Аўт, 08 жні 2023, Harry G Coin wrote:
On 8/8/23 02:43, Alexander Bokovoy wrote:
pstack $(pgrep ns-slapd) > ns-slapd l
On Аўт, 08 жні 2023, Harry G Coin wrote:
On 8/8/23 02:43, Alexander Bokovoy wrote:
pstack $(pgrep ns-slapd) > ns-slapd log
Tried an upgrade from 4.9.10 to 4.9.11, the "writeback to ldap failed"
error moved from the primary instance (on which the dns records were
being added) to the replica w
On 8/8/23 02:43, Alexander Bokovoy wrote:
pstack $(pgrep ns-slapd) > ns-slapd log
Tried an upgrade from 4.9.10 to 4.9.11, the "writeback to ldap failed"
error moved from the primary instance (on which the dns records were
being added) to the replica which hung in the same fashion. Here's th
On Пан, 07 жні 2023, Harry G Coin via FreeIPA-users wrote:
This January, Mark Potter first experienced what is now killing my new
freeipa setup as well. Once the primary server on which dns records
are being programatically added sees named-pcks11 putting "writeback
to ldap failed" in the log
13 matches
Mail list logo
