[Server-devel] Problems with EjabberD setup and how to test if it's working

[Carol Farlow Lerche]

Martin, et. al:  In my experience one of the most fruitful additions to any
system that is going to be deployed in the field and used by persons
unfamiliar with the underlying technology is a prepackaged way for the user
to submit a trouble report that has all the needed info (logs, config files,
etc.) without the user having to know what these are.  So in the case of the
xs, would it be possible to write a python script that pulled the last 100
lines of the syslog, the ejabberd log, etc. and relevant configuration files
and zipped or tarred them into a place reachable by the reporter's browser.
Then a problem report could be an email with whatever the user saw, together
with the lump of diagnostic data that they downloaded via their browser from
the xs.  Hopefully the user could request that the script be run through a
web interface, but even if it was a terminal, it would be better if a one
line command could be documented.  From the xo, this could even be done with
ssh to the xs.

On Sat, Apr 18, 2009 at 8:41 AM, Yifan <yifan.sun at students.olin.edu> wrote:

> Hi Daniel,
>
> Thanks for your response! The wiki page I'm referring to is
> http://wiki.laptop.org/go/Ejabberd_Configuration and
> http://wiki.laptop.org/go/Installing_ejabberd.
>
> I am using XS. What command should I use to display the current version?
> (I'm not too familiar with linux hacking, and I have several stored images,
> so I'm not entirely sure which one I used.)
>
> Sorry about the vague error report. I'm not sure what the exact error is,
> since we used the web interface, and there were no error messages; the only
> feedback we got was that nothing was working the way we had expected. My
> mental model (and please correct me if it's wrong) is that after configuring
> the server and setting up an admin account, any laptop that's connected to
> that server can be registered using Terminal, typing "sugar-control-panel -s
> jabber <server name>". Then, in the web client, we should then see each
> laptop being registered.
>
> However, what we found was that if the laptop was properly connected, and
> no other users (except the admin user) were registered, that laptop would
> register properly, but any subsequent laptop couldn't register.
>
> We then used the web interface to remove the user (I don't remember the
> exact sequence of steps ('m not on site) but I believe we selected the user,
> then chose the "remove user" option, or something similar). After that, that
> particular laptop couldn't be re-added using the "sugar-control-panel -s
> jabber <server name>" approach (the laptop didn't show up in the web
> interface). Because we couldn't qutie figure out what the name it was
> assiging to each laptop, we didn't try using the web interface to add a
> user.  That user, also, did not appear on any blocked list--as far as the
> web interface was concerned, the laptop had disappeared.
>
> In some cases, if we tried to connect to the jabber server without being
> connected properly to the internet, even after we had connected to the
> internet, that laptop couldn't be registered.
>
> Currently, we have ssh connection to the server, but not the laptops; any
> suggestions on what steps we should take next?
>
> Thanks so much for your help. I know this isn't a very technical bug
> report, but again, any advice would be appreciated. Thanks!
>
> Yifan
>
> On Fri, Apr 17, 2009 at 9:21 PM, Daniel Drake <dsd at laptop.org> wrote:
>
>> 2009/4/17 Yifan <yifan.sun at students.olin.edu>:
>> > I'm currently trying to set up the EJabberD with the server at Cambridge
>> > Friends School. I've gone through the instructions on the wiki page in
>> > configuring it, and am now trying to register some computers. Some
>> > interesting problems are coming up, and I was wondering if any of you
>> had
>> > this problem / know of a cool way to solve it.
>>
>> Which wiki page? Are you using XS? If so, which version?
>>
>> > 1) When one laptop was registered, it would show up under "users" and
>> shown
>> > as "online" with some very long hex string; subsequently, no laptop
>> could be
>> > registered. (I used "sugar-control-panel -s jabber <server name>", then
>> > restarted each time)
>>
>> You forgot to state the error or describe the error condition :)
>>
>> > 2) To test this out a bit more, we would add a user, then delete it,
>> then
>> > try to add it again. We realized that once a user was removed, it
>> couldn't
>> > be added again even when there weren't any other users. (this is all not
>> > including the admin account)
>>
>> Which procedure did you use to delete and readd users?
>> And what was the error message?
>>
>> > 3) a much more trivial problem, but when the laptop is registered, it
>> would
>> > be registered as a hex string that is very long and doesn't seem to
>> pertain
>> > to anything. What does this pertain to, and is there a way I can make it
>> > actually the name of the laptop (eg "blake 1"), etc?
>>
>> Not sure why you would want to do this - the hex strings do not appear
>> anywhere in the sugar UI, and can probably be considered an
>> implementation detail.
>>
>> Daniel
>>
>
>
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
>
>


-- 
"It is difficult to get a man to understand something, when his salary
depends upon his not understanding it." -- Upton Sinclair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20090418/7660ed77/attachment.htm