Talk:Installing ejabberd: Difference between revisions
| Line 20: | Line 20: | ||
:::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) |
||
== Odd problem getting emulated users to collaborate == |
|||
== Confused on using with OLPC images and emulation == |
|||
I am using Ubuntu Gutsy and have installed my ejabberd server on my laptop from your excellent instructions |
I am using Ubuntu Gutsy and have installed my ejabberd server on my laptop from your excellent instructions. One thing worth mentioning for folks is that the special instructions for creating the .pem file are still necessary with this approach. It isn't there until you do. |
||
So now I have two QEMM services, also running on the same laptop. Before I started, I 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 current presence service log on either XO. |
|||
Now, connecting to my laptop jabber server with the jtest user running in Pidgin, I can see both of my emulated XOs showing up in the list. They can also see each other and make friends, etc. I can see them clearly in the admin tool in my browser. However, when I create a chat in one emulated XO and open it up to the neighborhood, the other emulated XO doesn't see it. Where should I look for the root of this kind of problem? |
|||
When I first started trying to hook the XOs to the jabber server, they knew nothing about its hostname, safina, the laptop on which they were running. To get around this, since they access it via 10.0.2.2, I added the FQDN (with its short name as an alias) to the local hosts file on each emulated XO. |
|||
One oddity about my network - while my router provides DNS for outside things, I depend upon local hosts files for the systems in my (very small) subnet. That way, I don't have any particular system I need to leave powered up. However, I don't think counting on hosts files for local name resolution will hurt anything, will it? |
|||
Revision as of 23:05, 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)
Odd problem getting emulated users to collaborate
I am using Ubuntu Gutsy and have installed my ejabberd server on my laptop from your excellent instructions. One thing worth mentioning for folks is that the special instructions for creating the .pem file are still necessary with this approach. It isn't there until you do.
So now I have two QEMM services, also running on the same laptop. Before I started, I 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.
Now, connecting to my laptop jabber server with the jtest user running in Pidgin, I can see both of my emulated XOs showing up in the list. They can also see each other and make friends, etc. I can see them clearly in the admin tool in my browser. However, when I create a chat in one emulated XO and open it up to the neighborhood, the other emulated XO doesn't see it. Where should I look for the root of this kind of problem?