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

In some conditions, nunc-stans would report a timeout incorrectly #2230

Closed
389-ds-bot opened this issue Sep 13, 2020 · 10 comments
Closed

In some conditions, nunc-stans would report a timeout incorrectly #2230

389-ds-bot opened this issue Sep 13, 2020 · 10 comments
Labels
closed: fixed Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49171


Issue Description

In some conditions we were not handling timeouts correctly: Especially infinite timeouts.

We should improve our check in daemon.c to check for the idletimeout and warn us if this is occuring. We alter the event output function to give us TIMEOUT | (READ, SIGNAL, WRITE), so that we have a clear barrier between the two.

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 01:48:38

0001-Ticket-49171-Nunc-Stans-incorrectly-reports-a-timeou.patch

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 01:48:48

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to new
  • Custom field type adjusted to defect

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 01:49:10

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to review (was: new)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-03-15 02:20:04

48 + slapi_log_err(SLAPI_LOG_ERR, "ns_handle_pr_read_ready", "Recieved idletime out with c->c_idletimeout as 0. Ignoring.\n");

"received" is spelled wrong, and the indentation in daemon.c is off as well.

I'll assume you'll fix these two minor issues, ack.

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-03-15 02:20:14

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to ack (was: review)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-03-15 02:21:33

And that logging line, should we log a warning instead of an error? SLAPI_LOG_WARN?

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 02:49:02

commit c8ce1b3
To ssh://git@pagure.io/389-ds-base.git
c75126b..c8ce1b3 master -> master

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 03:03:29

commit 1d0ff1d
To ssh://git@pagure.io/389-ds-base.git
c8ce1b3..1d0ff1d master -> master

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 05:20:51

Metadata Update from @Firstyear:

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-03-15 05:21:15

Metadata Update from @Firstyear:

  • Issue close_status updated to: fixed
  • 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
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant