ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0022231 | ClearOS | app-radius - RADIUS Server | public | 2018-11-06 07:45 | 2019-04-26 03:54 |
| Reporter | NickH | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | suspended | ||
| Platform | OS | OS Version | |||
| Product Version | 7.5.0 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0022231: When LDAP dies Radius dies | ||||
| Description | If LDAP dies Radius dies. LDAP gets restarted due to servicewatch, but radius does not. The systemd way of fixing this would be to add lines something like: After=slapd.service Requires=slapd.service Restart=always .... but this only works for ldap because of the requires line. It may be possible to remove the Requires. I believe Radius does not work with the AD connector without tweaking so this fix could work. Alternatively we could come quietly and add it to servicewatch. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2018-11-06 07:45 | NickH | New Issue | |||
| 2018-11-06 08:42 | user2 | Status | new => confirmed | ||
| 2018-11-06 08:42 | user2 | Assigned To | => teamindia | ||
| 2018-11-06 08:43 | user2 | Product Version | 7.5.0 Updates => 7.5.0 | ||
| 2019-04-26 03:54 | NickH | Note Added: 0011931 | |||
| 2019-04-26 03:54 | NickH | Status | confirmed => closed | ||
| 2019-04-26 03:54 | NickH | Assigned To | teamindia => | ||
| 2019-04-26 03:54 | NickH | Resolution | open => suspended | ||
| Notes | |||||
|
|
|||||
|
|
||||