Bug #40644
Get samba_server status when checking if AD started
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
VNQ-960-98926
Hardware Configuration:
ChangeLog Required:
No
Description
Parent smbd occasionally exits on signal 6. Have not completed root cause analysis of this yet. Separate bug ticket. This results in shares being inaccessible. Customer asked for script to restart samba if it enters this state. Existing logic in AD monitoring does not catch this situation.
Arguably this is should be monitored separately (i.e. part of smb monitoring, not AD monitoring), but AD exists and monitoring is being rewritten in the future. The simple fix to this is to add additional check for samba_server status. This has added advantage of perhaps getting us out having to do a full restart of Active Directory when it's not warranted.
Related issues
Associated revisions
(11.1-stable)
Ticket: #40644
History
#1
Updated by John Hixson about 2 years ago
Updated by John Hixson - Copied from Bug #34411: Get samba_server status when checking if AD started added
#2
Updated by John Hixson about 2 years ago
11.1-stable PR: https://github.com/freenas/freenas/pull/1629
#3
Updated by Dru Lavigne about 2 years ago
Updated by Dru Lavigne - Status changed from Unscreened to In Progress
- Needs QA changed from No to Yes
- Needs Merging changed from No to Yes
#4
Updated by Dru Lavigne about 2 years ago
- Assignee changed from Andrew Walker to John Hixson
#5
Updated by Dru Lavigne about 2 years ago
- Status changed from In Progress to Ready for Testing
- Needs Merging changed from Yes to No
#7
Updated by Bonnie Follweiler about 2 years ago
Updated by Bonnie Follweiler - Status changed from Ready for Testing to Passed Testing
- Needs QA changed from Yes to No
#9
Updated by Dru Lavigne about 2 years ago
- Status changed from Passed Testing to Done