slapd crashing and changing permissions on log files
by Elizabeth Jones
We have a 389DS instance that has started having a strange problem when it
runs its backups -
[04/Sep/2014:01:05:01 -0500] - Backup finished.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors) chown failed (13)
Permission denied.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors.20140820-144326) chown
failed (13) Permission denied.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors) chown failed (13)
Permission denied.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors.20140820-144326) chown
failed (13) Permission denied.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors) chown failed (13)
Permission denied.
[04/Sep/2014:05:55:01 -0500] - chown_dir_files: file
(/var/log/dirsrv/slapd-vadc-ldap2-prod/errors.20140820-144326) chown
failed (13) Permission denied.
This is coming from the db2bak.pl backup script. Somehow our log files
are ending up with permissions --------- and then since they can't be
written to the instance crashes.
The only thing that has changed recently on this instance is that we
configured secure replication back to another server (it was already
receiving replication traffic from that server, so now they are able to
replicate back and forth to each other).
We are running
389-ds-base-1.2.11.25-1.el6.x86_64
on
2.6.39-300.26.1.el6uek.x86_64
any suggestions on why this instance has started behaving this way would
be appreciated.
thanks -
EJ
9 years, 7 months
nsslapd-listen-backlog-size on 1.2.11.30
by Michael Gettes
I’m trying to set nsslapd-listen-backlog-size which is documented to change the listen queue backlog.
I have net.core.somaxconn = 8192 and I am trying to set listen-backlog to 4096.
dn: cn=config
cn: config
objectClass: top
objectClass: extensibleObject
objectClass: nsslapdConfig
nsslapd-listen-backlog-size: 4096
…
I get the following:
[02/Sep/2014:18:49:33 -0400] config - Unknown attribute nsslapd-listen-backlog-size will be ignored
[02/Sep/2014:18:49:33 -0400] - 389-Directory/1.2.11.30 B2014.219.205 starting up
[02/Sep/2014:18:49:33 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests
[02/Sep/2014:18:49:33 -0400] - Listening on All Interfaces port 636 for LDAPS requests
Why am I getting the Unknown attribute error? (i feel like i am doing something really stupid here).
/mrg
9 years, 7 months
Configuring interfaces?
by David Barr
Good Morning!
I’m having a bad time finding documentation on how I would set up my 389-ds to only listen to localhost:389, and require all other connections to happen on port 636. The server is headless, so using the console is less than optimum.
Has anything like that been written?
Thanks!
David
--
David - Offbeat http://dafydd.livejournal.com
dafydd - Online http://pgp.mit.edu/
Battalion 4 - Black Rock City Emergency Services Department
Integrity*Commitment*Communication*Support
----5----1----5----2----5----3----5----4----5----5----5----6----5----7--
Dr. Viktor Frankenstein enters into a body building competition
only to find he has seriously misunderstood the objective.
9 years, 7 months
Attribute with Boolean issue
by Chase Miller
Hello,
I have an old fedora directory server, and I'm migrating it to a new
server, and on the new server, I have installed the latest version.
I had a custom attribute with a Boolean data type in the old one, and now,
when I try to ldif import into the new server, I receive an error "value #0
invalid per syntax"
However, I changed the data type to Directory String, and it imports.
Thoughts?
thanks,
Chase
9 years, 7 months
389 upgrades from older versions
by Chase Miller
good thing / bad thing
So I have a fedora directory server version 1.1.0, build date of 2007, and
now I'm trying to migrate to a new server, so I have installed the
latest/greatest. I'm having issues on my ldif imports, it's blowing up on
Boolean string, yet if I change it to Directory string, it will import.
I've banged my head against this for 3 days now. Was wondering about going
to an older version, getting the data imported, then doing the yum upgrade.
Anyone with experience with doing yum upgrades, and did everything work out
in the end. Any gotchas that I might come across?
Chase
9 years, 7 months
Announcing the revised port389.org wiki
by Mark Reynolds
We are pleased to announce the launch of our new wiki
http://www.port389.org
The site has been significantly revised, and moved to a more stable
environment. The layout, content, and organization has all been
improved. Please note, you will need to revise any old bookmarks you
may have, as the old ones will probably not work anymore.
Also, if you would like to add/edit content on the site you just need to
file a ticket <https://fedorahosted.org/389/newticket> (use "wiki" as
the component), add your content(preferably in MarkDown format, but not
required), and we will post it.
Thanks!
389 Project Team
9 years, 7 months
