Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1204157[details]
workaround patch
Description of problem:
Computer with high count of CPU with low usage will have a huge idle time which can be read from /proc/uptime. The problem is not with the high number itself but with the xml rpclib Marshaller which is not able to send long instead of int when it is necessary thus the rhn_check fails on <type 'exceptions.OverflowError'> error.
Version-Release number of selected component (if applicable):
rhn-check-2.0.2-6.el7.noarch
How reproducible:
Have a PC with 240 CPU and let it sit for 160 days, or just simply fake second value in /proc/uptime
Actual results:
rhn_check will fail to report the values.
Expected results:
data will be reported
Workaround:
The attached patch set the idle time to 0 to workaround the issue with too high number.
When system runs more then 68 years, the rhn_check start failing with following error:
<type 'exceptions.OverflowError'>
Více informací naleznete ve /var/log/up2date
<type 'exceptions.OverflowError'>
Více informací naleznete ve /var/log/up2date
[root@kvm-02-guest05 ~]# tail /var/log/up2date
File "/usr/lib64/python2.7/xmlrpclib.py", line 655, in __dump
f(self, value, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 715, in dump_array
dump(v, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 655, in __dump
f(self, value, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 666, in dump_int
raise OverflowError, "int exceeds XML-RPC limits"
<type 'exceptions.OverflowError'>: int exceeds XML-RPC limits
>> cat /proc/uptime
2148000000.83 214800000.83
>> cat /proc/uptime
882642.20 3306190.66
first number - the total number of seconds the system has been up
second number - how much of that time the machine has spent idle, in seconds
when second number is more than 2147483000.00, the rhn_check doesn't work and I receive traceback:
>> rhn_check -vv
An error has occurred:
<type 'exceptions.OverflowError'>
See /var/log/up2date for more information
>> /var/log/up2date
<type 'exceptions.OverflowError'>
See /var/log/up2date for more information
[root@kvm-02-guest05 ~]# tail /var/log/up2date
File "/usr/lib64/python2.7/xmlrpclib.py", line 655, in __dump
f(self, value, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 715, in dump_array
dump(v, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 655, in __dump
f(self, value, write)
File "/usr/lib64/python2.7/xmlrpclib.py", line 666, in dump_int
raise OverflowError, "int exceeds XML-RPC limits"
<type 'exceptions.OverflowError'>: int exceeds XML-RPC limits
Comment 11Gennadii Altukhov
2017-06-28 13:22:52 UTC
the bug is fixed in upstream. spacewalk.git master: b258e06ea3329b6782fdd21db77939380b3a85ca
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/RHBA-2017:2039
Created attachment 1204157 [details] workaround patch Description of problem: Computer with high count of CPU with low usage will have a huge idle time which can be read from /proc/uptime. The problem is not with the high number itself but with the xml rpclib Marshaller which is not able to send long instead of int when it is necessary thus the rhn_check fails on <type 'exceptions.OverflowError'> error. Version-Release number of selected component (if applicable): rhn-check-2.0.2-6.el7.noarch How reproducible: Have a PC with 240 CPU and let it sit for 160 days, or just simply fake second value in /proc/uptime Actual results: rhn_check will fail to report the values. Expected results: data will be reported Workaround: The attached patch set the idle time to 0 to workaround the issue with too high number.