pymsnt fails to connect after upgrade to Debian Lenny
Jamin W. Collins
updated my server. The distribution update was the only change made.
The system had previously been running pymsnt v0.11.2 without any major
issue. However, now with 0.11.3 I get the following error message back
when trying to connect:
Failed to connect to MSN servers: [Failure instance: Traceback (failure
with no frames): <type 'exceptions.Exception'>: Timeout
]
Searching seems to indicate some problem with packet fragmenting or
normalizing with routers, but I've made no change of any kind to my
router between this working and not, only the server update from Etch to
Lenny.
Any other ideas or help in tracking this down and resolving it? I tried
rolling back to the 0.11.2 package, but it seems there have been a
number of changes in Twisted from the pid check to the daemonize routines.
--
Jamin W. Collins
Jamie Thompson
wrote:
problem have been happening for a few months now. I just assumed it
was just transient problems due to changes on MS's end.
It would be wonderful if it were a bug, as that would of course mean
there's a chance of it being rectified and my users could then stop
moaning about how rubbish jabber is because it keeps "crashing" and
logging them out.
Jamie Thompson
a day at least it loses it's connection to the MSN servers. In one
particularly bad spell recently, it disconnected every few minutes for
a hours or so.
Matthew W. S. Bell
> With the recent release of Debian's latest stable version (Lenny), I
> updated my server. The distribution update was the only change made.
> The system had previously been running pymsnt v0.11.2 without any major
> issue. However, now with 0.11.3 I get the following error message back
> when trying to connect:
>
> Failed to connect to MSN servers: [Failure instance: Traceback (failure
> with no frames): <type 'exceptions.Exception'>: Timeout
> ]
I had an issue that manifested like this. The problem was that the
server IP was set to 127.0.0.1 to which pyMSNt dutifully bound its
sockets, then any connect() to a non-local address failed with EINVAL.
Setting a valid IP address makes everything work. It is unfortunate that
pyMSNt or twisted do not report this error.
Matthew W. S. Bell
Jamin W. Collins
>
> I had an issue that manifested like this. The problem was that the
> server IP was set to 127.0.0.1 to which pyMSNt dutifully bound its
> sockets, then any connect() to a non-local address failed with EINVAL.
> Setting a valid IP address makes everything work. It is unfortunate that
> pyMSNt or twisted do not report this error.
Which server or setting are you referring to? The transport server or
the Jabber server? I run the transports on the same system as the
jabber server and have always had them connect with each other over the
loopback interface and the localhost IP.
--
Jamin W. Collins
Norman Rasmussen
<jcol...@asgardsrealm.net> wrote:
> Which server or setting are you referring to? The transport server or
> the Jabber server? I run the transports on the same system as the
> jabber server and have always had them connect with each other over the
> loopback interface and the localhost IP.
<!-- The public IP or DNS name of the machine the transport is running on -->
<!-- This is needed for file transfer!! This is also used as the IP
address for outgoing connections -->
<host>0.0.0.0</host>
make sure that the value is _NOT_ 127.0.0.1. If you want file
transfer to work, it must be a valid IP address or dns name, otherwise
0.0.0.0 should work fine for standard outgoing connections.
--
- Norman Rasmussen
- Email: nor...@rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
Jamin W. Collins
>
> <!-- The public IP or DNS name of the machine the transport is running on -->
> <!-- This is needed for file transfer!! This is also used as the IP
> address for outgoing connections -->
> <host>0.0.0.0</host>
>
> make sure that the value is _NOT_ 127.0.0.1. If you want file
> transfer to work, it must be a valid IP address or dns name, otherwise
> 0.0.0.0 should work fine for standard outgoing connections.
Right now actual connectivity with the MSN network is more of a priority
than file transfers. Since the upgrade to Lenny and 0.11.3 I haven't
been able to make a single successful MSN connection.
--
Jamin W. Collins
Norman Rasmussen
<jcol...@asgardsrealm.net> wrote:
> Right now actual connectivity with the MSN network is more of a priority
> than file transfers. Since the upgrade to Lenny and 0.11.3 I haven't
> been able to make a single successful MSN connection.
You didn't post the value of your config host, so I can't guess what
might be wrong.
Jamin W. Collins
>
> You didn't post the value of your config host, so I can't guess what
> might be wrong.
Seems it was the file transfer setting, I had it set to 127.0.0.1 as I
was not worried about the file transfers. It is very strange that this
worked fine under 0.11.2 (same exact config file).
--
Jamin W. Collins
Norman Rasmussen
<jcol...@asgardsrealm.net> wrote:
> Seems it was the file transfer setting, I had it set to 127.0.0.1 as I
> was not worried about the file transfers. It is very strange that this
> worked fine under 0.11.2 (same exact config file).
The host config option is now being used as the outgoing address for
connections. This is to help out people on server with multiple IP
addresses. (This change was made in dev about 18 months ago by James,
but I only updated the default config value to 0.0.0.0 about 4 months
ago).
I'm not sure at what time 0.11.3 was released, but it would miss my
config changes.