[Spacewalk-list] spacewalk-proxy and osad

[Florian CROUZAT]

I do indeed have the same issue(s).
No network traffic of any kind on the TCP/5269 port on the spacewalk-server.
No scheduled actions are picked up, it just doesn't work. They only are
executed when rhnsd is fired up (from a cron IIRC).
Also, when I run osad manually (sudo /usr/bin/python /usr/sbin/osad -N
-vvvv) on a client behind the proxy, here's what I get after a while:

2011-06-03 17:31:18 jabber_lib.process: None
2011-06-03 17:31:27 jabber_lib.process: None
Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
    self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
    self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 242, in process_once
    client.process(timeout=None)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1038, in process
    raise SSLError("OpenSSL error; will retry", str(e))
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2011-06-03 17:31:27 jabber_lib.main: Sleeping 67 seconds

Maybe I'm not supposed to run osad manually or maybe it means a firewall or
a sysctl config closed a ESTABLISHED but inactive socket, I've no clues :/
Anyway, after this "crash" osad reconnects, redo the ssl handshake, etc.

----
Florian



> -----Original Message-----
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-
> bounces at redhat.com] On Behalf Of Wojtak, Greg
> Sent: Friday, June 03, 2011 3:09 PM
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] spacewalk-proxy and osad
>
> I have the same issue as well.  Running rhn_check on the hosts behind the
> proxy will work.  It just seems that osad is not able to communicate
> properly.  I'm running 1.2 server and 1.3 clients/proxy still, so I was
> hoping that was part of the problem.  I'm going to be starting upgrading
> to 1.4, but it seems like you're already there so now my hopes are dashed.
>
> Either way, I've not found a way to get this to work and no errors are
> being logged anywhere which is not helpful.
>
> On 2011-06-03 8:54 AM, "Baptiste AGASSE"
> <baptiste.agasse at lyra-network.com> wrote:
>
> >Hi all,
> >
> >We have some problems with osad and spacewalk proxy.
> >All boxes behind the proxy are seen as offline in osad status on
> >spacewalk server, and no action assigned to these machines are picked up.
> >Also, I can see in  "details => connection" section of host behind proxy,
> >i can see spacewalk proxy host listed.
> >
> >We can see boxes connected on spacewalk proxy (on port 5222), the proxy
> >is connected on spacewalk server (on port 5222), but we don't see any
> >trafic on 5269 port from spacewalk-proxy to spacewalk server.
> >
> >we have iptables firewal between the spacewalk server and proxy and we
> >opened 80,443,5222,5269 ports from proxy to spacewalk server.
> >
> >spacewalk server:
> >CentOS 5.6
> >spacewalk 1.4
> >SElinux : Permissive
> >
> >spacewalk proxy:
> >CentOS 5.6
> >spacewalk proxy installed from spacewalk 1.4 repo
> >SELinux: Enforcing, with spacewalk-proxy-selinux installed
> >
> >someone have the same problem ?
> >
> >Regards
> >
> >Baptiste AGASSE
> >
> >_______________________________________________
> >Spacewalk-list mailing list
> >Spacewalk-list at redhat.com
> >https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list