Development discussions related to ejabberd, the premier Jabber server written in Erlang ;-)

Marc Haber | 1 May 2011 10:13

Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze)

Hi,

I am currently trying to migrate my personal ejabberd from a host
running Debian lenny to a different host running Debian squeeze. So I
have to face the challenges of (a) changing the host name in the
mnesia stuff and (b) doing the actual upgrade.

First, I dumped the database on the old host (ejabberd 2.0.1) to a dump file:
| ejabberdctl --node ejabberd <at> nechayev backup /tmp/backupfile
and moved the backup file to the new host.

The new host was installed with Debian squeeze, ejabberd 2.1.5
installed and running.

The procedure outlined in the README.Debian.gz file to change the host
name does not work as advertised:
| (jabberd)root <at> cucaracha:/home/mh# sudo -u ejabberd erl -pa /usr/lib/ejabberd/ebin
| Erlang R14A (erts-5.8) [source] [smp:2:2] [rq:2] [async-threads:0] [kernel-poll:false]
|
| Eshell V5.8  (abort with ^G)
| 1> mnesia_convert:change_node_name('ejabberd <at> nechayev','ejabberd <at> cucaracha',"/tmp/backupfile","/tmp/newnewfile").
| ** exception error: undefined function mnesia_convert:change_node_name/4
| 2>

I thus tried to use the older migration procedure that was outlined in
a forum entry on ejabberd.im:
| cucaracha:/home/mh# wget http://www.ejabberd.im/files/contributions/convert.erl
| cucaracha:/home/mh# erl
| Erlang (BEAM) emulator version 5.6.3 [source] [smp:2] [async-threads:0] [kernel-poll:false]
|

(Continue reading)

headers

Marc Haber | 1 May 2011 19:14

Changing hostname on Debian with 2.1.5 (was: Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze))

Hi,

On Sun, May 01, 2011 at 10:13:02AM +0200, Marc Haber wrote:
> I am currently trying to migrate my personal ejabberd from a host
> running Debian lenny to a different host running Debian squeeze. So I
> have to face the challenges of (a) changing the host name in the
> mnesia stuff and (b) doing the actual upgrade.

I have divided the problem into its two parts. The update from Debian
lenny to Debian squeeze was done with the old hostname and was done
fine. This left me with reaming the host.

I changed the hostname to the new value and proceeded to use the
"Change Computer Hostname" procedure from the Ejabberd Guide.

This failed already in step one:
cucaracha:/var/lib/ejabberd# ejabberdctl --node ejabber <at> nechayev start
Failed RPC connection to the node ejabber <at> nechayev: nodedown
cucaracha:/var/lib/ejabberd#

The procedure does not outline on which host one is supposed to do
this procedure. I guess that the procedure is to be done with the new
host name already in effect, otherwise the --node $OLDNODENAME
wouldn't make sense, would it?

What am I doing wrong?

Greetings
Marc

(Continue reading)

headers

Franky Orson | 2 May 2011 09:45

Re: Any way to get the Nickname of the 'from' on some Presence 'Subscribe' request?

On Sat, Apr 30, 2011 at 5:22 AM, Badlop <badlop <at> gmail.com> wrote:

2011/4/29 Franky Orson <franky.orson <at> gmail.com>:
> sudo ejabberdctl get_vcard bob myTest.com NICKNAME

Try to provide the username and host in lowercase.

I tried this - no go - same issue

> BTW, the following fails eventough the nickname is set for that user bob - I
> check via some client IQ - any idea? (using ejabberd 2.1.3)

That command works for me using 2.1.6.
Maybe it's a bug in 2.1.3

Maybe - I'll upgrade to 2.1.6 soon and will try again then

Thanks!

---
Badlop
ProcessOne
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

headers

Franky Orson | 2 May 2011 10:13

Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls

Running Ejabberd 2.1.3 - I connect fine with my own client using SASL most of the time but then as I'm testing disconnection and re-connection, I'm finding that Ejabberd is not setting the version when replying to my <stream:stream> request - see below - 1st paragraph is when it is working fine, then the 2nd paragraph is when the 'version' is not being sent as part of the reply from Ejbabberd like if it was not supporting XMPP version 1.0 as defined in RFC 3920 - this is mostly happening after a reconnection with the server but it is working 2 times out of the 3 - weird!

2011-05-02 00:34:20.681 [79543:40b] SEND: <?xml version='1.0'?>
2011-05-02 00:34:20.681 [79543:40b] SEND: <stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' to='myTest-server.com'>
2011-05-02 00:34:20.821 [79543:40b] RECV: <?xml version='1.0'?>
// Version being set fine here on this attempt...
2011-05-02 00:34:20.822 [79543:40b] RECV: <stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1519821603' from='myTest-server.com' version='1.0' xml:lang='en'>
2011-05-02 00:34:20.822 [79543:40b] RECV: <stream:features>
2011-05-02 00:34:20.822 [79543:40b] RECV: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: DIGEST-MD5</mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: <mechanism>
2011-05-02 00:34:20.823 [79543:40b] RECV: PLAIN</mechanism>
2011-05-02 00:34:20.824 [79543:40b] RECV: </mechanisms>
2011-05-02 00:34:20.824 [79543:40b] RECV: <register xmlns='http://jabber.org/features/iq-register'/>
2011-05-02 00:34:20.824 [79543:40b] RECV: </stream:features>
2011-05-02 00:34:20.825 [79543:40b] SEND: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='DIGEST-MD5'/>
...
...

Handskake working, etc...

** Now, here the issue after reconnecting (works 2 times out of 3) - the sample below failed and makes my client thinks Ejabberd does support SAS (not RFC 3920 compliant), hence I initiate the old way of authenticating with 'jabber:iq:auth'

2011-05-02 00:34:50.222 [79543:40b] SEND: <?xml version='1.0'?>
2011-05-02 00:34:50.222 [79543:40b] SEND: <stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' to='myTest-server.com'>
2011-05-02 00:34:50.299 [79543:40b] RECV: <?xml version='1.0'?>
// SEE BELOW - NO VERSION SET ON REPLY FROM EJABBERD!
2011-05-02 00:34:50.300 [79543:40b] RECV: <stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1443222350' from='myTest-server.com' xml:lang='en'>
2011-05-02 00:34:50.300 [79543:40b] SEND: <iq type="get">
<query xmlns="jabber:iq:auth"/>
</iq>
2011-05-02 00:34:50.300 [79543:40b] RECV: <stream:error>
2011-05-02 00:34:50.300 [79543:40b] RECV: <invalid-namespace xmlns='urn:ietf:params:xml:ns:xmpp-streams'/>
2011-05-02 00:34:50.301 [79543:40b] RECV: </stream:error>

Settings as:

{listen,
[
{5222, ejabberd_c2s, [
                        {access, c2s},
                        {shaper, c2s_shaper},
                        {max_stanza_size, 65536},
                        %%zlib,
                        starttls, {certfile, "/etc/ejabberd/ejabberd.pem"}
                       ]},
]}.

Any idea why this would be happening?

Thanks in advance,

--Frank

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

headers

Stephan Maihöfer | 2 May 2011 13:03

messages to wrong ressources

hi,

we are still trying to figure out why we get these duplicate messages:

<message xmlns='jabber:client' from='22515077 <at> muc.example.com/steam'
to='1762237 <at> example.com/web_2143633635130417940746693' type='groupchat'><body>doppelt</body></message>
<message xmlns='jabber:client' from='22515077 <at> muc.example.com/steam'
to='1762237 <at> example.com/api_push' type='groupchat'><body>doppelt</body></message>

we get both of these in the client connected as something else entirely (say, /other_client).

we wrote this message the message was written on /web_2143633635130417940746693.

/api_push is nothing but a temporary resource that we use in connection with mod_rest
to update presence information of our user. i "admit" that we do not properly leave
the room after sending presence there, but no client should get messages that are
not adressed to another resource, right?

these message appear only on the clients that are connected with the same _bare_
jid as the same writing clients, other clients get the message only once as it should be.

i can not find any obvious error in the ejabberd 2.1.3 we are using, so i am
asking the list if anyone has seen things like this happen?

greetings,
stephan

headers

Konstantin Khomoutov | 2 May 2011 16:22

Re: Changing hostname on Debian with 2.1.5 (was: Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze))

On Sun, May 01, 2011 at 07:14:28PM +0200, Marc Haber wrote:

> On Sun, May 01, 2011 at 10:13:02AM +0200, Marc Haber wrote:
> > I am currently trying to migrate my personal ejabberd from a host
> > running Debian lenny to a different host running Debian squeeze. So I
> > have to face the challenges of (a) changing the host name in the
> > mnesia stuff and (b) doing the actual upgrade.
> 
> I have divided the problem into its two parts. The update from Debian
> lenny to Debian squeeze was done with the old hostname and was done
> fine. This left me with reaming the host.
> 
> I changed the hostname to the new value and proceeded to use the
> "Change Computer Hostname" procedure from the Ejabberd Guide.
> 
> This failed already in step one:
> cucaracha:/var/lib/ejabberd# ejabberdctl --node ejabber <at> nechayev start
> Failed RPC connection to the node ejabber <at> nechayev: nodedown
> cucaracha:/var/lib/ejabberd#
> 
> The procedure does not outline on which host one is supposed to do
> this procedure. I guess that the procedure is to be done with the new
> host name already in effect, otherwise the --node $OLDNODENAME
> wouldn't make sense, would it?
> 
> What am I doing wrong?

Hi, Marc!

(I maintain ejabberd in Debian, so I'm probably the right person to talk
to about this issue.)

The problem is two-fold.

The first thing to consider is that the ejabberdctl script in the Debian
package differs from that of upstream: in Debian, start/stop/restart
actions are carried out by the rc-script /etc/init.d/ejabberd which calls
two "back-end" scripts -- /usr/sbin/ejabberd which is used to start an
instance of ejabberd and /usr/sbin/ejabberdctl which is used to control
that running instance.
The ejabberdctl script from upstream performs both of these tasks.

I think the closest thing to replace
# ejabberdctl --node ejabberd <at> oldnode start
is changing the ERLANG_NODE variable in the /etc/default/ejabberd
file to read "ejabberd <at> oldnode" and then start it using 
# /etc/init.d/ejabberd start
or even
# /etc/init.d/ejabberd live
to easily see if it was able to start OK.

The second thing is converting the backup file.
This can be done as described in points 6-8 in the "Change Computer
Hostname" section of the official guide.

Alternatively, the conversion can be done as described in README.Debian,
but the command for conversion will be different:
ejabberd_admin:mnesia_change_nodename
instead of
mnesia_convert:change_node_name
(the meaning and ordering of the arguments is be the same).

In any case, the Debian package's README file has to be updated.
I would be grateful if you would summarise the results of your quest
here so I would have a clearer idea about what exactly to write there.

headers

Badlop | 2 May 2011 17:34

Re: Mod_multicast service-unavailable

I've now updated this branch:
https://git.process-one.net/~badlop/ejabberd/badlop-ejabberd/commits/multicast-2.1.x

When compiled, installed, and configured mod_multicast with empty options,
your disco#info query works.

---
Badlop
ProcessOne

headers

Badlop | 2 May 2011 19:00

Re: Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls

2011/5/2 Franky Orson <franky.orson <at> gmail.com>:
> Running Ejabberd 2.1.3 - I connect fine with my own client using SASL most
> of the time but then as I'm testing disconnection and re-connection, I'm
> finding that Ejabberd is not setting the version when replying to my
> <stream:stream> request - see below - 1st paragraph is when it is working

>  this is mostly happening after a reconnection with
> the server but it is working 2 times out of the 3 - weird!

Looking at the ejabberd 2.1.3 source code, the lack of version in the
response can only happen when the request had unexpected xmlns:stream,
hostname, or version. So, if your client sends exactly the same
request, ejabberd should produce exactly the same response. But
according to your tests, ejabberd doesn't.

And apparently this happens only when the client reconnects, and only
sometimes, and only with a custom client that only you have.

To continue investigating, you either:
A) explain how to reproduce the problem
B) or join the ejabberd chatroom, and when we meet, we'll do live
debugging. You'll need to make small changes to ejabberd source code,
compile, provoke the problem, tell me the result. And repeat until we
find some clue about what's wrong in ejabberd, or in your client.

---
Badlop
ProcessOne

headers

Franky Orson | 2 May 2011 21:09

Re: Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls

Thank you Badlop and Yes I'm going to try and reproduce the problem (assuming I can) with a smaller test case.

It is very likely that this might not be an Ejabberd issue - The way I workaround the issue right now is by delaying reconnection by a bit and in this case the issue doesn't manifest - am wondering if this could be a race condition in my client (where I had forced disconnections in my tests to happen at various times) and trying to reconnect too fast maybe - would this pattern explain this answer back from Ejabberd in that case? I'll dig more and let you know in anycase. Thanks again.

On Mon, May 2, 2011 at 10:00 AM, Badlop <badlop <at> gmail.com> wrote:

2011/5/2 Franky Orson <franky.orson <at> gmail.com>:
> Running Ejabberd 2.1.3 - I connect fine with my own client using SASL most
> of the time but then as I'm testing disconnection and re-connection, I'm
> finding that Ejabberd is not setting the version when replying to my
> <stream:stream> request - see below - 1st paragraph is when it is working

> this is mostly happening after a reconnection with
> the server but it is working 2 times out of the 3 - weird!

Looking at the ejabberd 2.1.3 source code, the lack of version in the
response can only happen when the request had unexpected xmlns:stream,
hostname, or version. So, if your client sends exactly the same
request, ejabberd should produce exactly the same response. But
according to your tests, ejabberd doesn't.

And apparently this happens only when the client reconnects, and only
sometimes, and only with a custom client that only you have.

To continue investigating, you either:
A) explain how to reproduce the problem
B) or join the ejabberd chatroom, and when we meet, we'll do live
debugging. You'll need to make small changes to ejabberd source code,
compile, provoke the problem, tell me the result. And repeat until we
find some clue about what's wrong in ejabberd, or in your client.

---
Badlop
ProcessOne
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

headers

Jorge Díaz | 2 May 2011 22:07

Re: Mod_multicast service-unavailable

Thanks a lot for your fast response.

What you mean with empty options?

It disco#info query won't work if you setup a host option?

Just to ensure.

Thanks again.

Jorge

On Mon, May 2, 2011 at 12:34 PM, Badlop <badlop <at> gmail.com> wrote:

I've now updated this branch:
https://git.process-one.net/~badlop/ejabberd/badlop-ejabberd/commits/multicast-2.1.x

When compiled, installed, and configured mod_multicast with empty options,
your disco#info query works.

---
Badlop
ProcessOne
_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

--
Jorge Díaz
email: jorgedf <at> gmail.com
spain: +34 620829213

us: +1 (415) 309-8039

chile: +56 (9) 87038661
skype: xurdedf

about.me/xurde

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

23	June 2013
39	May 2013
38	April 2013
41	March 2013
10	February 2013
37	January 2013
45	December 2012
92	November 2012
39	October 2012
31	September 2012
44	August 2012
70	July 2012
24	June 2012
63	May 2012
60	April 2012
32	March 2012
46	February 2012
56	January 2012
39	December 2011
75	November 2011
62	October 2011
37	September 2011
50	August 2011
84	July 2011
62	June 2011
120	May 2011
92	April 2011
78	March 2011
45	February 2011
36	January 2011
40	December 2010
74	November 2010
30	October 2010
59	September 2010
29	August 2010
57	July 2010
46	June 2010
76	May 2010
89	April 2010
65	March 2010
119	February 2010
194	January 2010
134	December 2009
71	November 2009
50	October 2009
97	September 2009
112	August 2009
77	July 2009
78	June 2009
87	May 2009
102	April 2009
116	March 2009
62	February 2009
75	January 2009
76	December 2008
98	November 2008
127	October 2008
132	September 2008
108	August 2008
64	July 2008
167	June 2008
169	May 2008
64	April 2008
26	March 2008
108	February 2008
96	January 2008
93	December 2007
44	November 2007
74	October 2007
116	September 2007
113	August 2007
87	July 2007
47	June 2007
54	May 2007
60	April 2007
105	March 2007
110	February 2007
34	January 2007
47	December 2006
47	November 2006
89	October 2006
109	September 2006
24	August 2006
109	July 2006
27	June 2006
190	May 2006
57	April 2006
57	March 2006
50	February 2006
70	January 2006
37	December 2005
57	November 2005
28	October 2005
35	September 2005
83	August 2005
51	July 2005
80	June 2005
75	May 2005
95	April 2005
149	March 2005
67	February 2005
68	January 2005
132	December 2004
87	November 2004
127	October 2004
55	September 2004
113	August 2004
31	July 2004
8	June 2004
13	May 2004
22	April 2004
13	March 2004
20	February 2004
7	January 2004
2	December 2003
12	November 2003
1	October 2003
13	September 2003
27	August 2003

Mon	Tue	Wed	Thu	Fri	Sat	Sun

						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30	31

Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze)

Changing hostname on Debian with 2.1.5 (was: Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze))

Re: Any way to get the Nickname of the 'from' on some Presence 'Subscribe' request?

Ejbabberd *not* returning xmpp version on <stream:stream/> from time to time - Starttls

messages to wrong ressources

Re: Changing hostname on Debian with 2.1.5 (was: Debian Migration from 2.0.1 to 2.1.5 (lenny => squeeze))

Re: Mod_multicast service-unavailable

Re: Ejbabberd *not* returning xmpp version on <stream:stream/> from time to time - Starttls

Re: Ejbabberd *not* returning xmpp version on <stream:stream/> from time to time - Starttls

Re: Mod_multicast service-unavailable

Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls

Re: Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls

Re: Ejbabberd not returning xmpp version on <stream:stream/> from time to time - Starttls