View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002174 | SOGo | Packaging (RedHat) | public | 2013-01-10 15:03 | 2014-12-30 18:21 |
Reporter | ryacketta | Assigned To | ludovic | ||
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | resolved | Resolution | suspended | ||
Product Version | 2.0.3a | ||||
Summary | 0002174: [Red Hat Based OS] init script does not properly shutdown SOGo | ||||
Description | Current init script only kills one PID when setting PREFORK greater then 1 PIDFILE=/var/run/$NAME/$NAME.pid stop() { maybe use something like stop() { | ||||
Additional Information | OS: Running Scientific Linux release 6.2 (Carbon) | ||||
Tags | No tags attached. | ||||
Under normal circumstances, this is the expected behaviour: the init script signals the sogo master process which in turn will signal the childs. This assumes that the childs will process the signal and that they are not stuck in a tight loop. |
|
Ran into the 'hung' process scenario earlier today which lead me down this rabbit whole. Parent was 100% CPU, did a service sogod stop and it only killed the parent while the children remained hanging around. Was forced to killall -u sogo -9. |
|
No change required here. This is the normal behavior. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-01-10 15:03 | ryacketta | New Issue | |
2013-01-10 20:11 |
|
Note Added: 0005126 | |
2013-01-10 20:22 | ryacketta | Note Added: 0005128 | |
2014-12-30 18:21 | ludovic | Note Added: 0007959 | |
2014-12-30 18:21 | ludovic | Status | new => resolved |
2014-12-30 18:21 | ludovic | Resolution | open => suspended |
2014-12-30 18:21 | ludovic | Assigned To | => ludovic |