On Wed, Aug 13, 2003 at 02:37:12PM -0400, Sean Estabrooks wrote:
> > One problem i had was caused by an old systemid file from
the 7.3 era.
> > No matter what i typed i got the error shown below. It would be nice
> > if rhn_register had a --force option or even better ask if it should
> > ignore or use the the current systemid file.
> `up2date --register` or `rhn_register --register` will
> "force" a reregister.
Isn't rhn_register --register a bit redundant? ;o)
It is. But rhn_register is just a symlink to up2date these
Anyway after restoring the _old_ systemid file the problem still
Hmm, indeed. Looks like the refactor may have broken forced
reregistering. I'll take a look and see what I can figure out.
# up2date --register
Traceback (most recent call last):
File "/usr/sbin/up2date", line 25, in ?
from up2date_client import repoDirector
File "repoDirector.py", line 12, in ?
File "rhnChannel.py", line 128, in getChannels
File "up2dateAuth.py", line 150, in getLoginInfo
File "up2dateAuth.py", line 104, in login
File "up2dateAuth.py", line 60, in maybeUpdateVersion
up2date_client.up2dateErrors.CommunicationError: Error communicating with server. The