Bug 1672167

Summary: Negative timeout printed while setting an entry in the cache file
Product: Red Hat Enterprise Linux 8 Reporter: amitkuma
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED ERRATA QA Contact: Andrej Dzilský <adzilsky>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: asn, dpal, gdeschner, jarrpa, jstephen
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: samba-4.10.4-0.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:19:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1682298    
Bug Blocks:    

Description amitkuma 2019-02-04 07:04:45 UTC 
Description of problem:
[2019/02/04 01:38:09.894983, 10, pid=9358, effective(0, 0), real(0, 0), class=tdb] ../source3/lib/gencache.c:301(gencache_set_data_blob)
  Adding cache entry with key=[IDMAP/SID2XID/S-1-5-21-4006949566-962402297-1653548521-1109] and timeout=[Wed Dec 31 07:00:00 PM 1969 EST] (-1549262289 seconds in the past)


        DEBUG(10, ("Adding cache entry with key=[%s] and timeout="
                   "[%s] (%d seconds %s)\n", keystr,
                   timestring(talloc_tos(), timeout),
                   (int)(timeout - time(NULL)),
                   timeout > time(NULL) ? "ahead" : "in the past"));

Looks wrong format specifier chosen for printing timeout.

Version-Release number of selected component (if applicable):
samba-4.8.3-4.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 errata-xmlrpc 2019-11-05 22:19:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3582