[Spacewalk-list] osa-dispatcher not running or not connecting

[Michiel van Es]

FIXED IT!

changed the max open files from 1024 to 2024 in the .xml files and moved 
/var/lib/jabberd/db to /var/lib/jabberd/old-jammer && mkdir 
/var/lib/jabberd/db && chown jabber:jabber /var/lib/jabberd/db && chmod 
777 /var/lib/jabberd/db
and restarted jabberd and now I see all connection established :)

Works like a charm! :D

Michiel van Es wrote:
> 
> Joshua Roys wrote:
>> On 10/29/2009 11:43 AM, Michiel van Es wrote:
>>>> Is it possible to reconfigure the jabber service and start clean?
>>>> The SYN_RECV packages are not ok..
>>>> The strange thing is that I can not even make a normal jabber connection
>>>> from a client (say pidgin) so I suspect my jabber settings are garbled..
>>>> Is it possible if I post some of my configuration here so people can
>>>> look at it?
>> I don't think it's a jabberd issue ... I feel like this is a general 
>> networking issue.  I don't think the application would even see a socket 
>> in that SYN_RECV state.  Here's a test:
>> $ strace nc -l 12345
>> # tcpdump -vnni lo port 12345 &
>> # nmap -v -sS -p 12345 localhost
>>
>> nc doesn't see anything...  and the tcpdump shows the kernel sees and 
>> replies to the SYN nmap sends:
>>
>> 16:27:56.880966 IP (tos 0x0, ttl 38, id 64160, offset 0, flags [none], 
>> proto TCP (6), length 44) 127.0.0.1.42004 > 127.0.0.1.12345: S, cksum 
>> 0xf26f (correct), 1382315266:1382315266(0) win 3072 <mss 1460>
>> 16:27:56.881000 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 
>> TCP (6), length 44) 127.0.0.1.12345 > 127.0.0.1.42004: S, cksum 0x0791 
>> (correct), 1846857288:1846857288(0) ack 1382315267 win 32792 <mss 16396>
>>
>> (then nmap kills the fake connection with a RST...)
>>
>> So I feel like you should examine the network setup...
> 
> Is it possible jabber tries to do an ldap lookup?
> 
> I am trying to install webmin on the same machine and I get this crap in 
> /var/log/messages:
> 
> Oct 30 13:57:41 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:57:44 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:57:44 devmx01 perl: nss_ldap: reconnecting to LDAP server 
> (sleeping 4 seconds)...
> Oct 30 13:57:51 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:57:51 devmx01 perl: nss_ldap: reconnecting to LDAP server 
> (sleeping 8 seconds)...
> Oct 30 13:58:02 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:58:02 devmx01 perl: nss_ldap: reconnecting to LDAP server 
> (sleeping 16 seconds)...
> Oct 30 13:58:21 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:58:21 devmx01 perl: nss_ldap: reconnecting to LDAP server 
> (sleeping 32 seconds)...
> Oct 30 13:58:56 devmx01 perl: nss_ldap: failed to bind to LDAP server 
> ldap://10.101.0.95: Can't contact LDAP server
> Oct 30 13:58:56 devmx01 perl: nss_ldap: reconnecting to LDAP server
> 
> My /etc/pam.d/jabberd:
> 
> #%PAM-1.0
> auth       required     pam_nologin.so
> auth       include      system-auth
> account    include      system-auth
> session    include      system-auth
> 
> This also stopped my ssh account from loging in..
> 
>>> Another question:
>>> Is it possbile to set the rhnsd on 5 minutes instead of 4 hours?
>>> In case of a failing jabber server, the clients will pull the requests
>>> every 5 minutes?
>>>
>>> Can this do any harm?
>>>
>> That should work - we do something like that here, although we set it to 
>> 30 minutes (I think).  Edit /etc/sysconfig/rhn/rhnsd - the INTERVAL is 
>> in minutes.  Also note that rhnsd varies the time a little every 12 
>> intervals to prevent massive concurrent checkins.
>>
>> Hope to help,
>>
> Michiel
> 
>> Josh
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list