Bug 32221 - rhn_register fails with large swap space
Summary: rhn_register fails with large swap space
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhn_register
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-19 12:45 UTC by Phil Venton
Modified: 2015-01-07 23:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-04-03 15:48:46 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2001:048 0 normal SHIPPED_LIVE New Update Agent with many fixes and enhanced functionality available 2001-04-12 04:00:00 UTC

Description Phil Venton 2001-03-19 12:45:56 UTC
From a customer service request:

System running enterprise kernel with two 1.9 gig swap partitions,
rhn_register quits with the following:

----- [snip]

Traceback (innermost last):
 File "/usr/lib/python1.5/site-packages/libglade.py", line28, in __call__
  ret = apply(self.func, a)
 File "/usr/share/rhn/register/gui.py", line 448, in \
                    onProfilePagePrepare hardware.read_memory()
 File "/usr/share/rhn/register/hardware.py", line 172, in read_memory
  megs = string.atoi(memlist[1])/(1024*1024)
ValueError: atoi() literal too large: 4038557696

----- [snip]

The atoi literal there is the total ram+swap in bytes.  Seems this much ram
pushes it outside atoi's legal range.

Turning off one of the swap partitions solves the problem, but given that
the swap limit on the enterprise kernel is 8x2 gigs (if I remember
correctly!), we might want to look at this.

Comment 1 Adrian Likins 2001-03-19 19:07:28 UTC
replaced the atoi with a atol, and cast approriately. Should work
up to about 300TB of swap now. Fixed in CVS.

Comment 2 Preston Brown 2001-04-12 20:53:46 UTC
fixed in errata, due out today.


Note You need to log in before you can comment on or make changes to this bug.