Transports killing connection when Connecting from a Second Location

Hi there!

I might have found a bug that can be triggered when connecting from a second location using the same account. The transports were sending the following error messages:

(20.02.2007 22:06:35) ICQ Transport:

Internal server error.

The server could not process the stanza because of a misconfiguration or

an otherwise-undefined internal server error.

(20.02.2007 22:06:57) ICQ Transport:

Service unavailable.

The server or recipient does not currently provide the requested

service.

(21.02.2007 17:15:27) MSN Transport:

Undefined condition.

The error condition is not one of those defined by the other conditions

in this list.

(21.02.2007 17:15:36) MSN Transport:

Service unavailable.

The server or recipient does not currently provide the requested

service.

This error occured first after I’'ve upgraded my server to Wildfire 3.2.2. Any ideas?

Best regards

Sven

blink I’'m not even sure where those errors are coming from!

Sounds good! :stuck_out_tongue:

Is there any information (logfiles, etc.) I could give you that would help you solve the issue?

Btw: Since I’'ve upgraded to Wildfire 3.2.2, my own server and the active transports (icq.hostname.tld, etc) are displayed under “Server Sessions” in the webadmin. Is that normal?

Message was edited by: ScP

ScP wrote:

Btw: Since I’'ve upgraded to Wildfire 3.2.2, my own server and the active transports (icq.hostname.tld, etc) are displayed under “Server Sessions” in the webadmin. Is that normal?

I don’‘t think so … i’‘ve also running wildfire 3.2.2 with gatewas plugin … and my servers aren’'t listed on this page …

Here’'s a small update:

My own server does no longer appear on the “Server Sessions” page and I’'m unable to reproduce this issue with the latest version of the plugin.