date:20220324

Re: Help configuring internal network

2022-03-24 Thread Samuel Sieb


On 3/24/22 20:34, Michael Hennebry wrote:

On Sun, 20 Mar 2022, R. G. Newbury wrote:

On 2022-03-20 8:00 a.m., Tim >R. G. 
Newbury wrote:

edit your /etc/hosts file to give the hdhomerun unit a fixed IP
address.

When has the /etc/hosts file ever given anything an IP address?


You are correct, and I am completely wrong. A static address for the 
computer would be set by editing 
/etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the 
network config gui to do the same thing.


Huh?

 From man hosts:


That's not *giving* anything an IP address.  It's assigning a name for 
the local host to be able to *lookup* an IP address.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

2022-03-24 Thread R. G. Newbury



DJ Delorie  wrote


Geoffrey Leach  writes:

Is there a 'Getting Started With pipewire' and/or wireplumber
somewhere? Or should they 'just work' and I need to check my
connections?


As a non-gnome (and non-display-manager) user, I share these .xsession
snippets:

# Required by pipewire, at least
export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)

# Required by most things
eval `dbus-launch --sh-syntax --exit-with-session`

pipewire &
pipewire-pulse &
(sleep 2 ; wireplumber & ) &


There wasn't a pipewire-specific config; it uses the same ALSA backend
as pulseaudio used.


If you don't mind answering, was it a Rhode Island Red cockerel or a hen 
which you sacrificed to learn these arcane secrets? And, full-moon at 
midnight, or dark of the moon? Or did this take moving up to a goat?
Or are you a graduate of Hogwarts? Because I am quite sure that none of 
these snippets show up anywhere in the so-called documentation. Pure 
magic, just like any sufficiently advanced technology.


Geoff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

2022-03-24 Thread R. G. Newbury


Geoffrey Leach  wrote:


I'm happy for you. For me, not so much :-(


I've just installed Fedora 35 and have discovered to my dismay that
previously-working (not at all sophisticated) audio no longer works.

Is there a 'Getting Started With pipewire' and/or wireplumber somewhere?

Or

should they 'just work' and I need to check my connections?

Bob Marcan wrote:
systemctl --user --now disable  wireplumber
works for me.
Obviously we are guinea pigs for this premature piece of software.


Could not agree more with the last sentence. To get audio recognized
in order I did this:
systemctl stop wireplumber.service
dnf  erase wireplumber
systemctl stop pipewire-pulse.service pipewire-pulse.socket
systemctl stop pipewire.service pipewire.socket
systemctl daemon-reload
dnf --skip-broken erase pipewire pipewire-* libpipewire* 
pipewire-media-session pipewire-pulseaudio*


dnf -y install plasma-desktop
# An error message said that plasma-desktop was deleted although that 
does not appear to be true


systemctl stop elogd.service
dnf  erase elog*
# I tried installing elog to get the global XDG_RUNTIME_DIR set: no joy 
doing that.


dnf --allowerasing --skip-broken --best install alsa* 
kde-settings-pulseaudio
dnf --allowerasing --skip-broken --best install pulseaudio* 
alsa-plugins-pulseaudio

dnf --allowerasing install pavucontrol pulseaudio-module-zeroconf

The TL:DR is, that I re-installed alsa and pulseaudio after a couple of 
hours spent trying to get *anything* to connect to the hardware.


Geoff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Help configuring internal network

2022-03-24 Thread Michael Hennebry


On Sun, 20 Mar 2022, R. G. Newbury wrote:

On 2022-03-20 8:00 a.m., Tim >R. G. Newbury 
wrote:

edit your /etc/hosts file to give the hdhomerun unit a fixed IP
address.

When has the /etc/hosts file ever given anything an IP address?


You are correct, and I am completely wrong. A static address for the computer 
would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or 
whatever) or using the network config gui to do the same thing.


Huh?

From man hosts:

SYNOPSIS
   /etc/hosts



  For each host a single line should be present
   with the following information:

  IP_address canonical_hostname [aliases...]



   In  modern  systems,  even though the host table has been superseded by
   DNS, it is still widely used for:

   bootstrapping
  Most systems have a small host table containing the name and ad-
  dress  information  for  important  hosts  on the local network.
  This is useful when DNS is not running, for example during  sys-
  tem bootup.


--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

2022-03-24 Thread DJ Delorie

Geoffrey Leach  writes:
> Is there a 'Getting Started With pipewire' and/or wireplumber
> somewhere? Or should they 'just work' and I need to check my
> connections?

As a non-gnome (and non-display-manager) user, I share these .xsession
snippets:

# Required by pipewire, at least
export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)

# Required by most things
eval `dbus-launch --sh-syntax --exit-with-session`

pipewire &
pipewire-pulse &
(sleep 2 ; wireplumber & ) &

There wasn't a pipewire-specific config; it uses the same ALSA backend
as pulseaudio used.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

2022-03-24 Thread Geoffrey Leach

I'm happy for you. For me, not so much :-(

On Thu, Mar 24, 2022 at 2:53 PM Bob Marcan  wrote:

> On Thu, 24 Mar 2022 14:07:27 -0700
> Geoffrey Leach  wrote:
>
> > I've just installed Fedora 35 and have discovered to my dismay that
> > previously-working (not at all sophisticated) audio no longer works.
> >
> > Is there a 'Getting Started With pipewire' and/or wireplumber somewhere?
> Or
> > should they 'just work' and I need to check my connections?
> >
> > Thanks.
>
> systemctl --user --now disable  wireplumber
> works for me.
> Obviously we are guinea pigs for this premature piece of software.
>
> BR, Bob
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: pipewire and wireplumber

2022-03-24 Thread Bob Marcan

On Thu, 24 Mar 2022 14:07:27 -0700
Geoffrey Leach  wrote:

> I've just installed Fedora 35 and have discovered to my dismay that
> previously-working (not at all sophisticated) audio no longer works.
> 
> Is there a 'Getting Started With pipewire' and/or wireplumber somewhere? Or
> should they 'just work' and I need to check my connections?
> 
> Thanks.

systemctl --user --now disable  wireplumber
works for me.
Obviously we are guinea pigs for this premature piece of software.

BR, Bob
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

pipewire and wireplumber

2022-03-24 Thread Geoffrey Leach

I've just installed Fedora 35 and have discovered to my dismay that
previously-working (not at all sophisticated) audio no longer works.

Is there a 'Getting Started With pipewire' and/or wireplumber somewhere? Or
should they 'just work' and I need to check my connections?

Thanks.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Announcing 389 Directory Server 2.1.1

2022-03-24 Thread Mark Reynolds



   389 Directory Server 2.1.1

The 389 Directory Server team is proud to announce 389-ds-base version 2.1.1

Fedora packages are available on Fedora 36 and Rawhide (f37)

Rawhide:

https://koji.fedoraproject.org/koji/taskinfo?taskID=84602886 



Fedora 36:

https://koji.fedoraproject.org/koji/taskinfo?taskID=84603435 



https://bodhi.fedoraproject.org/updates/FEDORA-2022-917bd01497 
 - Bodhi


The new packages and versions are:

 * 389-ds-base-2.1.1-1

Source tarballs are available for download at Download 
389-ds-base Source 




 Highlights in 2.1.1

 * Bug and Security fixes
 * Transition from BDB(libdb) to LMDB begun. BDB is still the default
   backend, but it can be changed to LMDB for early testing.


 Installation and Upgrade

See Download  for 
information about setting up your yum repositories.


To install the server use *dnf install 389-ds-base*

To install the Cockpit UI plugin use *dnf install cockpit-389-ds*

After rpm install completes, run *dscreate interactive*

For upgrades, simply install the package. There are no further 
steps required.


There are no upgrade steps besides installing the new rpms

See Install_Guide 
 for 
more information about the initial installation and setup


See Source  
for information about source tarballs and SCM (git) access.



 Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list: 
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org


If you find a bug, or would like to see a new feature, file it in our 
GitHub project: https://github.com/389ds/389-ds-base


 * Bump version to 2.1.1
 * Issue 5230 - Race condition in RHDS disk monitoring functions
 * Issue 5193 - Incomplete ruv occasionally returned from ruv
   search (#5194)
 * Issue 4970 - Add support for recursively deleting subentries
 * Issue 4299 - UI - Add CoS funtionality (#5196)
 * Issue 5225 - UI - impossible to manually set entry cache
 * Issue 5186 - UI - Fix SASL Mapping regex test feature
 * Issue 5221 - User with expired password can still login with
   full privledges
 * Issue 5218 - double-free of the virtual attribute context in
   persistent search (#5219)
 * Issue 5214 - CI Test
   tests/suites/replication/virtual_attribute_replication_test.py (#5215)
 * Issue 5197 - Build break in lib389 with INSTALL_PREFIX (#5198)
 * Issue 5200 - dscontainer should use environment variables with
   DS_ prefix
 * Issue 5189 - memberOf plugin exclude subtree not cleaning up groups
   on modrdn
 * Issue 5051 - RFE - ADSync flatten tree (#5192)
 * Issue 5188 - UI - LDAP editor - add entry and group types
 * Issue 5184 - memberOf does not work correctly with multiple
   include scopes
 * Issue 5162 - BUG - error on importing chain files (#5164)
 * Issue 5186 - UI - Fix SASL Mapping regex validation and other
   minor improvements
 * Issue 5048 - Support for nsslapd-tcp-fin-timeout and
   nsslapd-tcp-keepalive-time (#5179)
 * Issue 5122 - dsconf instance backend suffix set doesn’t accept
   backend name (#5178)
 * Issue 5032 - Fix configure option in specfile (#5174)
 * Issue 5176 - CI rewriter fails when libslapd.so.0 does not exist (#5177)
 * Issue 5160 - BUG - x- prefix in descr-oid can confuse oid parser (#5161)
 * Issue 5137 - RFE - improve sssd conf output (#5138)
 * Issue 5102 - BUG - container may fail with bare uid/gid (#5140)
 * Issue 5145 - Fix covscan errors
 * Issue 4721 - UI - attribute uniqueness crashes UI when there are
   no configs
 * Issue 5155 - RFE - Provide an option to abort an Auto Member
   rebuild task
 * Issue 4299 - UI - Add Role funtionality (#5163)
 * Issue 5050 - bdb bulk op fails if fs page size > 8K (#5150)
 * Issue 5149 - Build failure on EL8 - undefined reference to `twalk_r’
 * Issue 5142 - CLI - dsctl dbgen is broken
 * Issue 4678 - Added test cases

--
Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Announcing 389 Directory Server 2.0.15

2022-03-24 Thread Mark Reynolds



   389 Directory Server 2.0.15

The 389 Directory Server team is proud to announce 389-ds-base version 
2.0.15


Fedora packages are available on Fedora 34, and 35

Fedora 35:

https://koji.fedoraproject.org/koji/taskinfo?taskID=84608760 
 - Koji


https://bodhi.fedoraproject.org/updates/FEDORA-2022-40544b5314 
 - Bodhi


Fedora 34:

https://koji.fedoraproject.org/koji/taskinfo?taskID=84609037 
 - Koji


https://bodhi.fedoraproject.org/updates/FEDORA-2022-2558f14c58 
 - Bodhi


The new packages and versions are:

 * 389-ds-base-2.0.15-1

Source tarballs are available for download at Download 
389-ds-base Source 




 Highlights in 2.0.15

 * Bug and Security fixes


 Installation and Upgrade

See Download  for 
information about setting up your yum repositories.


To install the server use *dnf install 389-ds-base*

To install the Cockpit UI plugin use *dnf install cockpit-389-ds*

After rpm install completes, run *dscreate interactive*

For upgrades, simply install the package. There are no further 
steps required.


There are no upgrade steps besides installing the new rpms

See Install_Guide 
 for 
more information about the initial installation and setup


See Source  
for information about source tarballs and SCM (git) access.



 Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list: 
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org


If you find a bug, or would like to see a new feature, file it in our 
GitHub project: https://github.com/389ds/389-ds-base


 * Bump version to 2.0.15
 * Issue 5230 - Race condition in RHDS disk monitoring functions
 * Issue 4299 - UI - Add CoS funtionality (#5196)
 * Issue 5225 - UI - impossible to manually set entry cache
 * Issue 5186 - UI - Fix SASL Mapping regex test feature
 * Issue 5221 - User with expired password can still login with
   full privledges
 * Issue 5218 - double-free of the virtual attribute context in
   persistent search (#5219)
 * Issue 5200 - dscontainer should use environment variables with
   DS_ prefix
 * Issue 5193 - Incomplete ruv occasionally returned from ruv
   search (#5194)
 * Issue 5189 - memberOf plugin exclude subtree not cleaning up groups
   on modrdn
 * Issue 5188 - UI - LDAP editor - add entry and group types
 * Issue 5184 - memberOf does not work correctly with multiple
   include scopes
 * Issue 5162 - BUG - error on importing chain files (#5164)
 * Issue 5186 - UI - Fix SASL Mapping regex validation and other
   minor improvements
 * Issue 5048 - Support for nsslapd-tcp-fin-timeout and
   nsslapd-tcp-keepalive-time (#5179)
 * Issue 5122 - dsconf instance backend suffix set doesn’t accept
   backend name (#5178)
 * Issue 5160 - BUG - x- prefix in descr-oid can confuse oid parser (#5161)
 * Issue 5098 - Multiple issues around replication and CI test
   test_online_reinit_may_hang (#5109)
 * Issue 5102 - BUG - container may fail with bare uid/gid (#5140)
 * Issue 5137 - RFE - improve sssd conf output (#5138)
 * Issue 5145 - Fix covscan errors
 * Issue 4721 - UI - attribute uniqueness crashes UI when there are
   no configs
 * Issue 5155 - RFE - Provide an option to abort an Auto Member
   rebuild task
 * Issue 4299 - UI - Add Role funtionality (#5163)
 * Issue 5050 - bdb bulk op fails if fs page size > 8K (#5150)
 * Issue 4775 - Add entryuuid CLI and Fixup (#4776)
 * Issue 5142 - CLI - dsctl dbgen is broken
 * Issue 4299 - UI - fix minor issues with ldap editor (table view)
 * Issue 4299 - UI - fix minor issues with ldap editor
 * Issue 5103 - UI - Add support for TPR to web console (#5111)

--
Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Problem with kernel 5.16.16 not auto booting on 1 machine??

2022-03-24 Thread Michael D. Setzer II via users


Have 5 linux machines at home. 3 with Fedora 34 and 2 
with Fedora 35. 4 did the dnf update that included 
5.16.16 and rebooted fine.

The one system didn't?? Have 3 machine I vnc into, and 
have one monitor that I connect when I need to look at 
them.

When I couldn't get to the machine after there was 
enough time to reboot, and pings failed. I connected 
monitor. 

When screen came up, it was sitting at grub menu. 
Pressing enter had it load the 5.16.16 kernel with what 
seemed no issue. Then did a restart and again, it just got 
to the boot menu with no timeout? So had to press enter 
again. Did that 2 more times, same results.

Reinstalled the kernel but again. Same result.
Looked at grub.cfg and didn't see anything, and 
/default/grub was same as other machines?

Looked at grubenv and that was showing boot_success=0
while all other machines had boot_success=1.

On my notebook it shows as beginning.
# GRUB Environment Block
# WARNING: Do not edit this file by tools other than 
grub-editenv!!!
saved_entry=189711f94e78436d9618b891a8fce70e-5.16.
16-100.fc34.x86_64
boot_success=1
boot_indeterminate=0

Tried the grub-editenv that it mentioned, but program not 
found. There is a grub2-editenv, so perhaps a missed 
update for the grubenv?? 

Help didn't show much, so was going to change the 0 to 1 
with hexedit, but I looked at grubenv and it had changed 
from 0 to 1 on its own in the time I took looking at things.

The other 4 machines did update with no problem, and 
reboot started with no intervention. Not sure why this 
one had it go to grub menu, and just sit there.

Haven't tried another reboot to see it the timeout will 
work next time, or if will have to continue hitting enter 
after any reboot??

Haven't had this issue with any other updates??

Thanks.
Have a nice day.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Lewis Robson


nice one thankyou, Ill change this over tomorrow and see how it goes :D


On 24/03/2022 17:14, Mark Reynolds wrote:
Yup, you are using two different suffixes/backends between the 
suppliers and consumers.  The consumers are only accepting replication 
updates for "dc=test,dc=co,dc=uk", but the supplier is trying to 
replicate "dc=conscious,dc=co,dc=uk".  They have to be the same ;-)


Mark


On 3/24/22 11:17 AM, Lewis Robson wrote:

Thanks, here is the results:

# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: objectclass=nsds5replica
# requesting: ALL
#


dn: cn=replica,cn=dc\3Dtest\2Cdc\3Dco\2Cdc\3Duk,cn=mapping
 tree,cn=config
objectClass: nsDS5Replica
objectClass: top
nsDS5ReplicaRoot: dc=test,dc=co,dc=uk
nsDS5ReplicaType: 2
nsDS5Flags: 0
nsds5ReplicaPurgeDelay: 0
nsDS5ReplicaBindDN: cn=replication manager,cn=config
cn: replica
nsDS5ReplicaId: 65535
nsState:: //8AAACOWzxiAAABAA==
nsDS5ReplicaName: d0393002-ab6811ec-80f38dbb-204096f4
nsds5ReplicaChangeCount: 0
nsds5replicareapactive: 0

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1


Can you also provide provide the other information I requested from 
the RHEL 8 server?

slapd-consciousldap replication get --suffix dc=conscious,dc=co,dc=uk
dn: cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: replica
nsDS5Flags: 1
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaId: 1
nsDS5ReplicaName: 3309fd02-4dfd11ec-b026c7f3-953dc3fe
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaType: 3
nsState:: AQCkHTNiAAABAA==
nsds5ReplicaChangeCount: 34
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5Replica




dsconf slapd-consciousldap repl-agmt list --suffix 
dc=conscious,dc=co,dc=uk
dn: 
cn=copy,cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: copy
description: copy
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaBindMethod: simple
nsDS5ReplicaCredentials: {AES- stuff was here ive removed it for the 
email)

nsDS5ReplicaHost: linuxtestserver
nsDS5ReplicaPort: 636
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaTransportInfo: LDAPS
nsds5replicaChangesSentSinceStartup:
nsds5replicaLastInitEnd: 1970010100Z
nsds5replicaLastInitStart: 20220324141215Z
nsds5replicaLastInitStatus: Error (6) Replication error acquiring 
replica: no such replica
nsds5replicaLastInitStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "conn_rc": "0", "conn_rc_text": "operation success", 
"date": "2022-03-24T14:12:15Z", "message": "Error (6) Replication 
error acquiring replica: no such replica"}

nsds5replicaLastUpdateEnd: 1970010100Z
nsds5replicaLastUpdateStart: 1970010100Z
nsds5replicaLastUpdateStatus: Error (6) Replication error acquiring 
replica: Unable to acquire replica: there is no replicated area on 
the consumer server. Replication is aborting. (no such replica)
nsds5replicaLastUpdateStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "date": "2022-03-24T14:12:15Z", "message": "Error (6) 
Replication error acquiring replica: Unable to acquire replica: there 
is no replicated area on the consumer server. Replication is 
aborting. (no such replica)"}

nsds5replicaUpdateInProgress: FALSE
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5replicationagreement

Cheers





sidenote, If i run the below without any filtering applied by me


ldapsearch -x -b "dc=test,dc=co,dc=uk,cn=config" -H 
ldaps://myserver -D "cn=replication manager,cn=config" -W

Enter LDAP Password:


Is "dc=test,dc=co,dc=uk,cn=config" really an entry under cn=config.  
This looks wrong.


Mark




i get:


# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1





My other concern is about the error message above, is that from a 
RHEL 8 replica?


this is from the var/log/dirsrv/slapd-host/* logs




If so, this indicates replication is not setup properly on that 
suffix, but you say all the rhel 8 replicas are working.


we only have the 1 master node on 8, apologies for any confusion.


Thanks

-Lewis







Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it:

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Mark Reynolds

Yup, you are using two different suffixes/backends between the suppliers 
and consumers.  The consumers are only accepting replication updates for 
"dc=test,dc=co,dc=uk", but the supplier is trying to replicate 
"dc=conscious,dc=co,dc=uk".  They have to be the same ;-)


Mark


On 3/24/22 11:17 AM, Lewis Robson wrote:

Thanks, here is the results:

# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: objectclass=nsds5replica
# requesting: ALL
#


dn: cn=replica,cn=dc\3Dtest\2Cdc\3Dco\2Cdc\3Duk,cn=mapping
 tree,cn=config
objectClass: nsDS5Replica
objectClass: top
nsDS5ReplicaRoot: dc=test,dc=co,dc=uk
nsDS5ReplicaType: 2
nsDS5Flags: 0
nsds5ReplicaPurgeDelay: 0
nsDS5ReplicaBindDN: cn=replication manager,cn=config
cn: replica
nsDS5ReplicaId: 65535
nsState:: //8AAACOWzxiAAABAA==
nsDS5ReplicaName: d0393002-ab6811ec-80f38dbb-204096f4
nsds5ReplicaChangeCount: 0
nsds5replicareapactive: 0

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1


Can you also provide provide the other information I requested from 
the RHEL 8 server?

slapd-consciousldap replication get --suffix dc=conscious,dc=co,dc=uk
dn: cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: replica
nsDS5Flags: 1
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaId: 1
nsDS5ReplicaName: 3309fd02-4dfd11ec-b026c7f3-953dc3fe
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaType: 3
nsState:: AQCkHTNiAAABAA==
nsds5ReplicaChangeCount: 34
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5Replica




dsconf slapd-consciousldap repl-agmt list --suffix 
dc=conscious,dc=co,dc=uk
dn: 
cn=copy,cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: copy
description: copy
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaBindMethod: simple
nsDS5ReplicaCredentials: {AES- stuff was here ive removed it for the 
email)

nsDS5ReplicaHost: linuxtestserver
nsDS5ReplicaPort: 636
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaTransportInfo: LDAPS
nsds5replicaChangesSentSinceStartup:
nsds5replicaLastInitEnd: 1970010100Z
nsds5replicaLastInitStart: 20220324141215Z
nsds5replicaLastInitStatus: Error (6) Replication error acquiring 
replica: no such replica
nsds5replicaLastInitStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "conn_rc": "0", "conn_rc_text": "operation success", "date": 
"2022-03-24T14:12:15Z", "message": "Error (6) Replication error 
acquiring replica: no such replica"}

nsds5replicaLastUpdateEnd: 1970010100Z
nsds5replicaLastUpdateStart: 1970010100Z
nsds5replicaLastUpdateStatus: Error (6) Replication error acquiring 
replica: Unable to acquire replica: there is no replicated area on the 
consumer server. Replication is aborting. (no such replica)
nsds5replicaLastUpdateStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "date": "2022-03-24T14:12:15Z", "message": "Error (6) 
Replication error acquiring replica: Unable to acquire replica: there 
is no replicated area on the consumer server. Replication is aborting. 
(no such replica)"}

nsds5replicaUpdateInProgress: FALSE
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5replicationagreement

Cheers





sidenote, If i run the below without any filtering applied by me


ldapsearch -x -b "dc=test,dc=co,dc=uk,cn=config" -H ldaps://myserver 
-D "cn=replication manager,cn=config" -W

Enter LDAP Password:


Is "dc=test,dc=co,dc=uk,cn=config" really an entry under cn=config.  
This looks wrong.


Mark




i get:


# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1





My other concern is about the error message above, is that from a 
RHEL 8 replica?


this is from the var/log/dirsrv/slapd-host/* logs




If so, this indicates replication is not setup properly on that 
suffix, but you say all the rhel 8 replicas are working.


we only have the 1 master node on 8, apologies for any confusion.


Thanks

-Lewis







Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



--
Directory Server Development Team
___
389-users

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Lewis Robson


Thanks, here is the results:

# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: objectclass=nsds5replica
# requesting: ALL
#


dn: cn=replica,cn=dc\3Dtest\2Cdc\3Dco\2Cdc\3Duk,cn=mapping
 tree,cn=config
objectClass: nsDS5Replica
objectClass: top
nsDS5ReplicaRoot: dc=test,dc=co,dc=uk
nsDS5ReplicaType: 2
nsDS5Flags: 0
nsds5ReplicaPurgeDelay: 0
nsDS5ReplicaBindDN: cn=replication manager,cn=config
cn: replica
nsDS5ReplicaId: 65535
nsState:: //8AAACOWzxiAAABAA==
nsDS5ReplicaName: d0393002-ab6811ec-80f38dbb-204096f4
nsds5ReplicaChangeCount: 0
nsds5replicareapactive: 0

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1


Can you also provide provide the other information I requested from 
the RHEL 8 server?

slapd-consciousldap replication get --suffix dc=conscious,dc=co,dc=uk
dn: cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: replica
nsDS5Flags: 1
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaId: 1
nsDS5ReplicaName: 3309fd02-4dfd11ec-b026c7f3-953dc3fe
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaType: 3
nsState:: AQCkHTNiAAABAA==
nsds5ReplicaChangeCount: 34
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5Replica





dsconf slapd-consciousldap repl-agmt list --suffix dc=conscious,dc=co,dc=uk
dn: cn=copy,cn=replica,cn=dc\3Dconscious\2Cdc\3Dco\2Cdc\3Duk,cn=mapping 
tree,cn=config

cn: copy
description: copy
nsDS5ReplicaBindDN: cn=replication manager,cn=config
nsDS5ReplicaBindMethod: simple
nsDS5ReplicaCredentials: {AES- stuff was here ive removed it for the email)
nsDS5ReplicaHost: linuxtestserver
nsDS5ReplicaPort: 636
nsDS5ReplicaRoot: dc=conscious,dc=co,dc=uk
nsDS5ReplicaTransportInfo: LDAPS
nsds5replicaChangesSentSinceStartup:
nsds5replicaLastInitEnd: 1970010100Z
nsds5replicaLastInitStart: 20220324141215Z
nsds5replicaLastInitStatus: Error (6) Replication error acquiring 
replica: no such replica
nsds5replicaLastInitStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "conn_rc": "0", "conn_rc_text": "operation success", "date": 
"2022-03-24T14:12:15Z", "message": "Error (6) Replication error 
acquiring replica: no such replica"}

nsds5replicaLastUpdateEnd: 1970010100Z
nsds5replicaLastUpdateStart: 1970010100Z
nsds5replicaLastUpdateStatus: Error (6) Replication error acquiring 
replica: Unable to acquire replica: there is no replicated area on the 
consumer server. Replication is aborting. (no such replica)
nsds5replicaLastUpdateStatusJSON: {"state": "red", "ldap_rc": "0", 
"ldap_rc_text": "Success", "repl_rc": "6", "repl_rc_text": "no such 
replica", "date": "2022-03-24T14:12:15Z", "message": "Error (6) 
Replication error acquiring replica: Unable to acquire replica: there is 
no replicated area on the consumer server. Replication is aborting. (no 
such replica)"}

nsds5replicaUpdateInProgress: FALSE
nsds5replicareapactive: 0
objectClass: top
objectClass: nsds5replicationagreement

Cheers





sidenote, If i run the below without any filtering applied by me


ldapsearch -x -b "dc=test,dc=co,dc=uk,cn=config" -H ldaps://myserver 
-D "cn=replication manager,cn=config" -W

Enter LDAP Password:


Is "dc=test,dc=co,dc=uk,cn=config" really an entry under cn=config.  
This looks wrong.


Mark




i get:


# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1





My other concern is about the error message above, is that from a 
RHEL 8 replica?


this is from the var/log/dirsrv/slapd-host/* logs




If so, this indicates replication is not setup properly on that 
suffix, but you say all the rhel 8 replicas are working.


we only have the 1 master node on 8, apologies for any confusion.


Thanks

-Lewis







Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



--
Lewis Robson
Systems Administrator
Conscious Solutions Limited

Tel: 0117 325 0200
Web: https://www.conscious.co.uk
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:

Re: Message during dnf update

2022-03-24 Thread Robert McBroom via users


On 3/23/22 11:46, Roger Heflin wrote:
if the groups aren't being created and dnf did not show an error, then 
at the very least the script in the rpm doing the install is not 
checking return codes and reporting an error.


The scripts reporting the above, may or may not even have code that 
works (especially given they aren't checking error codes).


here are my permissions they appear to be default (rpm -V setup) will 
point out any permissions issues around those files.


-rw-r--r--. 1 root root 1891 Feb  5 11:39 /etc/group
--. 1 root root 1464 Feb  5 11:39 /etc/gshadow
-rw-r--r--. 1 root root 4837 Feb  5 11:57 /etc/passwd

likely the above scripts are using the groupadd and useradd commands 
so you might try adding a group and/or a user with those commands and 
see if it works or gives an error.


If it gives no error and you confirm it did add the user/group then 
one has to conclude that the script in the rpm is not doing the 
user/group creation properly.




On Wed, Mar 23, 2022 at 8:00 AM Robert McBroom 
 wrote:


On 3/22/22 13:27, Roger Heflin wrote:

The last Failed to write message is the only real error.   The
other messages are informational.    The /etc/gshadow is
basically trying to add the group users and it already being in
the file, which is informational.

The real error will be coming from one of the install scripts in
one of the rpms and that is what needs to be changed (bug report
on the rpm giving that error to correct the error).  And you
don't know exactly what rpm is doing it nor what file it is
trying to write to.

On Tue, Mar 22, 2022 at 11:55 AM Robert McBroom via users
 wrote:

The following message was sent to the terminal just before
the verifying step on a dnf update.

Creating group sgx with gid 106.
Creating group users with gid 100.
Creating group systemd-oom with gid 951.
Creating user systemd-oom (systemd Userspace OOM Killer) with
uid 951 and gid 951.
/etc/gshadow: Group "users" already exists.
Failed to write files: File exists

No such entries are in /etc/group. /etc/gshadow has
permissions of 000, with last update of may 20,2021. Do these
setting need to be changed?


The groups sgx and systemd-oom did not get created either. The
group users is in gshadow but not in group.


Apparently a little more complicated.

~]# groupadd sgx
[sss_cache] [sysdb_domain_cache_connect] (0x0010): DB version too old 
[0.22], expected [0.23] fo

r domain implicit_files!
Higher version of database is expected!
In order to upgrade the database, you must run SSSD.
Removing cache files in /var/lib/sss/db should fix the issue, but note 
that removing cache files

will also remove all of your cached credentials.
Could not open available domains

However, sgx was added to /etc/group. Other group additions went through 
with no messages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Lewis Robson

Resending replacing images with text explanations as email got put into 
queue.



Thanks Thierry,



I agree with Mark, an issue is likely in replication agreement 
definition. According to the error message it looks the consumer 
(centos 7) can not retrieve the replicaroot from the replication 
extop. A possibility is that the replication agreement (on alma 8) is 
missing 'nsDS5ReplicaRoot'.


the replication manager account was set up from the cockpit ui, 
replication as per the below, for the nsDS5ReplicaRoot, how would I go 
about adding this?



(images were here, they showed:)

(image 1, configuration tab)

replica role: Supplier

Replica ID: 1

configuration tab: replication managers: cn=replication manager,cn=config


(Image two, replication agreement)
port 636

bind DN cn=replication manager,cn=config

LDAPS

authentication method SIMPLE


--
Lewis Robson
Systems Administrator
Conscious Solutions Limited

Tel: 0117 325 0200
Web: https://www.conscious.co.uk
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Mark Reynolds



On 3/24/22 10:34 AM, Lewis Robson wrote:

Thanks Mark, please see responses below


Couple things here, are the RHEL 7 servers set up as replication 
consumers? that is correct, in the 389 console under configuration > 
replication > userRoot, dedicated consumer



Yes you need the replication manager setup, but the suffix needs to 
be enabled for replication as well.  Can you do a ldapsearch on 
cn=config searching for "objectclass=nsds5replica" and share the output?


heres the output of the below command, is this what you mean?


ldapsearch -x -b "dc=test,dc=co,dc=uk" -H ldaps://myserver -D 
"cn=replication manager,cn=config" -W "objectclass=nsds5replica"

Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: objectclass=nsds5replica
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1



You need to search under "cn=conifg" for objectclass=nsds5replica. not 
the database suffix, and you should do so as the directory manager account:


ldapsearch =D "cn=directory manger" -W -b cn=config objectclass=nsds5replica


Can you also provide provide the other information I requested from the 
RHEL 8 server?



# dsconf slapd-YOUR_INSTANCE replication get --suffix dc=test,dc=co,dc=uk

# dsconf slapd-YOUR_INSTANCE repl-agmt list --suffix dc=test,dc=co,dc=uk





sidenote, If i run the below without any filtering applied by me


ldapsearch -x -b "dc=test,dc=co,dc=uk,cn=config" -H ldaps://myserver 
-D "cn=replication manager,cn=config" -W

Enter LDAP Password:


Is "dc=test,dc=co,dc=uk,cn=config" really an entry under cn=config.  
This looks wrong.


Mark




i get:


# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1





My other concern is about the error message above, is that from a RHEL 
8 replica?


this is from the var/log/dirsrv/slapd-host/* logs




If so, this indicates replication is not setup properly on that 
suffix, but you say all the rhel 8 replicas are working.


we only have the 1 master node on 8, apologies for any confusion.


Thanks

-Lewis







Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



--
Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: OpenLDAP import into 389 Directory Server failing

2022-03-24 Thread Jason W. Lewis

Mark,
Thanks for that.  I have gone through those docs already, and I’m still running 
into it.  My 389-ds-base package is version 1.4.4.17.

--
Jason Lewis

Systems Administrator



From: Mark Reynolds 
Date: Tuesday, February 22, 2022 at 16:08
To: "General discussion list for the 389 Directory server project." 
<389-users@lists.fedoraproject.org>, "Jason W. Lewis" 
Subject: Re: [389-users] OpenLDAP import into 389 Directory Server failing


External email – Please make sure you trust the source before clicking links or 
opening attachments.

What version of 389-ds-base are you using?

Check out these docs if you haven't already:

https://www.port389.org/docs/389ds/howto/howto-openldap-migration.html

https://www.port389.org/docs/389ds/design/openldap2ds.html

Thanks,

Mark
On 2/22/22 3:59 PM, Jason W. Lewis wrote:
After RHEL, etc dropped OpenLDAP, I’ve begun testing with 389 Directory Server. 
Currently, I’m trying to use openldap_to_ds to import slapd.d config and an 
LDIF export to import my old database into the new server.
I’ve created a new instance in 389-ds named terminal-config. I’ve tried the 
following variations on the idea, all of which gave me the same results:

  1.  exported the LDIF from OpenLDAP 2.4 on Oracle Linux 7 and CentOS 6 
servers.
  2.  Rewrote all files being imported to make sure they weren’t corrupt.
  3.  used relative and absolute path names to the files
  4.  Tried importing with a new instance (as mentioned above) and no instance 
at all
  5.  When using dscreate to make the new instance, I’ve tried setting it up 
differently (allowed sample entries and not, etc)
No matter what I do, this is what I get when I try:
[root@ldaptest ~]# openldap_to_ds terminal-config /root/slapd.d  
/root/terminals.ldif
Examining OpenLDAP Configuration ...
Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 250, in 
result = do_migration(inst, log, args, skip_overlays)
  File "/usr/sbin/openldap_to_ds", line 178, in do_migration
config = olConfig(args.slapd_config, log)
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in __init__
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 305, in 
for db in dbs
  File "/usr/lib/python3.6/site-packages/lib389/migrate/openldap/config.py", 
line 112, in __init__
self.suffix = ensure_str(self.config[1]['olcSuffix'][0])
KeyError: 'olcSuffix'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/openldap_to_ds", line 257, in 
log.error("Error: %s" % " - ".join(str(val) for val in msg.values()))
AttributeError: 'str' object has no attribute 'values'
[root@ldaptest ~]#

Any thoughts on what could be causing this?

--
[Micro Electronics Inc]

Jason Lewis

Systems Administrator

jwle...@microcenter.com

|

[signature_251198827]

614-777-2728




[Micro Center Secure Email]

CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is 
intended exclusively for the person or entity to which it is addressed and may 
contain confidential and/or privileged material. If you are not the intended 
recipient, you are not authorized to read, print, retain, copy or disseminate 
this message or any part of it. If you receive this message in error, please 
contact the sender by reply e-mail and destroy all copies of the original 
message and attachments. Thank you





___

389-users mailing list -- 
389-users@lists.fedoraproject.org

To unsubscribe send an email to 
389-users-le...@lists.fedoraproject.org

Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

--

Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Lewis Robson


Thanks Mark, please see responses below


Couple things here, are the RHEL 7 servers set up as replication 
consumers? that is correct, in the 389 console under configuration > 
replication > userRoot, dedicated consumer



Yes you need the replication manager setup, but the suffix needs to be 
enabled for replication as well.  Can you do a ldapsearch on cn=config 
searching for "objectclass=nsds5replica" and share the output?


heres the output of the below command, is this what you mean?


ldapsearch -x -b "dc=test,dc=co,dc=uk" -H ldaps://myserver -D 
"cn=replication manager,cn=config" -W "objectclass=nsds5replica"

Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: objectclass=nsds5replica
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1


sidenote, If i run the below without any filtering applied by me


ldapsearch -x -b "dc=test,dc=co,dc=uk,cn=config" -H ldaps://myserver -D 
"cn=replication manager,cn=config" -W

Enter LDAP Password:


i get:


# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 0 Success

# numResponses: 1





My other concern is about the error message above, is that from a RHEL 8 
replica?


this is from the var/log/dirsrv/slapd-host/* logs




If so, this indicates replication is not setup properly on that suffix, 
but you say all the rhel 8 replicas are working.


we only have the 1 master node on 8, apologies for any confusion.


Thanks

-Lewis







Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



--
Lewis Robson
Systems Administrator
Conscious Solutions Limited

Tel: 0117 325 0200
Web: https://www.conscious.co.uk
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Thierry Bordaz



On 3/24/22 2:17 PM, Mark Reynolds wrote:


On 3/24/22 8:38 AM, Lewis Robson wrote:

Hello all,

i am working to do multi master with two different versions of OS 
(alma 8 and centos 7), this means that the 389 on alma 8 is using 
dsidm and cockpit and the 389 on centos 7 is using 389console with 
ldap commands.



the alma 8 directory tree is how we want it to be, users inside, all 
working as expected.


the 7 directory tree is the complete standard given when 389ds is setup.


on the 7 machine (slave) I have the bind dn information of 
cn=replication manager,cn=config.
This has been set up on the 8 mschine via cockpit in the replication 
agreement to connect with these credentials. an ldapsearch lets me 
connect with them and purposely typing the username or password wrong 
for the agreement gives a different error so im confident the account 
is okay.



The error I see, when i try and initiliaze the agreement from the 8 
cockpit view to the slave machine is:


ERR - NSMMReplicationPlugin - 
multimaster_extop_StartNSDS50ReplicationRequest - conn=289 op=3 
replica="unknown": Unable to acquire replica: error: no such replica


Couple things here, are the RHEL 7 servers set up as replication 
consumers?  Yes you need the replication manager setup, but the suffix 
needs to be enabled for replication as well.  Can you do a ldapsearch 
on cn=config searching for "objectclass=nsds5replica" and share the 
output?



I agree with Mark, an issue is likely in replication agreement 
definition. According to the error message it looks the consumer (centos 
7) can not retrieve the replicaroot from the replication extop. A 
possibility is that the replication agreement (on alma 8) is missing 
'nsDS5ReplicaRoot'.





My other concern is about the error message above, is that from a RHEL 
8 replica?  If so, this indicates replication is not setup properly on 
that suffix, but you say all the rhel 8 replicas are working.  Are you 
using multiple backends/suffixes or just one? If you are using 
multiple backends then maybe you have a mismatch in your replication 
config?  Becuase that error about "unknown" replica means the "suffix" 
was not configured for replication. Was this error from a RHEL 8 
replica?  If so run these commands:


Change the suffix value to your suffix:

# dsconf slapd-YOUR_INSTANCE replication get --suffix dc=example,dc=com

# dsconf slapd-YOUR_INSTANCE repl-agmt list --suffix dc=example,dc=com

If nothing sticks out try turning on replication logging 
(nsslapd-erorrlog-level: 8192) - you can do this from the Cockpit UI 
as well.


Thanks,

Mark





Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure



___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Mark Reynolds



On 3/24/22 8:38 AM, Lewis Robson wrote:

Hello all,

i am working to do multi master with two different versions of OS 
(alma 8 and centos 7), this means that the 389 on alma 8 is using 
dsidm and cockpit and the 389 on centos 7 is using 389console with 
ldap commands.



the alma 8 directory tree is how we want it to be, users inside, all 
working as expected.


the 7 directory tree is the complete standard given when 389ds is setup.


on the 7 machine (slave) I have the bind dn information of 
cn=replication manager,cn=config.
This has been set up on the 8 mschine via cockpit in the replication 
agreement to connect with these credentials. an ldapsearch lets me 
connect with them and purposely typing the username or password wrong 
for the agreement gives a different error so im confident the account 
is okay.



The error I see, when i try and initiliaze the agreement from the 8 
cockpit view to the slave machine is:


ERR - NSMMReplicationPlugin - 
multimaster_extop_StartNSDS50ReplicationRequest - conn=289 op=3 
replica="unknown": Unable to acquire replica: error: no such replica


Couple things here, are the RHEL 7 servers set up as replication 
consumers?  Yes you need the replication manager setup, but the suffix 
needs to be enabled for replication as well.  Can you do a ldapsearch on 
cn=config searching for "objectclass=nsds5replica" and share the output?


My other concern is about the error message above, is that from a RHEL 8 
replica?  If so, this indicates replication is not setup properly on 
that suffix, but you say all the rhel 8 replicas are working.  Are you 
using multiple backends/suffixes or just one? If you are using multiple 
backends then maybe you have a mismatch in your replication config?  
Becuase that error about "unknown" replica means the "suffix" was not 
configured for replication. Was this error from a RHEL 8 replica?  If so 
run these commands:


Change the suffix value to your suffix:

# dsconf slapd-YOUR_INSTANCE replication get --suffix dc=example,dc=com

# dsconf slapd-YOUR_INSTANCE repl-agmt list --suffix dc=example,dc=com

If nothing sticks out try turning on replication logging 
(nsslapd-erorrlog-level: 8192) - you can do this from the Cockpit UI as 
well.


Thanks,

Mark





Does anyone know anything that I could check for the error to get 
around this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


--
Directory Server Development Team
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

2022-03-24 Thread George N. White III

On Thu, 24 Mar 2022 at 09:36, Brad Bell  wrote:

> I am doing algorithmic differentiation with very large tapes and my jobs
> sometimes run out of memory.
>

Sometimes software developed for small problems can benefit from
adjustments to better
manage memory for larger problems.   Swapping is a very crude process while
working at the
algorithm level you often have better control over how memory is used.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

2022-03-24 Thread Richard Shaw

On Thu, Mar 24, 2022 at 7:36 AM Brad Bell  wrote:

> I am doing algorithmic differentiation with very large tapes and my jobs
> sometimes run out of memory.
>

Another helpful datapoint would be how much physical memory do you have?

This use case certainly isn't a typical desktop user one and memory isn't
that expensive. I would think using physical swap would slow the process
down quite a bit.

In either case, it looks like you have your initial problem solved.

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

2022-03-24 Thread Lewis Robson


Hello all,

i am working to do multi master with two different versions of OS (alma 
8 and centos 7), this means that the 389 on alma 8 is using dsidm and 
cockpit and the 389 on centos 7 is using 389console with ldap commands.



the alma 8 directory tree is how we want it to be, users inside, all 
working as expected.


the 7 directory tree is the complete standard given when 389ds is setup.


on the 7 machine (slave) I have the bind dn information of 
cn=replication manager,cn=config.
This has been set up on the 8 mschine via cockpit in the replication 
agreement to connect with these credentials. an ldapsearch lets me 
connect with them and purposely typing the username or password wrong 
for the agreement gives a different error so im confident the account is 
okay.



The error I see, when i try and initiliaze the agreement from the 8 
cockpit view to the slave machine is:


ERR - NSMMReplicationPlugin - 
multimaster_extop_StartNSDS50ReplicationRequest - conn=289 op=3 
replica="unknown": Unable to acquire replica: error: no such replica



Does anyone know anything that I could check for the error to get around 
this?



Thankyou kindly.

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

2022-03-24 Thread Brad Bell


I am doing algorithmic differentiation with very large tapes and my jobs 
sometimes run out of memory.

On 3/23/22 12:51, Richard Shaw wrote:

On Wed, Mar 23, 2022 at 2:04 PM Brad Bell  wrote:

The instructions below worked for me and the created extra swap space (not 
as much as desired
but I
can fix that)

~>swapon -s
Filename                Type        Size        Used Priority
/dev/zram0              partition   8388604     390584100
/swapfile               file        65532       0       -2


What do you mean by this may not be necessary. Is there a better way to 
increase the swap space ?


To rephrase the question, how do you know you need additional swap? Are you having processes 
killed by OOM?


Thanks,
Richard

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: 389ds for Dummies: How to get started with an empty 389ds server?

2022-03-24 Thread Johannes Kastl


Hi Viktor,

thanks for the fast reply!

On 24.03.22 at 09:57 Viktor Ashirov wrote:


Question: How do I get content into the server initially? It seems I have an
empty server, but I found no documentation on what to do at this point.


You have to create a backend and suffix first, because they are not
created by default:
dsconf localhost backend create --suffix="dc=example,dc=com" \
--be-name userRoot --create-suffix --create-entries


OK, so this commands seems to work:


389server-6fff4cb6d8-kjjd4:/ # dsconf slapd-localhost backend create 
--suffix="dc=ojkastl,dc=de"  --be-name userRoot --create-suffix
The database was sucessfully created
389server-6fff4cb6d8-kjjd4:/ # 


Now I get a result when searching with ldapsearch, it seems the "base" object 
was created (using objectclasses top and domain).


And it seems like I can add entries using ldapadd. Hooray!


Sorry about the missing docs. I'm working on a howto doc for running
DS in OpenShift, hope to publish it soon.


That would be really great!

Kind Regards,
Johannes

--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
http://www.b1-systems.de
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


OpenPGP_signature
Description: OpenPGP digital signature
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: 389ds for Dummies: How to get started with an empty 389ds server?

2022-03-24 Thread Viktor Ashirov

Hi,

On Thu, 24 Mar 2022 at 09:20, Johannes Kastl  wrote:
>
> Hi everyone,
>
> sorry if this question was asked before, but as I found nothing in the docs I 
> am
> blocked at the moment.
>
> I got 389ds running in Kubernetes, which uses a very simple container.inf 
> file:

This is actually a .dsrc file (even though it's named differently), so
it's not used to create an instance, but to help you to connect to
your instance using dsconf inside the container.

>
> > [localhost]
> > # Note that '/' is replaced to '%%2f' for ldapi url format.
> > # So this is pointing to /data/run/slapd-localhost.socket
> > uri = ldapi://%%2fdata%%2frun%%2fslapd-localhost.socket
> > binddn = cn=Directory Manager
> > # Set your basedn here
> > basedn = dc=example,dc=com
>
> So no sample entries are being generated (no "sample_entries = yes").
>
> I tried to follow and see which steps I need from the quickstart:
> https://www.port389.org/docs/389ds/howto/quickstart.html
>
> Checking the status is the first thing that does not work, as dsctl inside the
> container does not have a "status" subcommand:
> > 389server-6fff4cb6d8-kjjd4:/ # dsctl slapd-localhost status
> > usage: dsctl [-h] [-v] [-j] [-l] [instance] 
> > {db2index,db2bak,db2ldif,dbverify,bak2db,ldif2db,backups,ldifs,tls,healthcheck,get-nsstate,ldifgen,dsrc,cockpit,dblib}
> >  ...
> > dsctl: error: invalid choice: 'status' (choose from 'db2index', 'db2bak', 
> > 'db2ldif', 'dbverify', 'bak2db', 'ldif2db', 'backups', 'ldifs', 'tls', 
> > 'healthcheck', 'get-nsstate', 'ldifgen', 'dsrc', 'cockpit', 'dblib')
> > 389server-6fff4cb6d8-kjjd4:/ #
>
> The "healthcheck" seems to be successful. Puuh.
>
> Adding a user fails with "Error: 105 - 4 - 32 - No such object - []", most
> probably because there is no content inside the server yet (no base object,
> users OU or similar).
>
> So I tried to query the server using ldapsearch (from the outside) and got a
> working connection, even with "-ZZ":
>
> > $ ldapsearch -x -W -H ldap://my-389ds-server -D "cn=Directory Manager" -ZZ 
> > -b cn=config
>  > [...]
> > # search result
> > search: 3
> > result: 0 Success
> >
> > # numResponses: 161
> > # numEntries: 160
>
> OK, let's add a base object using ldapadd:
>
> > dn: dc=example,dc=com
> > objectClass: domain
> > objectClass: dcObject
>
> > $ ldapadd -x -f base_only.ldif -D "cn=Directory Manager" -W -H 
> > ldap://my-389ds-server
> > Enter LDAP Password:
> > adding new entry "dc=example,dc=com"
> > ldap_add: No such object (32)
>
> I tried different combinations of objectClass'es, but always got error 32.
>
> Question: How do I get content into the server initially? It seems I have an
> empty server, but I found no documentation on what to do at this point.

You have to create a backend and suffix first, because they are not
created by default:
dsconf localhost backend create --suffix="dc=example,dc=com" \
--be-name userRoot --create-suffix --create-entries

Leave --create-entries if you don't need sample entries present.

Sorry about the missing docs. I'm working on a howto doc for running
DS in OpenShift, hope to publish it soon.

>
> Am I missing some schema? If so, how would I bootstrap it?
>
> Sorry if those are obvious questions, but either I am lacking the deep LDAP
> knowledge to answer them myself or there is an error in my setup.
>
> Thanks in advance!
>
> Johannes
>
> --
> Johannes Kastl
> Linux Consultant & Trainer
> Tel.: +49 (0) 151 2372 5802
> Mail: ka...@b1-systems.de
>
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg
> http://www.b1-systems.de
> GF: Ralph Dehner
> Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure



-- 
Viktor
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] 389ds for Dummies: How to get started with an empty 389ds server?

2022-03-24 Thread Johannes Kastl


Hi everyone,

sorry if this question was asked before, but as I found nothing in the docs I am 
blocked at the moment.


I got 389ds running in Kubernetes, which uses a very simple container.inf file:


[localhost]
# Note that '/' is replaced to '%%2f' for ldapi url format.
# So this is pointing to /data/run/slapd-localhost.socket
uri = ldapi://%%2fdata%%2frun%%2fslapd-localhost.socket
binddn = cn=Directory Manager
# Set your basedn here
basedn = dc=example,dc=com


So no sample entries are being generated (no "sample_entries = yes").

I tried to follow and see which steps I need from the quickstart:
https://www.port389.org/docs/389ds/howto/quickstart.html

Checking the status is the first thing that does not work, as dsctl inside the 
container does not have a "status" subcommand:

389server-6fff4cb6d8-kjjd4:/ # dsctl slapd-localhost status
usage: dsctl [-h] [-v] [-j] [-l] [instance] 
{db2index,db2bak,db2ldif,dbverify,bak2db,ldif2db,backups,ldifs,tls,healthcheck,get-nsstate,ldifgen,dsrc,cockpit,dblib}
 ...
dsctl: error: invalid choice: 'status' (choose from 'db2index', 'db2bak', 
'db2ldif', 'dbverify', 'bak2db', 'ldif2db', 'backups', 'ldifs', 'tls', 
'healthcheck', 'get-nsstate', 'ldifgen', 'dsrc', 'cockpit', 'dblib')
389server-6fff4cb6d8-kjjd4:/ #


The "healthcheck" seems to be successful. Puuh.

Adding a user fails with "Error: 105 - 4 - 32 - No such object - []", most 
probably because there is no content inside the server yet (no base object, 
users OU or similar).


So I tried to query the server using ldapsearch (from the outside) and got a 
working connection, even with "-ZZ":



$ ldapsearch -x -W -H ldap://my-389ds-server -D "cn=Directory Manager" -ZZ -b 
cn=config

> [...]

# search result
search: 3
result: 0 Success

# numResponses: 161
# numEntries: 160


OK, let's add a base object using ldapadd:


dn: dc=example,dc=com
objectClass: domain
objectClass: dcObject



$ ldapadd -x -f base_only.ldif -D "cn=Directory Manager" -W -H 
ldap://my-389ds-server
Enter LDAP Password: 
adding new entry "dc=example,dc=com"

ldap_add: No such object (32)


I tried different combinations of objectClass'es, but always got error 32.

Question: How do I get content into the server initially? It seems I have an 
empty server, but I found no documentation on what to do at this point.


Am I missing some schema? If so, how would I bootstrap it?

Sorry if those are obvious questions, but either I am lacking the deep LDAP 
knowledge to answer them myself or there is an error in my setup.


Thanks in advance!

Johannes

--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
http://www.b1-systems.de
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


OpenPGP_signature
Description: OpenPGP digital signature
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-users] Re: Running 389ds server in Kubernetes: Questions on certificate names and bootstrapping

2022-03-24 Thread Johannes Kastl


Hi William,

On 23.03.22 at 22:48 William Brown wrote:

Cool, so it sounds like you have it all working then?


Yes, it seems like it. I.e. it is not erroring out and not crashlooping, I can 
get a working TLS connection.


I'll submit an SR for the docker file to include the tar executable, as this is 
needed within Kubernetes to have "kubectl cp" working (copying files to and from 
the container inside the pod, e.g. copying LDIF files or similar).


The next thing I wanna tackle is running without root permissions.

And then I need to figure out how to actually get data into that server. I'll 
open up another thread for that.


Kind Regards,
Johannes

--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg
http://www.b1-systems.de
GF: Ralph Dehner
Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


OpenPGP_signature
Description: OpenPGP digital signature
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: LibreOffice7.3 crashing?

2022-03-24 Thread Thomas Stephen Lee

On Fri, Feb 4, 2022 at 5:10 PM Thomas Stephen Lee  wrote:
>
> On Wed, Feb 2, 2022 at 8:25 PM Michael D. Setzer II via users
>  wrote:
> >
> > Have the Fedora version of LibreOffice working just fine.
> > Also, have the LibreOffice 7.2.5 working just fine.
> > Downloaded the 7.3 and and it seemed to install fine,
> > but attempts to use it result in crash??
> > Restart has it upload, and it successfully submits the
> > crash report, but goes in safe mode, but still crashes?
> > Doesn't seem to show me any info on what the crash is?
> > I've been trying to bring up calc, so perhaps other parts
> > work? This is on fully updated Fedora 34.
> >
> > Uninstalled the 7.3, and have Fedora version and 7.2.5
> > working again. Did try uninstalling 7.2.5 and installing
> > 7.3, but it did same thing.
> >
> > Perhaps the report will tell them something. Just
> > wondering if others might either have same issue, or
> > others have it work?
> >
> > Thanks.
> > ___
>
> Same here in RHEL 8.5.
> Seems to be a LibreOffice bug.
> odt files open, ods files crash.
>
> ---
> Lee

The issue seems to resolved with LO version 7.3.1

---
Lee
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Help configuring internal network

Re: pipewire and wireplumber

Re: pipewire and wireplumber

Re: Help configuring internal network

Re: pipewire and wireplumber

Re: pipewire and wireplumber

Re: pipewire and wireplumber

pipewire and wireplumber

[389-users] Announcing 389 Directory Server 2.1.1

[389-users] Announcing 389 Directory Server 2.0.15

Problem with kernel 5.16.16 not auto booting on 1 machine??

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

Re: Message during dnf update

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: OpenLDAP import into 389 Directory Server failing

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

[389-users] Re: unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

[389-users] unconventional replication, alma 8 master to centos 7 slave: Unable to acquire replica: error: no such replica

Re: Fedora 35 swapon: /swapfile: swapon failed: Invalid argument

[389-users] Re: 389ds for Dummies: How to get started with an empty 389ds server?

[389-users] Re: 389ds for Dummies: How to get started with an empty 389ds server?

[389-users] 389ds for Dummies: How to get started with an empty 389ds server?

[389-users] Re: Running 389ds server in Kubernetes: Questions on certificate names and bootstrapping

Re: LibreOffice7.3 crashing?

30 matches

Site Navigation

Mail list logo

Footer information