[389-users] 389-ds-base-1.3.5.4 doesn't build on Mageia
389-ds-base-1.3.5.4 doesn't build on Mageia
Altlinux reported the same problem with 389-ds-base-1.3.5.3
This is the error:
/libslapd_la-ssl.o
ldap/servers/slapd/ssl.c: In function 'svrcore_setup':
ldap/servers/slapd/ssl.c:1291:5: error: unknown type name
'SVRCOREStdSystemdPinObj'
SVRCOREStdSystemdPinObj *StdPinObj;
^
ldap/servers/slapd/ssl.c:1292:18: error: 'SVRCOREStdSystemdPinObj' undeclared
(first use in this function)
StdPinObj = (SVRCOREStdSystemdPinObj *)SVRCORE_GetRegisteredPinObj();
See log
http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20160528191035.spuhler.duvel.44896/log/389-ds-base-1.3.5.4-1.mga6/build.0.20160528191128.log
The attached patch makes it build
--
Best regards
Thomas Spuhler
All of my e-mails have a valid digital signature
ID 60114E63diff -Nru a/ldap/servers/slapd/ssl.c b/ldap/servers/slapd/ssl.c
--- a/ldap/servers/slapd/ssl.c 2016-05-18 19:35:32.0 +0200
+++ b/ldap/servers/slapd/ssl.c 2016-05-28 21:59:44.893347003 +0200
@@ -1287,7 +1287,7 @@
{
PRErrorCode errorCode;
int rv = 0;
-#ifdef WITH_SYSTEMD
+#ifndef WITH_SYSTEMD
SVRCOREStdSystemdPinObj *StdPinObj;
StdPinObj = (SVRCOREStdSystemdPinObj *)SVRCORE_GetRegisteredPinObj();
#else
@@ -1298,7 +1298,7 @@
if (StdPinObj) {
return 0; /* already registered */
}
-#ifdef WITH_SYSTEMD
+#ifndef WITH_SYSTEMD
if ( SVRCORE_CreateStdSystemdPinObj(, dongle_file_name, PR_TRUE, PR_TRUE, 90) != SVRCORE_Success) {
#else
if ( SVRCORE_CreateStdPinObj(, dongle_file_name, PR_TRUE) != SVRCORE_Success) {
signature.asc
Description: This is a digitally signed message part.
--
389-users mailing list
389-users@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org
[389-users] Re: 389-ds crash
On Monday, January 11, 2016 02:47:07 PM Todor Petkov wrote: > Hello, > > few days ago, as today, the ldap process crashed. I found this in > /var/log/messages: > > Jan 6 17:26:24 ds1 kernel: ns-slapd[18010] trap invalid opcode > ip:7f1372fabd60 sp:7f13499e7518 error:0 in > libfreeblpriv3.so[7f1372f59000+72000] > Jan 11 14:28:41 ds1 kernel: ns-slapd[14263] trap invalid opcode > ip:7f852c56fd60 sp:7f85037ea518 error:0 in > libfreeblpriv3.so[7f852c51d000+72000] > > There is no process in the memory, so I had to do "service dirsrv > restart" > > Does someone else have the same problem(s)? I see there are updates for > ds-base and ds-base-libs, and I will update later. > > Here is more information about my setup: > OS: Centos 6, > kernel: 2.6.32-431.17.1.el6.x86_64 > > 389-ds packages: > 389-admin-console-1.1.8-1.el6.noarch > 389-ds-1.2.2-1.el6.noarch > 389-ds-base-libs-1.2.11.15-65.el6_7.x86_64 > 389-adminutil-1.1.19-1.el6.x86_64 > 389-ds-console-1.2.6-1.el6.noarch > 389-admin-console-doc-1.1.8-1.el6.noarch > 389-admin-1.1.35-1.el6.x86_64 > 389-ds-base-1.2.11.15-65.el6_7.x86_64 > 389-console-1.1.7-1.el6.noarch > 389-ds-console-doc-1.2.6-1.el6.noarch > 389-dsgw-1.1.11-1.el6.x86_64 > > > Regards, > > -- > 389 users mailing list > 389-users@%(host_name)s > http://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org I don't have any crashes, but I also don't have libfreeblpriv What package provides this? -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@lists.fedoraproject.org
Re: [389-users] Announcing 389 Directory Server version 1.3.4.0
all the nunc-stans signal jobs when shutdown is detected * Ticket 48111 - “make clean” wipes out original files * Ticket 48122 - nunc-stans FD leak * Ticket 48127 - Using RPM, allows non root user to create/remove DS instance * Ticket 48141 - aci with wildcard and macro not correctly evaluated * Ticket 48143 - Password is not correctly passed to perl command line tools if it contains shell special characters. * Ticket 48149 - ns-slapd double free or corruption crash * Ticket 48154 - abort cleanAllRUV tasks should not certify-all by default * Ticket 48169 - support NSS 3.18 * Ticket 48170 - Parse nsIndexType correctly * Ticket 48175 - Avoid using regex in ACL if possible * Ticket 48178 - add config param to enable nunc-stans * Ticket 48191 - CI test: added test cases for ticket 48191 * Ticket 48191 - RFE: Adding nsslapd-maxsimplepaged-per-conn * Ticket 48191 - RFE: Adding nsslapd-maxsimplepaged-per-conn Adding nsslapd-maxsimplepaged-per-conn * Ticket 48194 - CI test: added test cases for ticket 48194 * Ticket 48197 - error texts from preop plugins not sent to client http://www.port389.org/docs/389ds/releases/release-1-3-4-0.html Has anybody seen build problems for 32bit Build Servers? It's the nunc-stans part. The errors are: In file included from src/liblfds_internal.h:2:0, from src/ringbuffer/ringbuffer_internal.h:2, from src/ringbuffer/ringbuffer_delete.c:1: inc/liblfds.h:124:5: error: unknown type name 'atom_t' atom_t ^ inc/liblfds.h:131:37: error: unknown type name 'size_t' void *abstraction_aligned_malloc( size_t size, size_t align_in_bytes ); -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Announcing 389 Directory Server version 1.3.4.0
On Monday, June 22, 2015 05:30:10 PM Rich Megginson wrote: On 06/22/2015 05:13 PM, Thomas Spuhler wrote: On Saturday, June 20, 2015 04:40:58 PM Noriko Hosoi wrote: 389 Directory Server 1.3.4.0 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.4.0. Fedora packages are available from the Fedora 22 and Rawhide repositories. The new packages and versions are: * 389-ds-base-1.3.4.0-1 Source tarballs are available for download at Download 389-ds-base Source http://www.port389.org/binaries/389-ds-base-1.3.4.0.tar.bz2 and Download nunc-stans Source http://www.port389.org/binaries/nunc-stans-0.1.4.tar.bz2. Highlights in 1.3.4.0 * A new version is available featuring Nunc Stans http://www.port389.org/docs/389ds/design/nunc-stans.html. Installation and Upgrade See Download http://www.port389.org/docs/389ds/download.html for information about setting up your yum repositories. To install, use *yum install 389-ds* yum install 389-ds After install completes, run *setup-ds-admin.pl* to set up your directory server. setup-ds-admin.pl To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run *setup-ds-admin.pl -u* to update your directory server/admin server/console information. setup-ds-admin.pl -u See Install_Guide http://www.port389.org/docs/389ds/legacy/install-guide.html for more information about the initial installation, setup, and upgrade See Source http://www.port389.org/docs/389ds/development/source.html 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://admin.fedoraproject.org/mailman/listinfo/389-users as well as https://admin.fedoraproject.org/updates/389-ds-base-1.3.4.0-1.fc22 https://admin.fedoraproject.org/updates/389-ds-base-1.3.4.0-1.fc22. If you find a bug, or would like to see a new feature, file it in our Trac instance: https://fedorahosted.org/389 Detailed Changelog since 1.3.3.12 * Enable nunc-stans in the build. * Ticket 47490 - test case failing if 47721 is also fixed * Ticket 47640 - Linked attributes transaction not aborted when linked entry does not exit * Ticket 47669 - CI test: added test cases for ticket 47669 * Ticket 47669 - Retro Changelog Plugin accepts invalid value in nsslapd-changelogmaxage attribute * Ticket 47723 - winsync sets AccountUserControl in AD to 544 * Ticket 47787 - Make the test case more robust * Ticket 47833 - TEST CASE only (modrdn fails if renamed entry member of a group and is out of memberof scope) * Ticket 47878 - Improve setup-ds update logging * Ticket 47893 - should use Sys::Hostname instead Net::Domain * Ticket 47910 - allow logconv.pl -S/-E switches to work even when timestamps not present in access log * Ticket 47913 - remove-ds.pl should not remove /var/lib/dirsrv * Ticket 47921 - indirect cos does not reflect changes in the cos attribute * Ticket 47927 - Uniqueness plugin: should allow to exclude some subtrees from its scope * Ticket 47953 - testcase for removing invalid aci * Ticket 47966 - CI test: added test cases for ticket 47966 * Ticket 47966 - slapd crashes during Dogtag clone reinstallation * Ticket 47972 - make parsing of nsslapd-changelogmaxage more fault tolerant * Ticket 47972 - make parsing of nsslapd-changelogmaxage more fool proof * Ticket 47998 - cleanup WINDOWS ifdef’s * Ticket 47998 - remove remaining obsolete OS code/files * Ticket 47998 - remove “windows” files * Ticket 47999 - address several race conditions in tests * Ticket 47999 - lib389 individual tests not running correctly when run as a whole * Ticket 48003 - build “suite” framework * Ticket 48008 - db2bak.pl man page should be improved. * Ticket 48017 - add script to generate lib389 CI test script * Ticket 48019 - Remove refs to constants.py and backup/restore from lib389 tests * Ticket 48023 - replace old replication check with lib389 function * Ticket 48025 - add an option ‘-u’ to dbgen.pl for adding group entries with uniquemembers * Ticket 48026 - fix invalid write for friendly attribute names * Ticket 48026 - Fix memory leak in uniqueness plugin * Ticket 48026 - Support for uniqueness plugin to enforce uniqueness on a set of attributes. * Ticket 48032 - change C code license to GPLv3; change C code license to allow openssl * Ticket 48035 - nunc-stans - Revise shutdown sequence * Ticket 48036 - ns_set_shutdown should
Re: [389-users] problems building RPM for 389-admin
On Sunday, April 26, 2015 02:39:47 PM Giovanni Baruzzi wrote:
Hi all,
sorry for a newcomer question.
After having built the RPM for 389-ds-base and 389-adminutil I’m stuck with a
problem with
389-admin.
I was not able to find an „official“ SPEC file and I resorted to one found
somewhere
in Internet. The problem is that this file requires the definition of the
macro %{_unitdir},
which apparetnly is not defined anymore (?) for Fedora.
How can I solve the problem?
Is there a location for the „official“ spec files?
http://pkgs.fedoraproject.org/cgit/389-admin.git/tree/
thank you,
Giovanni
--
Best regards
Thomas Spuhler
All of my e-mails have a valid digital signature
ID 60114E63
signature.asc
Description: This is a digitally signed message part.
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] selinux problem with centos 7.1
On Friday, April 17, 2015 03:27:05 PM Angel Bosch wrote:
hi,
I'm having problems installing a new test environment on centos 7.1
when I execute setup-ds-admin.pl i get this message:
Adding port 389 to selinux policy failed - ValueError: SELinux policy is
not managed or store
cannot be accessed.
I've tried with --debug and it keeps retrying every 5 seconds with same
message.
# lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.1.1503 (Core)
Release: 7.1.1503
Codename: Core
# sestatus
SELinux status: disabled
the only irregular thing is that im using an openvz container, but I have
plenty of other DS
inside openvz without any problems.
i managed to continue with the installation with a very dirty hack, I
modified DSCreate.pm script
and added a return in the beggining of updateSelinuxPolicy sub:
sub updateSelinuxPolicy {
my $inf = shift;
return 0;
did anyone got this same problem?
abosch
I went through this with Mageia. You either need to enable selinux (permissive)
or compile 389-ds
without selinux.
--
Best regards
Thomas Spuhler
All of my e-mails have a valid digital signature
ID 60114E63
signature.asc
Description: This is a digitally signed message part.
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] selinux problem with centos 7.1
On Friday, April 17, 2015 04:19:47 PM Angel Bosch wrote: I went through this with Mageia. You either need to enable selinux (permissive) or compile 389-ds without selinux. do you mean I won't be able to execute it without selinux? or is just the installer? abosch -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users I think, it is just the installer. But I ended up to just build all the 389-ds packages without selinux Use the srpms, remove the --with-selinux line in the configure and build it. if your not using it anyway. -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] 389-admin-1.1.38 setup problems
On Monday, March 23, 2015 09:15:02 AM Noriko Hosoi wrote: On 03/22/2015 12:00 PM, Thomas Spuhler wrote: On Saturday, March 21, 2015 04:46:17 PM Thomas Spuhler wrote: setup-ds-admin.pl returns an error. I packaged the new version of 389-admin-1.1.38 for Mageia (security update) and when running the setup script I am getting the error: httpd: Syntax error on line 136 of /etc/dirsrv/admin-serv/httpd.conf: Cannot load /usr/lib64/dirsrv/modules/mod_admserv.so into server: /usr/lib64/dirsrv/modules/mod_admserv.so: undefined symbol: admldapGetAuthDN I have not updated 389-adminutil as the fedora spec file doesn't require it. Could this be the problem? I have resolved it by upgrading 389-adminutil to vers. 1.1.21. I couldn't find this as requirement anywhere, Thank you for upgrading to 389-admin-1.1.38. Sorry about the inconvenience. We released and announced the version of 389-admin and adminutil-1.1.21 together, which are to be upgraded at the same time: http://www.port389.org/docs/389ds/releases/release-admin-1-1-38.html Thanks, --noriko -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users Thanks for the feedback. I put a requirement into our spec file (mageia) to be safe. -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] 389-console moves to background after opening
When I open the the 389-console as root, I get a brief flash and then it moves to the background. Is this expected or did I package it wrong? I have currently 389-console-1.1.7 -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] 389-admin-1.1.38 setup problems
On Saturday, March 21, 2015 04:46:17 PM Thomas Spuhler wrote: setup-ds-admin.pl returns an error. I packaged the new version of 389-admin-1.1.38 for Mageia (security update) and when running the setup script I am getting the error: httpd: Syntax error on line 136 of /etc/dirsrv/admin-serv/httpd.conf: Cannot load /usr/lib64/dirsrv/modules/mod_admserv.so into server: /usr/lib64/dirsrv/modules/mod_admserv.so: undefined symbol: admldapGetAuthDN I have not updated 389-adminutil as the fedora spec file doesn't require it. Could this be the problem? I have resolved it by upgrading 389-adminutil to vers. 1.1.21. I couldn't find this as requirement anywhere, -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
[389-users] 389-admin-1.1.38 setup problems
setup-ds-admin.pl returns an error. I packaged the new version of 389-admin-1.1.38 for Mageia (security update) and when running the setup script I am getting the error: httpd: Syntax error on line 136 of /etc/dirsrv/admin-serv/httpd.conf: Cannot load /usr/lib64/dirsrv/modules/mod_admserv.so into server: /usr/lib64/dirsrv/modules/mod_admserv.so: undefined symbol: admldapGetAuthDN I have not updated 389-adminutil as the fedora spec file doesn't require it. Could this be the problem? -- Best regards Thomas Spuhler All of my e-mails have a valid digital signature ID 60114E63 signature.asc Description: This is a digitally signed message part. -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
