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.

Sign up for GitHub

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

Jump to bottom

monitor displays wrong date for connection #4658

Closed
mreynolds389 opened this issue Mar 8, 2021 · 5 comments
Closed

monitor displays wrong date for connection #4658

mreynolds389 opened this issue Mar 8, 2021 · 5 comments
Assignees
@mreynolds389
Labels
priority_high need urgent fix / highly valuable / easy to fix
Milestone
1.4.3

Comments

@mreynolds389
Copy link
Contributor

Issue Description

Looks like a epoch date is used for new connections. Maybe it's related to the REALTIME vs MONOTONIC clock change we did recently?

# dsconf localhost monitor server
dn: cn=monitor
version: 389-Directory/2.0.3.20210306gitf0938dada B2021.065.1543
connection: 472:19700102065831Z:1:1:-:cn=dm:0:0:0:38323:ip=::1
connection: 473:19700102065834Z:3:2:-:cn=dm:0:0:0:38324:ip=local
@mreynolds389 mreynolds389 added the needs triage The issue will be triaged during scrum label Mar 8, 2021
@Firstyear
Copy link
Contributor

I think you're right, it's probably that it's trying to format the monotonic clock against epoch here.

@mreynolds389 mreynolds389 added Need BZ The ticket needs to be cloned to a BZ and removed needs triage The issue will be triaged during scrum labels Mar 11, 2021
@mreynolds389 mreynolds389 added this to the 1.4.3 milestone Mar 11, 2021
@mreynolds389 mreynolds389 self-assigned this Mar 16, 2021
mreynolds389 added a commit that referenced this issue Mar 16, 2021
@mreynolds389
Issue 4658 - monitor - connection start date is incorrect
47a2384 
Description:  The connection start time was incorrectly set to a
              MONTONIC time instead of a REALTIME.  This just sets
              the start time to REALTIME and the "idletimeout" to
              MONOTONIC as originally intended.

Relates: #4658

Reviewed by: mreynolds (one line commit rule)
mreynolds389 added a commit that referenced this issue Mar 16, 2021
@mreynolds389
Issue 4658 - monitor - connection start date is incorrect
a6b7d06 
Description:  The connection start time was incorrectly set to a
              MONTONIC time instead of a REALTIME.  This just sets
              the start time to REALTIME and the "idletimeout" to
              MONOTONIC as originally intended.

Relates: #4658

Reviewed by: mreynolds (one line commit rule)
mreynolds389 added a commit that referenced this issue Mar 16, 2021
@mreynolds389
Issue 4658 - monitor - connection start date is incorrect
11adb2d 
Description:  The connection start time was incorrectly set to a
              MONTONIC time instead of a REALTIME.  This just sets
              the start time to REALTIME and the "idletimeout" to
              MONOTONIC as originally intended.

Relates: #4658

Reviewed by: mreynolds (one line commit rule)
@mreynolds389
Copy link
Contributor Author

1827c76..47a2384 master -> master
6fddab6..a6b7d06 389-ds-base-1.4.4 -> 389-ds-base-1.4.4
015bcc7..11adb2d 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

@mreynolds389
Copy link
Contributor Author

Need to create downstream bugzillas going back to 8.3

@tbordaz tbordaz added the priority_high need urgent fix / highly valuable / easy to fix label Mar 25, 2021
@mreynolds389
Copy link
Contributor Author

Downstream bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1990002

@tbordaz
Copy link
Contributor

tbordaz commented Feb 9, 2022

This bug is fixed upstream and the BZ verified => close
1827c76..47a2384 master
6fddab6..a6b7d06 1.4.4
015bcc7..11adb2d 1.4.3

@tbordaz tbordaz closed this as completed Feb 9, 2022
@tbordaz tbordaz removed the Need BZ The ticket needs to be cloned to a BZ label Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mreynolds389 mreynolds389

Labels
priority_high need urgent fix / highly valuable / easy to fix
Projects
None yet
Milestone
1.4.3
Development

No branches or pull requests
3 participants
@Firstyear @mreynolds389 @tbordaz