[Spacewalk-list] up2date A protocol error occurred: Internal Server Error
Daryl Rose
darylrose at outlook.com
Thu Jul 6 17:56:52 UTC 2017
The magic of posting online resolved the error. As soon as posted my last reply, I was able to get it working.
I think the final issue was the FQDN in /etc/hostname. I had added the FQDN previously, but I kept rolling back the snapshot while working out other issues. Once I got everything configured correctly and the certificate working correctly I stopped rolling back and forgot that I needed to update the hostname. Once I did that, and rebooted, the clients are able to see the repositories and get patches/packages.
Thank you for the replies.
Daryl
________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Daryl Rose <darylrose at outlook.com>
Sent: Thursday, July 6, 2017 12:42 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error
I disabled selinux previously, so I don't think that is the issue.
Where did you see the HttpProtocolOptions Unsafe error?
Thank you
Daryl
________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Coffman, Anthony J <Tony.Coffman at snapon.com>
Sent: Thursday, July 6, 2017 11:50 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error
I ran into something similar with a newly deployed CentOS 7 / Spacewalk Proxy 2.5 today.
Selinux was denying access to several things. I guess this may not be fixed in Proxy 2.6?
Check the audit.log and see if you may be running into the same thing.
Anyway – this may save you some time, right after I resolved the SELINUX issues on the proxy, I ran into the HttpProtocolOptions Unsafe issue that had been previously reported. The symptom for that was a 400 error when a client requested updates. The fix/workaround has been posted on the list previously.
--Tony
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Daryl Rose
Sent: Thursday, July 6, 2017 12:26 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] up2date A protocol error occurred: Internal Server Error
I recently rebuilt my proxy server to v2.6. I'm able to get clients to register, but I can't patch or install packages via the proxy server. I use a signed certificate and I believe that everything with the certificate is working correctly. However, I get the following errors:
Registration error:
There was an error communicating with RHN.
Red Hat Satellite or RHN Classic support will be disabled.
rhn-plugin: Error communicating with server. The message was:
Internal Server Error
>From /var/log/up2date:
[Thu Jul 6 16:23:14 2017] up2date A protocol error occurred: Internal Server Error , attempt #1,
I'm not sure whats the issue. Did I miss something on the proxy server?
Thanks
Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20170706/c0a590c4/attachment.htm>
More information about the Spacewalk-list
mailing list