Hi Rueben,

 

Hope you had a nice time over Christmas and new Year! Sorry to bring this
down to earth again...but life goes on.. J 

 

I have reinstalled a fresh install. On starting, the server now shows

OLPC School Server release 9-0.5

Kernel 2.6.27.7-53.fc9.i686 on an i686 (tty1)

 

Everything done exactly as below. The XS has been configured and Online
roster created, server restarted. eJabberd running. The XOs have been
de-registered and rebooted, and then registered, and rebooted. This is what
happens when they have started up: 

 

(1)    All four XOs are connected

(2)    All have been registered - i.e. it told me "registration successful"

(3)    olpc-netstatus shows that all are running Telepathy type gabble, but
the numbers of XOs shown varies from 3 to 5 on the XOs and the corresponding
incomplete population on the neighbourhood screen. The school server is
correctly shown, and config is shown as "school mesh" on all four. 

(4)    Check - ejabberd running OK

(5)    After a period of 30 mins, no change. I shut down 3 XOs and check Web
admin - it shows all four XOs registered. 

(6)    I reboot everything inc server. After allowing a few minutes, I
check: ejabberd is running, all four XOs are connected, olpc-netstatus shows
them all running Telepathy gabble, school mesh, but XO = 2 (i.e. server and
XO). Neighbourhood screen remains unpopulated, even after 10 minutes. 

(7)    Video chat starts up OK but you don't see any other XOs initially.
However, after 5 minutes some of the other XOs do start to appear on Video
Chat - even though they are not shown in the network view, and it is not
reliable or symmetric - i.e. XO-1 might see XO-2 but not vice versa. This
might be an important clue or symptom of what is happening

 

 

The work around is as before:

(1)    Shut down all but one XO, log on to ejabberd Web Admin and delete all
users, reboot everything.

(2)    Start everything up and it works fine (as you can see on Youtube),
but only for that session - I have to do this procedure each time to get it
working.. and even then you can't be sure of 100% collaboration between the
four XOs

 

The identical equipment all works fine with XS-0.4

 

David Leeming

Technical Advisor, People First Network, Honiara, Solomon Islands

Alternative email address: leemingda...@yahoo.com.au 

 

 

From: Reuben Caron [mailto:caron.reu...@gmail.com] On Behalf Of Reuben K.
Caron
Sent: Wednesday, 31 December 2008 3:30 a.m.
To: David Leeming
Cc: 'XS Devel'; 'Martin Langhoff'
Subject: Re: [Server-devel] XS 0.5.1-dev03 with ejabberd goodness, kernel
bling, Access Point workingness... looking for xmas testers

 

David,

Thank you for the information.

Can you attempt to perform a clean install again with edits in line below.

David Leeming wrote: 

Hi Reuben
 
 
 
-          Installed 0.5 Nov 19th download on Toshiba notebook computer with
black box prototype AA (USB)
 
-          Fresh install (overwriting not upgrading the previously fully
working 0.4 installation
 
-          Set location Guadalcanal, use local time
  

(I did not change this in my tests; I doubt this has any effect but want to
note I left this at the default setting)



 
-          No optional application selected
 
-          Install...... restart
 
-          /etc/sysconfig/olpc-scripts/domain_config oceania.org
  

After running domain_config

Then edit the file /etc/sysconfig/network and set hostname to
schoolserver.oceania.org (nano /etc/sysconfig/network)

Then restart (shutdown -r now)




 
-          chkconfig --level 345 ejabberd on
 
-          service ejabberd start
 
  

Wait a few minutes for ejabberd to completely startup. You can check it's
status by running: service ejabberd status



-          ejabberdctl register admin schoolserver.oceania.org admin 
 
  


With a fresh install of 0.5.1 dev 3 you don't need the following from here
-->

-          restart
 
-          yum --enablerepo=olpcxs-testing update
 
-          restart
 
  

to here <--



-          One one of 4 XOs, log onto ejabberd web admin and set up shared
roster "Online"
 
-          restart
 
-          start all four XOs and register, then restart
 
 
  

On the XOs are registering from a fresh OS install, 8.2? If the XOs have
been previously registered; you will need to clean out their registration by
removing the server fields in /home/olpc/.sugar/default/config. 

After removing these fields; restart the XOs
Then connect the XOs to the appropriate SSID or AA.
Then register the XO.
Then restart the XO.

I hope this helps. Please let us know.



 
At this stage I cannot see any other XO, and still had to do the work around
of removing all four users from the ejabberd webadmin and restarting
everything before I could see them in the neighbourhood views.  (as advised
by Martin):
 
 
 
(Martin wrote...) To avoid re-installing the XS to re-test the "just
registered" scenario you can
 
 - go with a webbrowser to the ejabberd admin panel, go into the
'schoolserver' vhost listed there and delete all the users registered
 
 - restart ejabberd
 
 - restart the laptops
 
 
 
This happens each time a laptop is restarted. 
 
 
 
However, once all going, it is fine: 
 
- All four show up in the eJabberd control panel as users
 
- All have the same correct results for olpc-netstatus 
 
- I tried sharing Memorize - all four OK
 
- Video chat is OK between any two
 
- Server access and Internet browsing all OK (updated them each online)
 
 
 
 
 
Log attached
 
 
 
 
 
 
 
 
 
David Leeming
 
Technical Advisor, People First Network, Honiara, Solomon Islands
 
Alternative email address: leemingda...@yahoo.com.au 
 
 
 
 
 
From: Reuben Caron [mailto:caron.reu...@gmail.com] On Behalf Of Reuben K.
Caron
Sent: Tuesday, 30 December 2008 12:15 p.m.
To: David Leeming
Cc: XS Devel; Martin Langhoff
Subject: Re: [Server-devel] XS 0.5.1-dev03 with ejabberd goodness, kernel
bling, Access Point workingness... looking for xmas testers
 
 
 
Hmm..
 
Are you upgrading or doing this from fresh install? 
 
If upgrade from what previous version?
 
If from fresh install can you give more detail to the exact steps you are
performing?
 
(pardon me if you provided this information earlier; I quickly reviewed the
archive and could not find anything)
 
Reuben
 
 
Martin Langhoff wrote: 
 
On Mon, Dec 29, 2008 at 10:04 PM, David Leeming
  <mailto:leem...@pipolfastaem.gov.sb> <mailto:leem...@pipolfastaem.gov.sb>
<mailto:leem...@pipolfastaem.gov.sb> <leem...@pipolfastaem.gov.sb> wrote:
  
 
It works but you have to run through the procedure below each time you start
the XOs up with the server.
    
 
 
Hmmm, well, that's definitely not normal procedure!
 
  
 
- I have to log onto ejabberd web admin with all XOs turned off and delete
all users (time consuming for a class of 40....) and then start them up.
Then it will work fine and the neighbourhood screens populate, until you
want to start again. Next time you start everything up, you will not see the
other XOs, until the procedure is repeated.
    
 
 
I suspect there's something else happening there... on the server
there should be a log for ejabberd, /var/log/ejabberd.log I think. Can
you post it to the list or to me? That should give us something to
chew on...
 
cheers,
 
 
m
  
 
 
 
 
  

 

-- 
Reuben K. Caron
Country Support Engineer
One Laptop per Child
Mobile: +1-617-230-3893
reu...@laptop.org
Deployments Support <http://wiki.laptop.org/go/Deployments_Support>  

_______________________________________________
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Reply via email to