Closed
Bug 710467
Opened 13 years ago
Closed 13 years ago
slapd segfault causes slapd to not use ca-bundle.crt
Categories
(Participation Infrastructure :: Phonebook, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: ozten, Unassigned)
References
Details
(Whiteboard: [qa-])
As noted in Bug#710466 after a segfault, a slapd server will start to experience SSL Peer verification errors.
Example logs:
Dec 13 16:38:19 mozillians1 browserid-server: curl_easy_perform failed [60] Peer certificate cannot be authenticated with known CA certificates
Dec 13 16:38:19 mozillians1 browserid-server: No dice, STATUS=[curl-error] REASON=[Peer certificate cannot be authenticated with known CA certificates]
Reporter | ||
Comment 1•13 years ago
|
||
@jason or @jabba: Do we have a system in place to restart slapd after a segfault, or is it in a weird post-crash state?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Austin King [:ozten] from comment #1)
via dchan - is it possible slapd gets restart as another user who can't read the ca-bundle.crt?
Comment 3•13 years ago
|
||
Puppet will start slapd if it isn't running, but it will only check into it once per half hour.
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Justin Dow [:jabba] from comment #3)
mozillians-dev is having the same backend error, which I'm guessing is the SSL issue. It seems puppet isn't sufficient for resetting to a working state.
The site does work after jason does a manual restart.
Can we tell puppet to do a restart even if slapd looks "up"?
Comment 5•13 years ago
|
||
Not really. Puppet isn't the right tool for this. You are probably looking for something like monit to watch the process and restart it if problems arise.
Comment 6•13 years ago
|
||
Maybe it's an environment thing?
Can we capture this from a working slapd and a failing slapd?
> xargs -0 -n1 < /proc/$slapd_pid/environ | sort
Reporter | ||
Comment 7•13 years ago
|
||
(In reply to Pete Fritchman [:petef] from comment #6)
$ sudo xargs -0 -n1 < /proc/18166/environ | sort
-bash: /proc/18166/environ: Permission denied
boo.
Reporter | ||
Comment 8•13 years ago
|
||
Based on logs, I don't think that this was actually happening.
master ldap only had 2 SSL failures in it's logs. slapd was running for very little of this week.
Reporter | ||
Comment 9•13 years ago
|
||
Causing segfault with kill -11 and restarting via
* puppet
* /etc/init.d/slapd restart
* services slapd restart
* sudo slapd
I was not able to reproduce this behavior.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Updated•13 years ago
|
Whiteboard: [qa-]
Updated•13 years ago
|
Target Milestone: --- → 1.2
Updated•13 years ago
|
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Target Milestone: 1.2 → ---
Version: unspecified → other
You need to log in
before you can comment on or make changes to this bug.
Description
•