Talk:Installing ejabberd: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 19: Line 19:


:::Time to look at the presenceservice.log on those sugar instances - in ~/.sugar/sugar1/logs/presenceservice.log and .../sugar2/... - if you can pastebin those or stick them somewhere, I'll take a look.--[[User:Morgs|morgs]] 06:31, 8 March 2008 (EST)
:::Time to look at the presenceservice.log on those sugar instances - in ~/.sugar/sugar1/logs/presenceservice.log and .../sugar2/... - if you can pastebin those or stick them somewhere, I'll take a look.--[[User:Morgs|morgs]] 06:31, 8 March 2008 (EST)

== Confused on using with OLPC images and emulation and hosts files ==

I am using Ubuntu Gutsy and have installed my ejabberd server on my laptop from your excellent instructions but I'm having trouble getting my two QEMM services, also running on the same laptop, to talk to my server. I've checked that both emulated XOs are functioning and networked properly by running a chat briefly through the Quebec OLPC Community server. This worked without difficulty.

When I tail -f my ejabberd log, I can see the one line for each emulated XOs connecting to the server. However, there is no further logging for either. There is nothing in the presence service log on either XO.

When I first started trying to hook the XOs to the server, they knew nothing about its hostname, brigantine, the laptop on which they were running. To get around this, since they access it via 10.0.2.2, I added the name (with its FQDN as an alias) to the local hosts file on each emulated XO. The second is that when I try to do an http connection locally on my laptop to the admin http page, I have to use http://localhost:5280/admin. If I use http://brigantine.macksoft.com:5280/admin, it doesn't work. (I can ping my own system by name, though, of course.)

On my domestic network I keep all my machines shut down when I'm not using them - y'know - thinking green. Consequently, since I can't designate anything as an external server, I use a common set of local hosts files on my five or six systems to hold things together rather than a local DNS server. For external addresses, I point DNS to my Linksys router, which points to my service provider. This has worked for most everything else, but I haven't been working much with the emulated XOs. I think this arrangement may be near the root of my problem. Is there something else I should be doing?

Revision as of 16:07, 16 March 2008

Instructions for Fedora

I'd like to have these instructions on building ejabberd for Fedora too, but I don't have Fedora. Perhaps someone can do a Fedora version?--morgs 08:52, 4 March 2008 (EST)

Packages

RPMs are currently a bit out of date (ejabberd2 beta). debs are very out of date (ejabberd 1.4). If/when I can build newer packages and/or prod those who built the current packages, I'll add them as installing packages would be much easier than building from source.--morgs 08:54, 4 March 2008 (EST)

Can't see the "everybody" group?

I followed these instructions as well as I could, but I don't see the "everybody" group in Gajim. The sugar-jhbuild's name is "sugar1". When I try "ejabberdctl connected-users", I just get the Gajim client connected.

Suggestions?

You need at least two users on the server for it to show up on your buddy list. You don't see yourself. What works for me, although it's a bit confusing, is to add a second account in the same client (I used pidgin in my testing, but should be the same in others) - then put both accounts online, and the "everybody" group appears and shows both accounts. (What is really happening is that one account sees the other, and the second account sees the first, in the same buddy list.)
Or, you could use two different jabber clients on the same machine - less confusing but more work...--morgs 03:08, 6 March 2008 (EST)
I should be more exact. Basically, I'm trying to set up a development environment for a Sugar activity. I have two Sugar profiles - "sugar1" and "sugar2". When I share a Sugar activity from "sugar1", it does not show up in either the Analyze activity OR the other sugar-jhbuild environment. I have the jabber server set to "localhost" on both profiles. Suggestions? --kawk 21:37, 7 March 2008 (EST)
Time to look at the presenceservice.log on those sugar instances - in ~/.sugar/sugar1/logs/presenceservice.log and .../sugar2/... - if you can pastebin those or stick them somewhere, I'll take a look.--morgs 06:31, 8 March 2008 (EST)

Confused on using with OLPC images and emulation and hosts files

I am using Ubuntu Gutsy and have installed my ejabberd server on my laptop from your excellent instructions but I'm having trouble getting my two QEMM services, also running on the same laptop, to talk to my server. I've checked that both emulated XOs are functioning and networked properly by running a chat briefly through the Quebec OLPC Community server. This worked without difficulty.

When I tail -f my ejabberd log, I can see the one line for each emulated XOs connecting to the server. However, there is no further logging for either. There is nothing in the presence service log on either XO.

When I first started trying to hook the XOs to the server, they knew nothing about its hostname, brigantine, the laptop on which they were running. To get around this, since they access it via 10.0.2.2, I added the name (with its FQDN as an alias) to the local hosts file on each emulated XO. The second is that when I try to do an http connection locally on my laptop to the admin http page, I have to use http://localhost:5280/admin. If I use http://brigantine.macksoft.com:5280/admin, it doesn't work. (I can ping my own system by name, though, of course.)

On my domestic network I keep all my machines shut down when I'm not using them - y'know - thinking green. Consequently, since I can't designate anything as an external server, I use a common set of local hosts files on my five or six systems to hold things together rather than a local DNS server. For external addresses, I point DNS to my Linksys router, which points to my service provider. This has worked for most everything else, but I haven't been working much with the emulated XOs. I think this arrangement may be near the root of my problem. Is there something else I should be doing?