[Spacewalk-list] FW: Spacewalk-list Digest, Vol 21, Issue 19
Stefan Bluhm
stefanbluhm2 at alice-dsl.net
Mon Feb 8 14:47:14 UTC 2010
Hi Josh,
thank you for this indication. I didn't realise that the messages log is
being used. I assumed it is only for system start up messages.
This is what the logs state after a /usr/sbin/rhn-satellite stop (this
is when I got the error "Stopping
s2s: [FAILED]"):
Feb 8 14:35:23 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
connect
Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
error: XML parse error (not well-formed (invalid token))
Feb 8 14:35:25 spacewalk jabberd/router[12237]: [127.0.0.1, port=58524]
disconnect
Feb 8 14:35:39 spacewalk wrapper[12762]: TERM trapped. Shutting down.
Feb 8 14:35:39 spacewalk wrapper[12762]: <-- Wrapper Stopped
Feb 8 14:35:59 spacewalk jabberd/router[12237]: shutting down
Feb 8 14:35:59 spacewalk jabberd/router[12237]: [127.0.0.1, port=37300]
disconnect
Feb 8 14:35:59 spacewalk jabberd/router[12237]: [s2s] default route offline
Feb 8 14:35:59 spacewalk jabberd/router[12237]: [s2s] offline
Feb 8 14:35:59 spacewalk jabberd/s2s[12306]: connection to router closed
Feb 8 14:35:59 spacewalk jabberd/s2s[12306]: attempting reconnect (3 left)
Feb 8 14:36:01 spacewalk jabberd/s2s[12306]: attempting connection to
router at 127.0.0.1, port=5347
Feb 8 14:36:01 spacewalk jabberd/s2s[12306]: [6] [router] write error:
Connection refused (111)
Feb 8 14:36:01 spacewalk jabberd/s2s[12306]: connection to router closed
Feb 8 14:36:01 spacewalk jabberd/s2s[12306]: attempting reconnect (2 left)
Feb 8 14:36:03 spacewalk jabberd/s2s[12306]: attempting connection to
router at 127.0.0.1, port=5347
Feb 8 14:36:03 spacewalk jabberd/s2s[12306]: [6] [router] write error:
Connection refused (111)
Feb 8 14:36:03 spacewalk jabberd/s2s[12306]: connection to router closed
Feb 8 14:36:03 spacewalk jabberd/s2s[12306]: attempting reconnect (1 left)
Feb 8 14:36:05 spacewalk jabberd/s2s[12306]: attempting connection to
router at 127.0.0.1, port=5347
Feb 8 14:36:05 spacewalk jabberd/s2s[12306]: [6] [router] write error:
Connection refused (111)
Feb 8 14:36:05 spacewalk jabberd/s2s[12306]: connection to router closed
Feb 8 14:36:05 spacewalk jabberd/s2s[12306]: shutting down
Now heading straight for a /usr/sbin/rhn-satellite start:
Feb 8 14:38:40 spacewalk jabberd/router[14107]: starting up
Feb 8 14:38:40 spacewalk jabberd/router[14107]: process id is 14107,
written to /var/lib/jabberd/pid/router.pid
Feb 8 14:38:40 spacewalk jabberd/router[14107]: loaded user table (1 users)
Feb 8 14:38:40 spacewalk jabberd/router[14107]: loaded filters (0 rules)
Feb 8 14:38:40 spacewalk jabberd/router[14107]: [0.0.0.0, port=5347]
listening for incoming connections
Feb 8 14:38:40 spacewalk jabberd/sm[14130]: starting up
Feb 8 14:38:40 spacewalk jabberd/sm[14130]: id: spacewalk.bluhm-de.com
Feb 8 14:38:40 spacewalk jabberd/sm[14130]: process id is 14130,
written to /var/lib/jabberd/pid/sm.pid
Feb 8 14:38:40 spacewalk jabberd/sm[14130]: loading 'db' storage module
Feb 8 14:38:40 spacewalk jabberd/c2s[14153]: starting up
Feb 8 14:38:40 spacewalk jabberd/c2s[14153]: process id is 14153,
written to /var/lib/jabberd/pid/c2s.pid
Feb 8 14:38:40 spacewalk jabberd/c2s[14153]: modules search path:
/usr/lib/jabberd
Feb 8 14:38:40 spacewalk jabberd/c2s[14153]: loading 'db' authreg module
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: starting up (interval=3,
queue=60, keepalive=0, idle=86400)
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: process id is 14176,
written to /var/lib/jabberd/pid/s2s.pid
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: attempting connection to
router at 127.0.0.1, port=5347
Feb 8 14:38:40 spacewalk jabberd/router[14107]: [127.0.0.1, port=45920]
connect
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: connection to router
established
Feb 8 14:38:40 spacewalk jabberd/router[14107]: [127.0.0.1, port=45920]
authenticated as jabberd at jabberd-router
Feb 8 14:38:40 spacewalk jabberd/router[14107]: [s2s] set as default route
Feb 8 14:38:40 spacewalk jabberd/router[14107]: [s2s] online (bound to
127.0.0.1, port 45920)
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: [0.0.0.0, port=5269]
listening for connections
Feb 8 14:38:40 spacewalk jabberd/s2s[14176]: ready for connections
Feb 8 14:39:15 spacewalk wrapper[14636]: --> Wrapper Started as Daemon
Feb 8 14:39:15 spacewalk wrapper[14636]: Launching a JVM...
So I can't really see any indications of an error in the logs. Note that
I can now do a "telnet 127.0.0.1 5347" and connect successfully. So i am
not sure why the connection is refused on shut down. Do I need a FQDN or
should it all work on the 127.0.0.1 IP?
Now same thing for the log at /var/log/rhn/osa-dispatcher
Whilst stopping:
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', <X509Name object
'/C=DE/ST=Lower
Saxony/L=Hannover/O=ABC/OU=spacewalk.domain.com/CN=spacewalk.domain.com'>)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
rhnSQL/driver_cx_Oracle._execute_wrapper('Executing SQL: "select sysdate
as ID from dual" with bind params: {}',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib._get_jabber_client
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib._get_jabber_client('Connecting to', 'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.__init__
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.check_cert('Loading cert', <X509Name object
'/C=DE/ST=Lower
Saxony/L=Hannover/O=ABC/OU=spacewalk.domain.com/CN=spacewalk.domain.com'>)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.connect
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.connect('Attempting to connect',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('socket error',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.print_message('Could not connect to jabber server',
'spacewalk.domain.com')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('ERROR', 'Traceback (most recent call
last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in
setup_connection\n c = self._get_jabber_client(js)\n File
"/usr/share/rhn/osad/jabber_lib.py", line 311, in
_get_jabber_client\n c.connect()\n File
"/usr/share/rhn/osad/jabber_lib.py", line 577, in connect\n
jabber.Client.connect(self)\n File
"/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 464, in
connect\n else: self._sock.connect((self._hostIP, self._port))\n
File "<string>", line 1, in connect\nerror: [Errno 111] Connection
refused\n')
2010/02/08 14:35:25 +02:00 12317 0.0.0.0:
osad/jabber_lib.setup_connection('Could not connect to any jabber server',)
2010/02/08 14:35:25 +02:00 12317 0.0.0.0: osad/jabber_lib.main('Unable
to connect to jabber servers, sleeping 10 seconds',)
This one is repeating a couple of times. After restart it also shows the
same scenario.
Are there any other logs to check?
On 08.02.2010 14:01, not applicable wrote:
>
>
> -------------------------------------------
> *From:* spacewalk-list-bounces at redhat.com on behalf of
> spacewalk-list-request at redhat.com[SMTP:SPACEWALK-LIST-REQUEST at REDHAT.COM]
> *Sent:* Monday, February 08, 2010 2:01:48 PM
> *To:* spacewalk-list at redhat.com
> *Subject:* Spacewalk-list Digest, Vol 21, Issue 19
> *Auto forwarded by a Rule*
>
> Send Spacewalk-list mailing list submissions to
> spacewalk-list at redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> or, via email, send a message with subject or body 'help' to
> spacewalk-list-request at redhat.com
>
> You can reach the person managing the list at
> spacewalk-list-owner at redhat.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Spacewalk-list digest..."
>
>
> Today's Topics:
>
> 1. osa-dispatcher problems. no system ever reports (Stefan Bluhm)
> 2. Re: osa-dispatcher problems. no system ever reports (Joshua Roys)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 08 Feb 2010 13:13:51 +0100
> From: Stefan Bluhm <stefanbluhm2 at alice-dsl.net>
> To: spacewalk-list at redhat.com
> Subject: [Spacewalk-list] osa-dispatcher problems. no system ever
> reports
> Message-ID: <4B6FFFFF.5060300 at alice-dsl.net>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Hello,
>
> I am running the following setup:
>
> Clean VMWARE Fedora 12 32bit
>
> Spacewalk nightly built (updated just now)
>
> My clients never seem to check in (although they register fine) or
> execute any of the activities.
>
> When I run /usr/sbin/rhn-satellite restart
>
> I get the following message on the stop processes:
>
> Stopping s2s: [FAILED]
>
> And these two messages on the start process.
>
> Starting osa-dispatcher:
> /usr/lib/python2.6/site-packages/jabber/jabber.py:68:
> DeprecationWarning: the sha module is deprecated; use the hashlib module
> instead
>
> import sha, time
>
> RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
> last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in
> setup_connection\n c = self._get_jabber_client(js)\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 311, in
> _get_jabber_client\n c.connect()\n File
> "/usr/share/rhn/osad/jabber_lib.py", line 577, in connect\n
> jabber.Client.connect(self)\n File
> "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 464, in
> connect\n else: self._sock.connect((self._hostIP, self._port))\n
> File "<string>", line 1, in connect\nerror: [Errno 111] Connection
> refused\n',)
>
> So I guess some socket or so could not be opened. Does anyone have any
> advise on what to do?
>
> Thanks and best wishes,
>
> Stefan
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://www.redhat.com/archives/spacewalk-list/attachments/20100208/14c646eb/attachment.html>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 8 Feb 2010 08:01:24 -0500
> From: Joshua Roys <joshua.roys at gtri.gatech.edu>
> To: <spacewalk-list at redhat.com>
> Subject: Re: [Spacewalk-list] osa-dispatcher problems. no system ever
> reports
> Message-ID: <4B700B24.1090507 at gtri.gatech.edu>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> On 02/08/2010 07:13 AM, Stefan Bluhm wrote:
> > Stopping s2s: [FAILED]
> >
>
> This means it wasn't running, which is bad - see below.
>
> > RHN 7447 2010/02/08 12:00:55 +02:00: ('Traceback (most recent call
> > last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 254, in
> > setup_connection\n c = self._get_jabber_client(js)\n File
> > "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client\n
> > c.connect()\n File "/usr/share/rhn/osad/jabber_lib.py", line 577, in
> > connect\n jabber.Client.connect(self)\n File
> > "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 464, in
> > connect\n else: self._sock.connect((self._hostIP, self._port))\n File
> > "<string>", line 1, in connect\nerror: [Errno 111] Connection
> refused\n',)
> >
>
> That "Connection refused" was caused by the first issue - so let's debug
> jabberd. Do you have any logs in /var/log/messages (or wherever you've
> configured jabberd logs to go)?
>
> Josh
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 2719 bytes
> Desc: S/MIME Cryptographic Signature
> URL:
> <https://www.redhat.com/archives/spacewalk-list/attachments/20100208/d67e4e84/attachment.bin>
>
>
> ------------------------------
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> End of Spacewalk-list Digest, Vol 21, Issue 19
> **********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20100208/f165d50f/attachment.htm>
More information about the Spacewalk-list
mailing list