[389-users] Re: BER Size

xbersize attribute in > cn=config to increase. Is this connection coming from the other master? Or some client connection? > > >> On Dec 6, 2017, at 10:47 AM, Viktor Ashirov <vashi...@redhat.com> wrote: >> >> Hi, >> On Wed, Dec 06 2017 at 10:34:05 -0600, Sergei Ge

[389-users] Re: BER Size

Hi, On Wed, Dec 06 2017 at 10:34:05 -0600, Sergei Gerasenko wrote: > Hi, > > I just discovered that I have a mismatch of BER sizes (nsslapd-maxbersize) > between some of my masters. On the masters that we consider the authorative > ones, the BER size is (cough, cough) 209M

[389-users] Re: tls encryption and key changes: symmetric key failed to unwrap

Hi, On Fri, Jun 01 2018 at 12:06:50 +0200, Jan Kowalsky wrote: > Hi all, > > we have the following situation: An 389ds with tls/ssl configured whith > an certificate from letsencrypt. > > Since letsencrypt is short-dated we have an automated update routine for > regenerating the cert8.db. > >

[389-users] Re: Server Group empty in 389 Management Console for windows

Hi, On Thu, Dec 6, 2018 at 6:00 AM Jason Jenkins wrote: > Exception in thread "AWT-EventQueue-0" > java.lang.UnsupportedClassVersionError: c > > om/netscape/management/admserv/AdminServer : Unsupported major.minor > version 51. > > 0 > Was there any change (upgrade/downgrade) of JRE on a system

[389-users] Re: Looking for installation documentation for CentOS 7

Hello, On Wed, Aug 14, 2019 at 1:56 PM Dan White wrote: > https://www.port389.org/docs/389ds/howto/howto-install-389.html appears > to be geared toward 389-*-1.4.x > while https://www.port389.org/docs/389ds/legacy/install-guide.html does > not seem to reference anything past RHEL 4 > > I was

[389-users] Re: Latest Version of 389-ds-base for CentOS 7

On Mon, Jul 8, 2019 at 7:17 PM Paul Whitney wrote: > I was looking up the latest version of 389-ds and noticed that an update > has not been released since March 2019. Has there not been anymore updates > to this bundle? > There is an update to 389-ds-base in the upcoming batch update for RHEL

[389-users] Re: Using sec-activate to enable SSL for admin server

Hi Grant, On Thu, Nov 7, 2019 at 2:16 AM Grant Byers wrote: > Hi Mark, > > > > I am using certutil and a pin file, but that’s only half of what’s > required. The other half involves adding and/or amending entries in the > local and adm bootstrap configs, in the global config database >

[389-users] Re: Building 389 rpm on CentOS 8 from source rpm

Hi Andrey, argparse-manpage is missing in EPEL8: https://bugzilla.redhat.com/show_bug.cgi?id=1763246 I was able to rebuild fedora srpm in my copr: https://copr.fedorainfracloud.org/coprs/vashirov/389ds/packages/ But 389-ds-base build fails further down due to other missing dependencies, please

[389-users] Re: cockpit problems

Hi, On Thu, Dec 12, 2019 at 5:18 PM Alberto Viana wrote: > Hi Guys, > > I have installed 389 from source (389-Directory/1.4.2.4 B2019.344.19) > > Installed 389-ds cockpit plugin via npm e copy > to /usr/share/cockpit/389-console/ > > cockpit-195.1-1.el7.centos.0.1.x86_64 > > When I login into

[389-users] Re: When 389ds will be available on CentOS 8

Hi, On Tue, Oct 29, 2019 at 11:34 AM wodel youchi wrote: > Hi, > > Any idea when the cockpit plugin for 389DS will be available on CentOS8? > Unfortunately, it's a bit complicated right now. There is no timeline yet, but we're working on it. Some of the blockers: 1. argparse-manpage is missing

[389-users] Re: When 389ds will be available on CentOS 8

On Tue, Oct 29, 2019 at 1:02 PM Viktor Ashirov wrote: > Hi, > > On Tue, Oct 29, 2019 at 11:34 AM wodel youchi > wrote: > >> Hi, >> >> Any idea when the cockpit plugin for 389DS will be available on CentOS8? >> > Unfortunately, it's a bit compl

[389-users] Re: healthcheck problems

On Thu, Jan 23, 2020 at 8:34 PM Mark Reynolds wrote: > > On 1/23/20 1:17 PM, Alberto Viana wrote: > > Mark, > > I using python3-lib389-1.4.3.1-20200116gita08202a5b.el8.noarch > python3.6 > > And still got the same error: > > DEBUG: [Errno 2] No such file or directory: >

[389-users] Re: DB problems

On Fri, Jan 17, 2020 at 3:56 PM Alberto Viana wrote: > Hi Guys, > > 389-Directory/1.4.3.1.20200116git4f9aafca9 > > Start to get this error: > [17/Jan/2020:11:49:56.436658541 -0300] - NOTICE - bdb_start - Detected > Disorderly Shutdown last time Directory Server was running, recovering >

[389-users] Re: New Instance errors

Hi, On Fri, Apr 10, 2020 at 11:48 PM Nick Bright wrote: > Greetings, > > I've performed a fresh CentOS 8 installation within VMWare, updated the OS > fully, installed 389-ds through yum by: yum module install > 389-directory-server:stable/default > > This installed the server, along with the

[389-users] Re: dsconf broken for ldaps instances in 1.4.3 but working in 1.4.2

On Wed, Nov 25, 2020 at 1:16 AM William Brown wrote: > > > > On 25 Nov 2020, at 01:08, Ivanov Andrey (M.) < > andrey.iva...@polytechnique.fr> wrote: > > > > > > But all in all i think i start to see where the problem comes from. > dsconf version 1.4.2 uses /etc/openldap/ldap.conf (which in turn

[389-users] Re: Fwd: How to manage 389DS on CentOS8 ?

On Thu, Nov 19, 2020 at 2:10 PM Mark Reynolds wrote: > Forwarding to the correct list... > > > Forwarded Message > Subject: How to manage 389DS on CentOS8 ? > Date: Thu, 19 Nov 2020 07:04:45 -0400 > From: Alix FALEME > To: 389-users-ow...@lists.fedoraproject.org >

[389-users] Re: Fwd: How to manage 389DS on CentOS8 ?

show_bug.cgi?id=1654238 In the meantime I recommend to use Apache Directory Studio: https://directory.apache.org/studio/ HTH > > CentOS7 have 389console package for exemple. > > > > Le jeu. 19 nov. 2020 à 10:03, Viktor Ashirov a > écrit : > >> >> >> >

[389-users] Re: Cockpit and 389

On Thu, Jul 8, 2021 at 8:34 PM Gary Waters wrote: > I was pointed at EPEL8. It appears that the packages are being uploaded > to all the mirrors as el8. > > https://download.fedoraproject.org/pub/epel/8/Modular/x86_64/ > > Can the RHEL9 versions be built into epel/9 instead ? > There is no EPEL9

[389-users] Re: Lock table is out of available lock entries

On Mon, Oct 11, 2021 at 8:33 PM Mark Reynolds wrote: > > On 10/11/21 2:29 PM, Kees Bakker wrote: > > On 11-08-2021 15:21, Mark Reynolds wrote: > > On 8/11/21 9:09 AM, Pierre Rogier wrote: > > Hi, > I suspect that Kees discovered a new bug ... > > As the retro changelog is persistent across

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

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

[389-users] Re: version changes/updates

Hi, On Thu, 31 Mar 2022 at 15:27, Neel Karandikar wrote: > Hello > > > > > > At what point did the repo installation “stable/default” change from > 1.4.4.17 to 2.0.x? > As described in https://www.port389.org/docs/389ds/download.html#centos-81-ds-14x, "stable" stream follows the oldest of the

[389-users] Re: Announcing 389 Directory Server 2.0.13

On Mon, Jan 24, 2022 at 11:13 PM Mark Reynolds wrote: > > This build needs to go through testing now that is built. Once it passes > Fedora testing, and it does not receive any negative karma then we will do > the EPEL builds that should get picked up in Centos 8 (eventually). We have > no

[389-users] Re: 389DS on K8s - dirserv won't start

On Thu, Sep 1, 2022 at 4:24 PM Ronald Wimmer wrote: > Thanks for pointing us in the right direction. We are proxying quay.io > and dockerhub through a local artifactory instance. We accidentally used > the Dockerhub URL instead of the quay.io URL. After correcting the path > everything works as

[389-users] Re: 389DS on K8s - dirserv won't start

On Thu, Sep 1, 2022 at 2:34 PM Ronald Wimmer wrote: > On 01.09.22 14:23, Viktor Ashirov wrote: > > On Thu, Sep 1, 2022 at 2:05 PM Ronald Wimmer wrote: > > > >> On 01.09.22 13:41, Viktor Ashirov wrote: > >>> On Thu, Sep 1, 2022 at 1:24 PM Ronald Wimmer wrote

[389-users] Re: 389DS on K8s - dirserv won't start

On Thu, Sep 1, 2022 at 2:05 PM Ronald Wimmer wrote: > On 01.09.22 13:41, Viktor Ashirov wrote: > > On Thu, Sep 1, 2022 at 1:24 PM Ronald Wimmer wrote: > > > >> We stuck to the guide on > >> > https://directory.fedoraproject.org/docs/389ds/howto/

[389-users] Re: 389DS on K8s - dirserv won't start

On Thu, Sep 1, 2022 at 1:24 PM Ronald Wimmer wrote: > We stuck to the guide on > https://directory.fedoraproject.org/docs/389ds/howto/howto-deploy-389ds-on-openshift.html > but tried to leave out LDAPs and all the certificate stuff for now. Pod is > starting but crashes immediately with the

[389-users] Re: 389ds memory limits in kubernetes

Hi, On Mon, Oct 17, 2022 at 1:14 PM Juan R Moral wrote: > Hello, > > 389ds docker image acts different in hosts with different amount of memory. > > For example in minikube with 8Gi nodes and limit 6Gi work wells. But in > a kubernetes cluster with 256Gi nodes and limit 6Gi Pod is contantly >

[389-users] Re: 389ds memory limits in kubernetes

r: You have 4k entries, you run ldapsearch command from the first message in a loop, and over several hours the resident memory of ns-slapd increases? Thanks. > Regards > El 17/10/2022 a las 13:42, Viktor Ashirov escribió: > > Hi, > > On Mon, Oct 17, 2022 at 1:14 PM Juan

[389-users] Re: I have some problem with 389 Directory Server container project

On Wed, Aug 3, 2022 at 11:31 AM hu xudong wrote: > Does it work on a different Ubuntu 18.04 instance? > what do you mean? > Can you try to run this on a different VM with Ubuntu 18.04? You mentioned that it works on Centos 7, but not on Ubuntu 18.04. I've tried to run the container in Ubuntu

[389-users] Re: 389-ds-base/cockpit-389-ds on EL9

Hi, On Wed, Aug 10, 2022 at 4:54 PM Daniel Bird wrote: > Hello all, > > I thought I’d test a build of 389-ds on Alma/Rocky Linux 9, as we’re > looking to start the upgrade process from our CentOS 7 hosts soon. > > > > Instructions for CentOS8.1+ do not work; not that I expected them to, but >

[389-users] Re: 389-ds-base/cockpit-389-ds on EL9

Hi, I've created 2 copr repositories for CentOS Stream 9 and EL9: https://copr.fedorainfracloud.org/coprs/g/389ds/389-directory-server/ - contains rebuilds of 389-ds-base and cockpit-389-ds from the latest stable Fedora release (F36 at the moment, will be switched to the next version once

[389-users] Re: I have some problem with 389 Directory Server container project

Hi On Wed, Aug 3, 2022 at 9:41 AM Hu, Xudong wrote: > > Hi ,I want to ask a question > When I use docker pull 389ds/dirsrv to install 389ds,then I use docker > run 389ds/dirsrv:latest command > > What is the exact sha256 checksum of the image? docker inspect 389ds/dirsrv --format='{{index

[389-users] Re: I have some problem with 389 Directory Server container project

On Wed, Aug 3, 2022 at 10:31 AM hu xudong wrote: > I pull from dockhub just now ,when I use docker inspect 389ds/dirsrv > --format='{{index .RepoDigests 0}}' > > the result is : 389ds/dirsrv@sha256 > :ea9bba8d7e23a0ecb63a000765d9f70f7d555fbb073bde684496011677e40df3 > Okay, I've just tested this

[389-users] Re: I have some problem with 389 Directory Server container project

Does it work on a different Ubuntu 18.04 instance? What is the exact docker command that you use to start the container? What is the backing filesystem for your storage? Should be in `docker info`. On Wed, Aug 3, 2022 at 10:41 AM hu xudong wrote: > the complete start log is as follows: > --

[389-users] Re: Builds for EL8 have a new home

Hi, On Tue, Dec 13, 2022 at 4:25 PM Rosario Esposito wrote: > Hello, > I have a question. > With EPEL8 modular, when I want to do a fresh 389ds installation i use the > command: > dnf module install 389-directory-server:stable/default > which provides 389ds version 2.0.15 > > Now, if I do a

[389-users] Builds for EL8 have a new home

Hello, epel-modular repository for EL8 was discontinued: https://pagure.io/epel/issue/198 On February 15, 2023 EPEL 8 modules will be archived and removed: https://lists.centos.org/pipermail/centos-devel/2022-October/120635.html See the forwarded email below for more details. This means we can

[389-users] Re: 389ds container images and tags

Hi Johannes, On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl wrote: > Hi all, > > I am in the process of rewriting my helm chart for 389ds (stay tuned, I'll > send > another mail once it is ready), and noticed the lack of recent tags for > the > container images: > Oh, nice! Looking forward to

[389-users] Re: 389ds container images and tags

On Tue, Apr 18, 2023 at 9:13 AM Johannes Kastl wrote: > Hi Viktor, > > On 18.04.23 at 09:02 Viktor Ashirov wrote: > > > On Tue, Apr 18, 2023 at 8:15 AM Johannes Kastl > wrote: > > >> https://hub.docker.com/r/389ds/dirsrv only has 2.1, 2.2 and latest. 2.2 >

[389-users] Re: 389-DS Cockpit

Hi, On Fri, Feb 10, 2023 at 2:47 PM Rosario Esposito wrote: > Hello, > > I read from https://directory.fedoraproject.org/docs/389ds/download.html > "cockpit-389-ds is not distributed in AppStream." > > I just downloaded the current 389-ds-base source rpm from Appstream: >

[389-users] Re: Fwd: dscontainer as non root

> > > > On Mon, Feb 12, 2024 at 9:38 PM Viktor Ashirov > wrote: > >> Hi Antony, >> >> On Mon, Feb 12, 2024 at 3:37 PM Mark Reynolds >> wrote: >> >>> Forwarding to the correct list >>> >>> >>> Forwarded

[389-users] Re: Fwd: dscontainer as non root

Hi Antony, On Mon, Feb 12, 2024 at 3:37 PM Mark Reynolds wrote: > Forwarding to the correct list > > > Forwarded Message > Subject: dscontainer as non root > Date: Mon, 12 Feb 2024 20:01:09 +0530 > From: Antony Jose > To: 389-users-ow...@lists.fedoraproject.org > > Hi, >

[389-users] Re: 389-ds-base name log pipe problems

On Thu, Dec 7, 2023 at 11:25 AM Nyquist wrote: > > 1. Stop directory server and remove access log file. > 2. Run logpipe.py. Python create access.pipe (pipe) > 3. Change directory server settings > nsslapd-accesslog-maxlogsperdir: 1 > nsslapd-accesslog-logexpirationtime: -1 >

[389-users] Re: Question about @389ds/389-directory-server copr repository

Hi Rosario, On Wed, Dec 6, 2023 at 2:02 PM Rosario Esposito wrote: > Thanks a lot Viktor, I was able to downgrade to 2.2.9 and now my server is > running fine. > Good to hear! I'll be waiting for the issue to be fixed in a future release. > Maybe it's not worth to keep 2.3.7 rpms in the

[389-users] Announcing 389 Directory Server 2.4.5

389 Directory Server 2.4.5 The 389 Directory Server team is proud to announce 389-ds-base version 2.4.5 Fedora packages are available on Fedora 39 and Rawhide. Fedora 39: https://koji.fedoraproject.org/koji/taskinfo?taskID=111921314 - Koji

[389-users] Re: Question about @389ds/389-directory-server copr repository

Hi Rosario, On Wed, Dec 6, 2023 at 12:12 PM Rosario Esposito wrote: > Hello, > > I was running 389-ds 2.2.8 on a RockyLinux 8 machine. > I updated to 389-ds 2.3.7 using copr EPEL-8 repository. > Unfortunately I'm experiencing issues with the new version: >