Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Troubleshooting information for systemd integration #4286

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Add Troubleshooting information for systemd integration #4286

sssd-bot opened this issue May 2, 2020 · 0 comments

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3253

  • Created at 2016-12-01 16:37:54 by mkosek
  • Closed at 2020-03-24 14:04:06 as wontfix
  • Assigned to nobody

When #2243 is completed, we should add more troubleshooting related information for SSSD with this integration enabled.

Jakub Hrozek already suggested steps he would do to investigate:

    - inspect sssd.conf
    - systemctl status sssd.service
    - systemctl status sssd-$responder.service
    - journalctl -u sssd.service
    - journalctl -u sssd-$responder.service
    - journalctl -br
    - cross-reference the two above with SSSD debug logs to see if the
      sssd sockets saw any activity

Comments


Comment from jhrozek at 2016-12-02 10:12:03

Fields changed

rhbz: => 0


Comment from jhrozek at 2016-12-08 17:27:46

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.15 Alpha


Comment from jhrozek at 2017-01-25 12:16:37

Fields changed

milestone: SSSD 1.15.0 => SSSD 1.15 Beta


Comment from mkosek at 2017-02-24 14:48:37

Metadata Update from @mkosek:

  • Issue set to the milestone: SSSD 1.15.3

Comment from jhrozek at 2017-03-15 11:03:24

Metadata Update from @jhrozek:

  • Custom field design_review reset
  • Custom field mark reset
  • Custom field patch reset
  • Custom field review reset
  • Custom field sensitive reset
  • Custom field testsupdated reset
  • Issue close_status updated to: None
  • Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

Comment from jhrozek at 2017-08-18 16:54:55

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue tagged with: cleanup-one-sixteen

Comment from jhrozek at 2017-08-23 17:20:53

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue untagged with: cleanup-one-sixteen
  • Issue priority set to: minor (was: major)
  • Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)
  • Issue tagged with: docs

Comment from jhrozek at 2017-10-19 20:45:54

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

Comment from jhrozek at 2017-12-18 20:32:33

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue tagged with: postpone-to-2-0

Comment from jhrozek at 2018-01-08 18:22:43

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue untagged with: postpone-to-2-0
  • Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)

Comment from jhrozek at 2018-08-13 11:02:20

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

Comment from jhrozek at 2019-02-22 15:52:03

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

Comment from jhrozek at 2019-06-13 23:23:53

Metadata Update from @jhrozek:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

Comment from thalman at 2020-03-11 11:29:06

Metadata Update from @thalman:

  • Custom field design_review reset (from false)
  • Custom field mark reset (from false)
  • Custom field patch reset (from false)
  • Custom field review reset (from false)
  • Custom field sensitive reset (from false)
  • Custom field testsupdated reset (from false)
  • Issue tagged with: Canditate to close

Comment from pbrezina at 2020-03-24 14:04:06

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.


Comment from pbrezina at 2020-03-24 14:04:07

Metadata Update from @pbrezina:

  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant