Good to hear that you have it working.  I will contact you off list to get more 
information so this can be reviewed as a bug.

Mike

>>> On 7/13/2010 at 09:13 AM, in message
<d7457cbb6214164aa8715a5f0e19d8102d99602...@msgcmsv21023.ent.wfb.bank.corp>,
Marcy Cortes <[email protected]> wrote: 
> Well, appears there's some sort of bug with proxy there.
> 
> 
> It ignored the NO_PROXY line in /etc/sysconfig/proxy and it ignored the 
> --no-proxy argument.
> Changing PROXY_ENABLED='no' in /etc/sysconfig/proxy allowed it to register.
> 
> 
> 
> Marcy 
> 
> "This message may contain confidential and/or privileged information. If you 
> are not the addressee or authorized to receive this for the addressee, you 
> must not use, copy, disclose, or take any action based on this message or any 
> information herein. If you have received this message in error, please advise 
> the sender immediately by reply e-mail and delete this message. Thank you for 
> your cooperation."
> 
> 
> -----Original Message-----
> From: Cortes, Marcy D. 
> Sent: Tuesday, July 13, 2010 7:45 AM
> To: 'Linux on 390 Port'
> Subject: RE: [LINUX-390] SMT client can't suse_register
> 
> No registrations have worked... New setup here
> 
> Not sure where squid is.  I don't its on the client or the server.  I ran it 
> with the --no-proxy in case it was hitting a proxy server
> 
> /usr/bin/suse_register -i -L /root/.suse_register.log --no-proxy
> And it still failed with the same error.
> 
> 
> 2010-07-13 07:40:58 SUSE::SRPrivate - [info]  SEND DATA to URI: 
> https://pippin.wellsfargo.com/center/regsvc?command=listproducts&lang=en-US&vers
> ion=1.0:
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  ERROR: HTTP/1.0 503 Service 
> Unavailable
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  Server: squid/2.6.STABLE17
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  Date: Tue, 13 Jul 2010 
> 14:42:28 
> GMT
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  Content-Type: text/html
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  Content-Length: 1130
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  Expires: Tue, 13 Jul 2010 
> 14:42:28 GMT
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  X-Squid-Error: 
> ERR_CONNECT_FAIL 
> 110
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  (2)
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  ERROR: Failure when receiving 
> data from the peer: (56)
> 2010-07-13 07:42:28 SUSE::SRPrivate - [error]  (2)
> 
> Is what ends up in the .suse_register log.
> 
>  
> I can hit that URL with my pc browse and it works.
> 
> 
> Marcy Cortes 
> Operating Systems Engineer, zVM and Linux on z
> Enterprise Hosting Services, Mainframe/Midrange Services
> MAC A0187-050
> 201 3rd St. 
> San Francisco, CA 94103
> w. (415) 477-6343
> c. (415) 517-0895 
> [email protected]
> "This message may contain confidential and/or privileged information. If you 
> are not the addressee or authorized to receive this for the addressee, you 
> must not use, copy, disclose, or take any action based on this message or any 
> information herein. If you have received this message in error, please advise 
> the sender immediately by reply e-mail and delete this message. Thank you for 
> your cooperation."
> 
> 
> -----Original Message-----
> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mike 
> Friesenegger
> Sent: Tuesday, July 13, 2010 7:37 AM
> To: [email protected]
> Subject: Re: [LINUX-390] SMT client can't suse_register
> 
> Hello Marcy,
> 
> Has registration worked in the past with this SMT server from another 
> server?  Can you try a registration from another server?
> 
> It looks like you are getting a certificate from the SMT server.  Where is 
> squid running?
> 
> I would also look at the /root/.suse_register.log to see if there is any 
> additional messages that may provide a hint.
> 
> Look at the /etc/suseRegister.conf to confirm that the server that you would 
> like to register is pointing to the correct SMT server.  If the 
> suseRegister.conf is pointed correctly then you will be able to rerun 
> suse_register without having to use clientSetup4SMT.sh.
> 
> Regards,
> 
> Mike
> 
>>>> On 7/13/2010 at 08:09 AM, in message
> <d7457cbb6214164aa8715a5f0e19d8102d99602...@msgcmsv21023.ent.wfb.bank.corp>,
> Marcy Cortes <[email protected]> wrote: 
>> I have set up a SMT SLES 11 server and it seems to work, mirrors things from 
> 
>> Novell just fine.
>> 
>> However, I can't get any client to work.
>> The clientSetup4SMT.sh command results in 
>> 
>> <snip>
>> Do you accept this certificate? [y/n] y
>> Client setup finished.
>> Start the registration now? [y/n] y
>> /usr/bin/suse_register -i -L /root/.suse_register.log
>> All services have been refreshed.
>> Repository 'SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152' is up to date.
>> All repositories have been refreshed.
>> ERROR: HTTP/1.0 503 Service Unavailable
>> Server: squid/2.6.STABLE17
>> Date: Tue, 13 Jul 2010 14:06:19 GMT
>> Content-Type: text/html
>> Content-Length: 1130
>> Expires: Tue, 13 Jul 2010 14:06:19 GMT
>> X-Squid-Error: ERR_CONNECT_FAIL 110
>> 
>> 
>> (2)
>> ERROR: Failure when receiving data from the peer: (56)
>> (2)
>> ERROR: Failure when receiving data from the peer: (56)
>> 
>> 
>> 
>> Any ideas?
>> All SMT updates have been applied to the SMT server.
>> 
>> Marcy 
>> 
>> 
>> "This message may contain confidential and/or privileged information. If you 
> 
>> are not the addressee or authorized to receive this for the addressee, you 
>> must not use, copy, disclose, or take any action based on this message or 
> any 
>> information herein. If you have received this message in error, please 
> advise 
>> the sender immediately by reply e-mail and delete this message. Thank you 
>> for 
> 
>> your cooperation."
>> 
>> ----------------------------------------------------------------------
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO LINUX-390 or 
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> ----------------------------------------------------------------------
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or 
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or 
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to