[Server-devel] Fwd: Hoping for assistance with XS 0.5 configuration difficulties (ejabberd)
I just sent this to Reuben. I have done some digging through the log file
and haven't seen anything useful. Do I perhaps need to set the ejabberd.cfg
file to 5:debug instead of 4:Verbose? i remember seeing something about
that inside it.
Unfortunately, we we haven't set up a GUI, web browser, or emailing
capabilities of any kind on the server itself so emailing the log file will
be a roadblock for me. I haven't worked in linux for about 5 years now
until trying to tackle this project. I'm relearning how to do basic things
like ls, pipe to less, and use vi for simple text edits. Setting that stuff
up is likely to take a lng time. Is there anything specific I can do
offline to find what you're hoping for inside. In writing you this email I
just recalled the existence of grep. is there something I could grep for in
the log file and give you some feedback on it?
On the subject of following instructions, there have been two of us working
on the server, sometimes one at a time so I can't guarantee that we've
followed them to a T, but we both believe that we have. We've gone so far
as to rerun the initial scripts, recheck hostname, reset the acl lines in
ejabberd.cfg repeatedly, connect to the jabber server with 2 different
jabber clients (which has been successful, we've chatted back and forth
using our server. We just can't access the admin inteface at
http://192.168.0.162:5280/admin, we keep getting 401 unauthorized), read
every wiki page that sounded remotely relevant, etc.
And we've been following hunches at each step so we have pulled some of the
instructions out of related pages from the wiki.
I've been careful to comment out all of the original lines in the
ejabberd.cfg file and mark all of my changes for easy resetting of each
segment to it's original state. Which I've since done. So theoretically,
the file should be in it's original state except for the {acl, admin {...
line that we added to give admin privs to our sample user.
But of course, I could have made missed something. However, the server is
still working fine when we connect via 3rd party clients (pidgin pis), so I
don't think I've done anything critical...
Let me know if I should grep anything out of the log file for you.
Thanks for the help!
-Dan
-- Forwarded message --
From: Daniel Bennett dant...@gmail.com
Date: Sat, Apr 25, 2009 at 5:57 PM
Subject: Re: [Server-devel] Hoping for assistance with XS 0.5 configuration
difficulties (ejabberd)
To: Reuben K. Caron reu...@laptop.org
Cc: Michael Ishaku michaelish...@gmail.com
Reuben,
Thank you for the quick reply and the hints. I've cc'd Michael Ishaku on
this thread. He's and I have been working on this issue together and he is
going to be administering the server once I head back to the states.
I've replied to your statements inline below to the best of my ability.
Please take a look.
On Sat, Apr 25, 2009 at 5:19 PM, Reuben K. Caron reu...@laptop.org wrote:
Daniel,
I am sorry to hear about all your difficulties. I'd like to work with you
to get this to work.
If you cannot enter the ejabberd web interface to setup the online group
then XOs will not collaborate.
I'd like to know about your hardware, 2 nics or 1?
We have one LAN card for ethernet, but have also installed a wireless
networking card for communication with Access Points. That should work,
right? I'm really no IT professional... :)
I'm sure you have read through this but please be sure to follow this line
by line:
http://wiki.laptop.org/go/XS_Installing_Software#Initial_Configuration
One particular point I'd like to make in the instructions is this:
---Set the hostname of the machine like this (until we fix bug 8983) by
editing /etc/sysconfig/network to set HOSTNAME=schoolserver.example.org
contents of /etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=schoolserver.lccnyola.org
~
~
/etc/sysconfig/network 2L, 50C
--and restarting.
We had this problem yesterday when we left, and when i arrived this morning
I had to turn the server back on (it had powered off overnight due to the
generator being shut down and the UPS running out of juice). I'm fairly
certain that we tried rebooting a couple of times during the day yesterday
as well. I'm certain that we used the command shell to: service ejabberd
restart many many times both days. This would cover the restarting,
right?
It is important to restart before moving on; otherwise, the ejabberd db
will be intialized using the wrong domain.
Is the bandwidth too limited to download the new 0.5.2 ISO? If yes, I'd
recommend a fresh install, connect to internet, and then after install run:
yum update. After an up to date install run through the setup steps.
I left the states on 3/23/09. I believe that 0.5.2 was released on 3/18/09.
This is the file name for the image I brought with me (and that we are
currently running: OLPC-School-Server-0.5.2-i386.iso
we could probably download a fresh image with 12/24
Re: [Server-devel] Fwd: Hoping for assistance with XS 0.5 configuration difficulties (ejabberd)
Daniel Bennett wrote:
I just sent this to Reuben. I have done some digging through the log
file and haven't seen anything useful. Do I perhaps need to set the
ejabberd.cfg file to 5:debug instead of 4:Verbose? i remember seeing
something about that inside it.
Unfortunately, we we haven't set up a GUI, web browser, or emailing
capabilities of any kind on the server itself so emailing the log file
will be a roadblock for me. I haven't worked in linux for about 5
years now until trying to tackle this project. I'm relearning how to
do basic things like ls, pipe to less, and use vi for simple text
edits. Setting that stuff up is likely to take a lng time. Is
there anything specific I can do offline to find what you're hoping
for inside. In writing you this email I just recalled the existence
of grep. is there something I could grep for in the log file and give
you some feedback on it?
On the subject of following instructions, there have been two of us
working on the server, sometimes one at a time so I can't
guarantee that we've followed them to a T, but we both believe that we
have. We've gone so far as to rerun the initial scripts, recheck
hostname, reset the acl lines in ejabberd.cfg repeatedly, connect to
the jabber server with 2 different jabber clients (which has been
successful, we've chatted back and forth using our server.
We just can't access the admin inteface at
http://192.168.0.162:5280/admin, we keep getting 401 unauthorized),
read every wiki page that sounded remotely relevant, etc.
Where is this IP coming from? How are you changing this?
Martin, also note (below) they have one nic.. Can you remind us what the
default behavior is for one nic?
And we've been following hunches at each step so we have pulled some
of the instructions out of related pages from the wiki.
I've been careful to comment out all of the original lines in the
ejabberd.cfg file and mark all of my changes for easy resetting of
each segment to it's original state. Which I've since done. So
theoretically, the file should be in it's original state except for
the {acl, admin {... line that we added to give admin privs to our
sample user.
But of course, I could have made missed something. However, the
server is still working fine when we connect via 3rd party clients
(pidgin pis), so I don't think I've done anything critical...
Let me know if I should grep anything out of the log file for you.
Thanks for the help!
-Dan
-- Forwarded message --
From: *Daniel Bennett* dant...@gmail.com mailto:dant...@gmail.com
Date: Sat, Apr 25, 2009 at 5:57 PM
Subject: Re: [Server-devel] Hoping for assistance with XS 0.5
configuration difficulties (ejabberd)
To: Reuben K. Caron reu...@laptop.org mailto:reu...@laptop.org
Cc: Michael Ishaku michaelish...@gmail.com
mailto:michaelish...@gmail.com
Reuben,
Thank you for the quick reply and the hints. I've cc'd Michael Ishaku
on this thread. He's and I have been working on this issue together
and he is going to be administering the server once I head back to the
states.
I've replied to your statements inline below to the best of my
ability. Please take a look.
On Sat, Apr 25, 2009 at 5:19 PM, Reuben K. Caron
reu...@laptop.org mailto:reu...@laptop.org wrote:
Daniel,
I am sorry to hear about all your difficulties. I'd like to work
with you to get this to work.
If you cannot enter the ejabberd web interface to setup the online
group then XOs will not collaborate.
I'd like to know about your hardware, 2 nics or 1?
We have one LAN card for ethernet, but have also installed a wireless
networking card for communication with Access Points. That should
work, right? I'm really no IT professional... :)
I'm sure you have read through this but please be sure to follow
this line by line:
http://wiki.laptop.org/go/XS_Installing_Software#Initial_Configuration
One particular point I'd like to make in the instructions is this:
---Set the hostname of the machine like this (until we fix bug
8983) by editing /etc/sysconfig/network to set
HOSTNAME=schoolserver.example.org http://schoolserver.example.org
contents of /etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=schoolserver.lccnyola.org http://schoolserver.lccnyola.org
~
~
/etc/sysconfig/network 2L, 50C
--and restarting.
We had this problem yesterday when we left, and when i arrived this
morning I had to turn the server back on (it had powered off overnight
due to the generator being shut down and the UPS running out of
juice). I'm fairly certain that we tried rebooting a couple of times
during the day yesterday as well. I'm certain that we used the
command shell to: service ejabberd restart many many times both
days. This would cover the restarting, right?
It is important to restart before moving on; otherwise, the
ejabberd db will be intialized using the
Re: [Server-devel] Fwd: Hoping for assistance with XS 0.5 configuration difficulties (ejabberd)
On Sat, Apr 25, 2009 at 7:23 PM, Reuben K. Caron reu...@laptop.org wrote: We just can't access the admin inteface at http://192.168.0.162:5280/admin, we keep getting 401 unauthorized), read every wiki page that sounded remotely relevant, etc. Where is this IP coming from? How are you changing this? Good point! Daniel, please, start from the beginning reinstalling the server from the start, and follow my guide. NO OTHER GUIDE. Also -- skip the optional bits. Stick to the core guide. Martin, also note (below) they have one nic.. Can you remind us what the default behavior is for one nic? A single NIC will defaiult to being the WAN NIC (on the assumption that AAs will be connected). So use xs-swapnics to turn the single NIC into a LAN port. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
