Red Hat Bugzilla – Bug 432135
Need better error reporting when stats file can't be accessed
Last modified: 2015-01-04 18:30:42 EST
I missed cleaning up an old DS install completely on my system, which caused
some problems with a new install that were hard to track down. My old install
was configured to run as "nobody", and I forgot to remove the /var/run/dirsrv
directory when I cleaned everything up.
I installed DS again, but this time told it to run as a special "dirsrv" user.
When the server first attempts to start doing setup, it just exits. All the
errors log shows is the "starting up" message.
I then tried to start the server from the debugger, and I see this output in my
Failed to open stats file (/var/run/dirsrv/slapd-test.stats) (error 1).
This message is output to the terminal that you are trying to start DS from, but
I was unable to see it from the installer. Since we can log to the errors log
at this point, it would be nice to output this message there as well.
Or we should just fix https://bugzilla.redhat.com/show_bug.cgi?id=428946
Created attachment 326777 [details]
Log message to errors log instead of to terminal.
Please add the string error message using slapd_system_strerror(err)
Created attachment 326783 [details]
Added text description of system error.
Checked into ldapserver (HEAD). Thanks to Rich and Noriko for their reviews!
Checking in ldap/servers/slapd/snmp_collator.c;
/cvs/dirsec/ldapserver/ldap/servers/slapd/snmp_collator.c,v <-- snmp_collator.c
new revision: 1.19; previous revision: 1.18
Fix verified RHEL 5 DS 8.1
[17/Mar/2009:10:06:08 -0400] - Red Hat-Directory/8.1.0 B2009.076.813 starting up
[17/Mar/2009:10:06:08 -0400] - Failed to delete old semaphore for stats file (/var/run/dirsrv/slapd-jennyv1.stats). Error 13 (Permission denied).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.