Bug 60370 - reserveUser error, just started happening for no apparent reason
reserveUser error, just started happening for no apparent reason
Status: CLOSED NOTABUG
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration (Show other bugs)
unspecified
All Linux
medium Severity high
: ---
: ---
Assigned To: Cristian Gafton
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-02-26 16:26 EST by Isaiah Weiner
Modified: 2015-01-07 18:55 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-02-26 17:23:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Isaiah Weiner 2002-02-26 16:26:09 EST
Description of problem:
Until the last day or so registration of machines was working fine.  Tonight at 
6PM Pacific we are registering a batch of many hundred machines.  This error we 
see MUST be resolved before then, that's roughly 4 hours away.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. execute registration command
2. wait

Actual Results:  A protocol error occured: Forbidden , attempt #1
A protocol error occured: Forbidden , attempt #2
A protocol error occured: Forbidden , attempt #3
A protocol error occured: Forbidden , attempt #4
A protocol error occured: Forbidden , attempt #5
Traceback (innermost last):
  File "/usr/sbin/rhnreg_ks", line 230, in ?
    main()
  File "/usr/sbin/rhnreg_ks", line 194, in main
    ret = rhnreg.reserveUser(username, password)
  File "/usr/share/rhn/register/rhnreg.py", line 440, in reserveUser
    ret = doCall(s.registration.reserve_user, username, password)
  File "/usr/share/rhn/register/rhnreg.py", line 168, in doCall
    raise CommunicationError(e.errmsg)
rhnreg.CommunicationError: Error communicating with server.  The message was:
Forbidden
RHN registration command returned non-zero result: 1.

Expected Results:  The command line should have been returned without error and 
the machine registered.

Additional info:

The registration command is:
/usr/sbin/rhnreg_ks --profilename="$MACHINEID" \
--username="cisco_ecs_${MACHINEID}_$USERNAME" \
--password="cisco_ecs_$USERNAME" --orgid="377569" \
--orgpassword="<password>" --email="rhn-notify@cisco.com" \
--force

The client version is: rhn_register-2.7.2-7.x.8
Comment 1 Mihai Ibanescu 2002-02-26 16:48:12 EST
Can you please attach the contents of /var/log/httpd/error.log and access.log,
on the proxy box?
Comment 2 Isaiah Weiner 2002-02-26 16:50:51 EST
InfoSec was active; the communications between it and the outside world have 
halted.  Which explains it, and why nothing appeared to change; please give me 
a list of addresses or CIDR notation for what the proxy server needs to talk to.
Comment 3 Isaiah Weiner 2002-02-26 17:23:46 EST
Address information fixed it, thanks guys!

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