RE: RHN Registration Errors

"Lamar Milligan" <[email protected]>
Newsgroups gmane.linux.redhat.rhn.user
Message-ID <[email protected]>

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of inode0
> Sent: Tuesday, June 10, 2008 10:55 AM
> To: Discussions about Red Hat Network (rhn.redhat.com)
> Subject: Re: [rhn-users] RHN Registration Errors
>
>
> On Tue, Jun 10, 2008 at 9:00 AM, Lamar Milligan
> <[email protected]> wrote:
> > I have read previous threads concerning yum errors and RHN
> problems.  I am
> > trying to register a RHEL 3 (redhat-release 3ES-13.9.5) system
> and a RHEL
> > 5.2 system.  When I try to register the systems with RHN, the
> process errors
> > at 60% complete.  The profile is created, but the hardware and
> package lists
> > are both empty.    Any pointers?
>
> Did the systems both get registered but have missing information on RHN?

Yes.  Both hardware and software profiles are empty.

>
> If so, with the RHEL3 box you can try running
>
> # up2date -p

I started the up2date -p command several minutes ago, and it has not
completed yet, but neither has it thrown an error (a good sign).

> # up2date --hardware
>
> and on the RHEL5 box
>
> # rhn-profile-sync
>

I ran rhn-profile-sync on the RHEL 5.2 box, and received the following
error:

[root@host1 ~]# rhn-profile-sync
Updating package profile...
An error has occurred:
Connection timed out on write
See /var/log/up2date for more information

[root@host1]# tail -100 /var/log/up2date
<snip>
[Tue Jun 10 12:55:04 2008] up2date updateLoginInfo() login info
[Tue Jun 10 12:55:04 2008] up2date logging into up2date server
[Tue Jun 10 12:55:06 2008] up2date successfully retrieved authentication
token from up2date server
[Tue Jun 10 12:55:06 2008] up2date Updating package profile
[Tue Jun 10 12:55:56 2008] up2date A socket error occurred: Timeout
Exception, attempt #1
[Tue Jun 10 12:56:52 2008] up2date A socket error occurred: Timeout
Exception, attempt #2
[Tue Jun 10 12:57:33 2008] up2date A socket error occurred: Timeout
Exception, attempt #3
[Tue Jun 10 12:58:34 2008] up2date A socket error occurred: Timeout
Exception, attempt #4
[Tue Jun 10 12:59:29 2008] up2date A socket error occurred: Timeout
Exception, attempt #5
[Tue Jun 10 12:59:29 2008] up2date Error communicating with server. The
message was:
Connection timed out on write
[Tue Jun 10 12:59:29 2008] up2date
Traceback (most recent call last):
  File "/usr/sbin/rhn-profile-sync", line 54, in ?
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhn-profile-sync", line 42, in main
    rhnPackageInfo.updatePackageProfile()
  File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 27, in
updatePackageProfile
    rpmUtils.getInstalledPackageList(getArch=1))
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 50, in __call__
    return rpcServer.doCall(method, *args, **kwargs)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 206, in doCall
    raise up2dateErrors.CommunicationError(e.args[0])
up2date_client.up2dateErrors.CommunicationError: Error communicating with
server. The message was:
Connection timed out on write

> to update the package profiles and hardware lists on RHN.
>
> John
>
> _______________________________________________
> rhn-users mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhn-users
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.