James, thank you very much! :)

It is of course my own stupid mistake. I had a problem with the server
tonight and the server rebooted. Since I just added the listen for 5346 in
the web config for ejabberd it was lost at the reboot and hence it is not
listening to the port no more. 

Very sorry to bother you with this when it was just my own stupid fault! 

Best regards
Stian B. Barmen 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> James Bunton
> Sent: Thursday, January 26, 2006 1:36 PM
> To: PyAIM-t/PyICQ-t/PyMSN-t Discussion
> Subject: Re: [py-transports] Rev. 107 problems with twisted 
> XmlStreamFactorysomething
> 
> Is that port (5346) the correct port to connect to you jabberd?
> Make sure you can do telnet 127.0.0.1 5346 and connect.
> 
> ---
> 
> James
> 
> 
> On 26/01/2006, at 10:48 PM, Stian B. Barmen wrote:
> 
> >  Of course. <unknown.png>
> >
> >  For the beta transport I have startet it from the command 
> line as the 
> > jabber:jabber user which has rights for the 
> /usr/local/PyMSNt dir and 
> > the spool dir /var/spool/jabber/pymsnt-beta. The command is simply 
> > "./PyMSNt.py".
> >
> >  My config per now is:
> >
> > <pymsnt>
> > <!-- This file contains options to be configured by the server 
> > administrator. -->
> > <!-- Please read through all the options in this file -->
> >
> > <!-- The JabberID of the transport --> <jid>msn-beta.jabber.no</jid>
> > <!-- The public IP of the machine the transport is running on --> 
> > <ip>217.199.39.160</ip>
> > <!-- The component JID of the transport. Unless you're doing 
> > clustering, leave this alone -->
> > <!-- <compjid>msn1</compjid> -->
> >
> >
> > <!-- The location of the spool directory.. if relative, relative to 
> > the PyMSNt dir.
> > Do not include the jid of the transport --> 
> > <spooldir>/var/spool/jabber/pymsnt-beta</spooldir>
> > <!-- The location of the PID file, relative to the PyMSNt directory 
> > --> <pid>PyMSNt.pid</pid>
> > <!-- If set, the transport will background itself when run --> 
> > <background/>
> >
> >
> > <!-- The IP address of the main Jabber server to connect to --> 
> > <mainServer>127.0.0.1</mainServer>
> > <!-- The website of the Jabber service -->  
> > <website>http://www.jabber.no</website>
> > <!-- The TCP port to connect to the Jabber server on (this is the 
> > default for Jabberd2) --> <port>5346</port>
> > <!-- The authentication token to use when connecting to the Jabber 
> > server --> <secret>want_to_keep_it_secret!!</secret>
> > <!-- The Twisted reactor to choose. Pick poll or epoll on Linux, 
> > kqueue on BSD. Or leave as default (select) -->
> > <!-- <reactor>poll</reactor> -->
> >
> >
> > <!-- The default language to use -->
> > <lang>en</lang>
> >
> >
> > <!-- Comment out the following options to disable them, or 
> uncomment 
> > them to enable them -->
> > <!-- Send email notification messages to users -->
> > <mailNotifications/>
> > <!-- Send greeting on login -->
> > <!-- <sessionGreeting>You have just started a session with 
> > PyMSNt</sessionGreeting> -->
> > <!-- Send message on successful registration -->
> > <!-- <registerMessage>You have successfully registered with 
> > PyMSNt</registerMessage> -->
> > <!-- Allow users to register with this transport -->
> > <allowRegister/>
> > <!-- Get all avatars. If this is set to true then avatars 
> are grabbed 
> > for all your contacts immediately. If false then avatars are only 
> > grabbed when you're in a chat with a contact -->
> > <getAllAvatars/>
> > <!-- Use Jabber.com's XCP component protocol extensions. -->
> > <!-- <useXCP/> -->
> >
> >
> > <!-- File transfer settings -->
> > <!-- Please give the port to listen for Jabber socks5 
> transfers on. -->
> > <ftJabberPort>8008</ftJabberPort>
> > <!-- Please give the port to listen for HTTP GETs here (Used in OOB 
> > file transfers). -->
> > <ftOOBPort>8080</ftOOBPort>
> > <!-- Please give the root URL the transport should send to clients. 
> > (You can use an Apache reverse proxy to put this on your ordinary 
> > website) -->
> >  <ftOOBRoot>http://jabber.no:8080</ftOOBRoot>
> >
> > <!-- You can choose which users you wish to have as administrators. 
> > These users can perform some tasks with Ad-Hoc commands that others 
> > cannot -->
> > <!--<admins>
> >  <jid>[EMAIL PROTECTED]</jid>
> > </admins>-->
> >
> >
> > <!-- Log settings -->
> >
> > <!-- The logging level
> > 0 -> No logging
> > 1 -> Log tracebacks
> > 2 -> Log tracebacks, warnings and errors
> > 3 -> Log everything -->
> > <debugLevel>3</debugLevel>
> >
> > <!-- The file to log to. Leave this disabled for stdout -->
> > <debugFile>debug.log</debugFile>
> >
> > </pymsnt>
> >
> >
> >  tor, 26,.01.2006 kl. 22.38 +1100, skrev James Bunton:
> >> How are you starting the transport?
> >> Could we have a look at your config file?
> >>
> >>
> >> ---
> >>
> >> James
> >>
> >>
> >> On 26/01/2006, at 7:48 PM, Stian B. Barmen wrote:
> >>
> >> > When I try to start the latest rev it doesnt start, or listen for
> >> > requests.
> >> > I had to start debugging level 3 before I got anyting in 
> the debug
> >> > logg and
> >> > there is the following message:
> >> >
> >> > [2006-01-26 09:45:21] INFO ::  ::  :: addNode :: 
> ServerDiscovery ::
> >> > {'node':
> >> > 'stats', 'jid': 'msn-beta.jabber.no', 'name': 
> 'command_Statistics',
> >> > 'self':
> >> > 'instance', 'handler': <bound method AdHocCommands.incomingIq of
> >> > <misciq.AdHocCommands instance at 0xb7b3e42c>>, 
> 'rootnode': False}
> >> > [2006-01-26 09:45:21] Starting factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:21] <twisted.internet.tcp.Connector instance at
> >> > 0xb7b403ec> will retry in 2 seconds
> >> > [2006-01-26 09:45:21] Stopping factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:23] Starting factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:23] <twisted.internet.tcp.Connector instance at
> >> > 0xb7b403ec> will retry in 5 seconds
> >> > [2006-01-26 09:45:23] Stopping factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:29] Starting factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:29] <twisted.internet.tcp.Connector instance at
> >> > 0xb7b403ec> will retry in 17 seconds
> >> > [2006-01-26 09:45:29] Stopping factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:46] Starting factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:45:46] <twisted.internet.tcp.Connector instance at
> >> > 0xb7b403ec> will retry in 49 seconds
> >> > [2006-01-26 09:45:46] Stopping factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:46:35] Starting factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> > [2006-01-26 09:46:35] <twisted.internet.tcp.Connector instance at
> >> > 0xb7b403ec> will retry in 130 seconds
> >> > [2006-01-26 09:46:35] Stopping factory
> >> > 
> <twisted.words.protocols.jabber.xmlstream.XmlStreamFactory instance 
> >> at
> >> > 0xb7b39fec>
> >> >
> >> > Hope you have the solution for this problem :)
> >> >
> >> > Best regards
> >> > Stian B. Barmen
> >> >
> >> >
> >> > _______________________________________________
> >> > py-transports mailing list
> >> > py-transports@blathersource.org
> >> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> >> >
> >>
> >> _______________________________________________
> >> py-transports mailing list
> >> py-transports@blathersource.org
> >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> >>
> > <smiley-3.png>_______________________________________________
> > py-transports mailing list
> > py-transports@blathersource.org
> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> 
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
> 

Reply via email to