Server Initialization of Port 5222 and 5269

I tried FAQ but server seems to be down.

RH62 Jabber 1.4.2

System has been running for awhile now.  Had a problem with MySQL on this
server (not using with jabber) and the server went into a strange state.
After rebooting, jabber clients started telling me they couldn't connect.
Looking at the server it looked fine, but the error.log reveled the
following:

...snip...
20020331T23:03:22: [notice] (-internal): initializing server
20020331T23:03:22: [alert] (-internal): io_select unable to listen on 5222
[(null)]
20020331T23:03:22: [alert] (-internal): io_select unable to listen on 5269
[(null)]

Anyone know what is wrong?

RE: Server Initialization of Port 5222 and 5269

Patrick Nelson wrote:
----------------->>>>
I tried FAQ but server seems to be down.

RH62 Jabber 1.4.2

System has been running for awhile now.  Had a problem with MySQL on this
server (not using with jabber) and the server went into a strange state.
After rebooting, jabber clients started telling me they couldn't connect.
Looking at the server it looked fine, but the error.log reveled the
following:

...snip...
20020331T23:03:22: [notice] (-internal): initializing server
20020331T23:03:22: [alert] (-internal): io_select unable to listen on 5222
[(null)]
20020331T23:03:22: [alert] (-internal): io_select unable to listen on 5269
[(null)]

Anyone know what is wrong?
----------------->>>>
Well some messing around and I got it back up.  This is what I did...

I have an init.d file that uses RedHats daemon function to start jabber in
the following manner:

 daemon /usr/loca/jabber-1.4.2/jabberd/jabberd -U jabber -B

However this continues to produce the errors so I just went to the directory
/usr/local/jabber-1.4.2 and ran:

Re: jabber+mysql

hi kamesh.
Please check out xdb_sql this has all functionality you need to store 
information on mysql db. The tarball contains the docs as well.

kamesh jayachandran wrote:

> Hi all,
> I have jabber running in my machine as of now user's information is kept as username.xml for each user.I
want to keep this information in the mysql database.Can anyone point me to the documents helping me
achieving this?
> With regards
> kamesh jayachandran
> 
> 
> _______________________________________________
> jadmin mailing list
> jadmin <at> jabber.org
> http://mailman.jabber.org/listinfo/jadmin
> 

--

-- 
Raditha Dissanayake
raditha <at> mediasolv.com
http://www.mediasolv.com/?rd

Re: wanna use Jabber for local network IM server

Hi guido,
it's indeed possible to use jabber for your local network. However we 
need more information in order to help you. Stuff like did you server 
compile correctly? did it start properly? etc.

Guido R.Rol ón A. wrote:

> I wanna use Jabber for my local network IM server.
> Jabber 1.4.1-5
> I use gabber to connect to it.
> Gabber 0.8.4-3
> I get broken pipe message all the time.
> 
> BTW, i use linx mandrake 8.1
> 
> Is possible touse Jabber for my local network?, 
> 
> Thanks
> Guido
> _______________________________________________
> jadmin mailing list
> jadmin <at> jabber.org
> http://mailman.jabber.org/listinfo/jadmin
> 

--

-- 
Raditha Dissanayake
raditha <at> mediasolv.com
http://www.mediasolv.com/?rd

Can anybody help on LDAP

s2s connections failing ("sending name is invalid")

Hi folks,

I recently checked my error logs and got an awful lot of these messages:
We were told by charente.de that our sending name crunchy-frog.org is invalid, 
either something went wrong on their end, we tried using that name improperly, 
or dns does not resolve to us

I guess this is because the reverse-lookup of my server's IP address doesn't 
return the hostname the server itself is using (crunchy-frog.org). 
(mawis if you're reading this: can you take a look at charente.de's logfiles
and confirm, that this is the problem?)

Unfortunately changing the reverse lookup isn't possible. So the obvious 
question is: is there some config option that I can use to set the 
"sending name" without changing the name my Jabber server is
using (i.e. I still want all users to have * <at> crunchy-frog.org JIDs and not
something like * <at> nasty-very-long-name)?

Thanx,
	Konrad

________________________________________________________________
  .~.   Konrad Podloucky      GnuPG/PGP-key available by request
  /V\   "If there's anything more important than my ego, I want
 // \\   it caught and shot--now!"  --Zaphod Beeblebrox
/(   )\ "The Hitchhiker's Guide to the Galaxy", Douglas Adams
 ^^-^^   

Illegal characters in passwords?

If I have users with the '&' character in their password, they don't 
seem able to log in. Is this a forbidden character in passwords or 
something? Is there a list somewhere of what is and is not forbidden 
in a password, because I can't seem to find anything about it in the 
Jabber book, and I just distributed passwords to our employee base 
(randomly generated) and a bunch of them contain the "&" character. 
:-/

D

--

-- 
+---------------------+-----------------------------------------+
| dredd <at> megacity.org  | "Thou art the ruins of the noblest man  |
|  Derek J. Balling   |  That ever lived in the tide of times.  |
|                     |  Woe to the hand that shed this costly  |
|                     |  blood" - Julius Caesar Act 3, Scene 1  |
+---------------------+-----------------------------------------+

Re: Illegal characters in passwords?

On Mon, Apr 01, 2002 at 08:47:33AM -0500, Derek Balling wrote:
| If I have users with the '&' character in their password, they don't 
| seem able to log in. Is this a forbidden character in passwords or 
| something? Is there a list somewhere of what is and is not forbidden 
| in a password, because I can't seem to find anything about it in the 
| Jabber book, and I just distributed passwords to our employee base 
| (randomly generated) and a bunch of them contain the "&" character. 
| :-/

Is the password stored in an XML file?  If so, is it properly escaped?
I think the escape for a '&' character is '&'.

-D

--

-- 

Windows, hmmm, does it come with a GUI interface that works or just
pretty blue screens?

JIM new user registration broken in 1.4.2?

Did jabberd 1.4.2 break new user registration from JIM?  Ever since
upgrading to 1.4.2, I've been unable to add new users from JIM's
new account wizard, while WinJab and Exodus work just fine.

("Just use winjab/exodus" is, unfortunatly, not a workable approach
right now, as neither one of them implements mod_groups correctly.)

Any insight anyone could offer would be appreciated.

The error looks like this in the debug log:

mio.c:760 MIO read from socket 14: <stream:stream to="galactus.feedroom.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams">
c2s [client.c:277] pthsock_client_read called with: m:BFA10 flag:2 arg:EFE80
c2s [client.c:310] root received for 14
c2s [client.c:315] Recieved connection to: galactus.feedroom.com
mio.c:1054 mio_write called on x: 0 buffer: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' id='3CA87C01' xmlns='jabber:client' from='galactus.feedroom.com'>
mio.c:279 write_dump writing data: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' id='3CA87C01' xmlns='jabber:client' from='galactus.feedroom.com'>
mio.c:607 mio while loop top
mio.c:620 mio while loop, working
mio.c:607 mio while loop top
mio.c:620 mio while loop, working
mio.c:760 MIO read from socket 14: <iq type="get" id="JCOM_0"><query xmlns="jabber:iq:register"></query></iq>
c2s [client.c:277] pthsock_client_read called with: m:BFA10 flag:3 arg:EFE80
deliver.c:474 DELIVER 4:galactus.feedroom.com <route type='auth' to='galactus.feedroom.com'
from='14 <at> c2s/BFA10'><iq type='get' id='JCOM_0'><query xmlns='jabber:iq:register'/></iq></route>
deliver.c:678 delivering to instance 'sessions'
deliver.c:94 (77C30)incoming packet <route type='auth' to='galactus.feedroom.com'
from='14 <at> c2s/BFA10'><iq type='get' id='JCOM_0'><query xmlns='jabber:iq:register'/></iq></route>
util.c:103 config query maxusers
deliver.c:100 creating user hash 1183C0 for galactus.feedroom.com
deliver.c:102 checking 1183C0
util.c:103 config query auth
mtq 129D38 starting
mtq 129D38 leaving to pth
mtq 139FD0 starting
mtq 139FD0 leaving to pth
mtq 14A268 starting
mtq 14A268 leaving to pth
mtq 15A500 starting
mtq 15A500 leaving to pth
mtq 16A798 starting
mtq 16A798 leaving to pth
mtq 17AA30 starting
mtq 17AA30 leaving to pth
mtq 129D38 entering from pth
mtq 129D38 one call 1179B0
authreg.c:84 registration get request
modules.c:135 mapi_call 6
modules.c:158 MAPI C5310
modules.c:158 MAPI C5BD0
modules.c:158 MAPI C5C90
util.c:103 config query mod_auth_0k/enable_registration
modules.c:158 MAPI C5CF0
util.c:103 config query register
mod_register checking
deliver.c:474 DELIVER 4:galactus.feedroom.com <route from='14 <at> c2s/BFA10'
to='galactus.feedroom.com' type='auth'><iq type='result' id='JCOM_0'><query xmlns='jabber:iq:register'>
        <instructions>Choose a username and password to register with this server.</instructions>
        <name/>
        <email/>
      </query></iq></route>
deliver.c:678 delivering to instance 'sessions'
deliver.c:94 (77C30)incoming packet <route from='14 <at> c2s/BFA10' to='galactus.feedroom.com'
type='auth'><iq type='result' id='JCOM_0'><query xmlns='jabber:iq:register'>
        <instructions>Choose a username and password to register with this server.</instructions>
        <name/>
        <email/>
      </query></iq></route>
util.c:103 config query auth
mtq 129D38 leaving to pth
mtq 18ACC8 starting
mtq 18ACC8 leaving to pth
mtq 19AF60 starting
mtq 19AF60 leaving to pth
mtq 1AB1F8 starting
mtq 1AB1F8 leaving to pth
mtq 1BB490 starting
mtq 1BB490 leaving to pth
mtq 139FD0 entering from pth
mtq 139FD0 one call 1CC058
authreg.c:95 registration set request
deliver.c:474 DELIVER 4:c2s <route from='galactus.feedroom.com'to='14 <at> c2s/BFA10'
type='auth'><iq type='error' id='JCOM_0'><query xmlns='jabber:iq:register'>
        <instructions>Choose a username and password to register with this server.</instructions>
        <name/>
        <email/>
      </query><error code='406'>Not Acceptable</error></iq></route>
deliver.c:678 delivering to instance 'c2s'
c2s [client.c:164] galactus.feedroom.com has an active session,delivering packet
log.c:186 <log type='record' from='galactus.feedroom.com'>loginfail 10.0.12.27 406 (null)</log>
deliver.c:474 DELIVER 3:galactus.feedroom.com <log type='record'
from='galactus.feedroom.com'>login fail 10.0.12.27 406 (null)</log>
deliver.c:678 delivering to instance 'rlogger'
c2s [client.c:236] Writing packet to MIO: <iq type='error' id='JCOM_0'><query xmlns='jabber:iq:register'>
        <instructions>Choose a username and password to register with this server.</instructions>
        <name/>
        <email/>
      </query><error code='406'>Not Acceptable</error></iq>
mio.c:1054 mio_write called on x: 116FB8 buffer: (null)
mtq 139FD0 leaving to pth
mio.c:607 mio while loop top
mio.c:620 mio while loop, working
mio.c:279 write_dump writing data: <iq type='error' id='JCOM_0'><query xmlns='jabber:iq:register'>
        <instructions>Choose a username and password to register with this server.</instructions>
        <name/>
        <email/>
      </query><error code='406'>Not Acceptable</error></iq>
mio.c:607 mio while loop top
mio.c:620 mio while loop, working
c2s [client.c:277] pthsock_client_read called with: m:BFA10 flag:4 arg:EFE80
c2s [client.c:282] io_select Socket 14 close notification
mio.c:366 freed MIO socket

-n

------------------------------------------------------------<memory <at> blank.org>
                      "We're the dot in `Fuck.You!'"
<http://blank.org/memory/>----------------------------------------------------

User Persistence