Fri, Oct 11, 2013 at 10:04 AM, <tkk...@nurturingasia.com> wrote:
> Managed to install it. Nice ansible and all the goodies for server
> management
>
An install note - sometimes the first runthrough of runansible fails for
me. Not always, I think it's the vagaries of my internet and/or wifi. I
simply runansible again (and again, if needed) until it finally finishes.
> How stable is the system? I am able to load the IIAB demo files (on a USB
> stick). It will work for a while and then crash...
Just as on the XSCE, on the DXS we've noticed stability issues on low end
1.75 units. The 1.75's with 512MB of RAM, to be specific. In particular,
yes, IIAB crashes the low end 1.75 if a few (as in 3) clients try to access
IIAB content at the same time. I think folks determined it was some sort
of kernel issue. But yeah, the system freezes up, is totally unresponsive
even on the local console, and I have to do a "hard reboot" (as in walk
over to it, press down the power button till it powers off, then power back
up). I don't try to put that "crappy 1.75" up on my public URL anymore,
I've found it to be entirely too unstable. However, my testing cycles can
be very short and rather specific, thus sometimes I need to reflash a unit
several times a day. For those testing cycles confined to my LAN, I mostly
use the "crappy 1.75" because it wouldn't break my heart if it broke,
unlike these units below:
*What I have found to be very stable for XSCE and DXS*
1. The XO 1.5 (got one up right now public, uptime 9 days with the full
IIAB TB drive)
Apparently there's almost 1GB RAM
[root@schoolserver] html >free -m
total used free shared buffers cached
Mem: 936 824 112 0 60 543
2. The XO 1.75 HS with the "chicklet" keyboard
Looks like this thing has 840MB RAM?
-bash-4.2# free -m
total used free shared buffers cached
Mem: 840 418 422 0 21 146
3. The XO-4
For stability testing, I typically make the XSCE or DXS public. During
"end of cycle" testing, I try to keep the install up public at least a
week, if not longer. I have ejabberd users who always notice when my
server goes down. Not only can I see downtime in my scrollback in Pidgin
or Psi or Gajim (any chat client that handles XMPP), but my users will
literally call me on my telephone to let me know if my server is down. So
far with XSCE/DXS testing, I haven't gotten any phone calls. Again, the
only stability issue we've run into was when I tried to run the XSCE/DXS on
the "crappy" 1.75 with IIAB.
Anna
>
> >-----Original Message-----
> >From: Anna [mailto:ascho...@gmail.com]
> >Sent: Friday, October 11, 2013 08:20 AM
> >To: 'xsce-devel'
> >Cc: 'Server Devel'
> >Subject: Re: [XSCE] ansible
> >
> >Couple of postinstall notes:
> >
> >xs-authserver has some sort of conflict with the library versions that
> IIAB
> >installs. This gets xs-authserver working (don't worry, it doesn't break
> >IIAB):
> >pip install --upgrade --force-reinstall Werkzeug Flask
> >systemctl restart xs-authserver
> >
> >OLPC Backup needs a permissions fix in /etc/rssh.conf, so uncomment:
> >allowrsync
> >allowsftp
> >
> >Here's my testing checklist. Thought I'd paste this in so y'all can see
> >how similar to XSCE DXS is, and also how to access DXS specific things
> like
> >Munin, Ajenti, and xs-authserver.
> >
> > Item Access from Note dhcpd Client Client gets an IP address in the
> >172.18.x.x range dhcpd Server Check /var/lib/dhcpd/dhcpd.leases for
> >client leases idmgr Client Registration - Register the XO idmgr
> >Server Check
> >/library/users for the XO's Serial Number dir ejabberd Client 2
> >registered clients can see each other ejabberd Server `ejabberdctl
> >connected_users` reports the 2 registered clients ejabberd Clients Share
> >the chat activity and communicate httpd Client http://schoolserver and
> >http://schoolserver.local resolves to Apache test page Moodle Client
> >http://schoolserver.local/moodle autologs in Authserver Client
> >http://schoolserver.local:5000 greets with the XO buddy name Squid
> >Server Check
> >/library/cache size, load webpage on client, verify size has increased
> >Dansguardian Client Try to look at porn? No way! IIAB Client
> >http://schoolserver/iiab resolves OLPC-Backup Server du -sk
> >/library/users/* indicates backups Stats Server A client's rrds are in
> >/library/sugar-stats/rrd/ Monit Server Halt services and see if they
> >restart Munin Client http://schoolserver/munin user:admin
> pass:munindxs
> >Ajenti Client http://schoolserver:9990 user:root pass:admin Ajenti
> >Wondershaper Client Verify bandwidth edits via online speedtest such as
> >speakeasy.net/speedtest Upload Activity N/A
> /var/www/html/upload_activity.php
> >is currently not present - WIP
> >
> >
> >On Thu, Oct 10, 2013 at 2:46 PM, Anish Mangal <an...@activitycentral.com
> >wrote:
> >
> >> Documented in the githup repo here:
> >>
> >> https://github.com/activitycentral/dxs/blob/master/docs/INSTALL.rst
> >>
> >>
> >> On Thu, Oct 10, 2013 at 12:38 PM, Anna <ascho...@gmail.com> wrote:
> >>
> >>> Some quick instructions for installing the DXS. I've only tested on a
> XO
> >>> 1.75 as the target so far.
> >>>
> >>> On your target machine:
> >>> Flash 13.2.0-13
> >>> Turn off power management
> >>> Connect to internet
> >>> Get a root terminal
> >>>
> >>> Install from git source:
> >>>
> >>> wget
> >>>
> http://xsce.activitycentral.com/repos/xs-extra/noarch/ansible-1.3.1-0.git201309161027.fc18.noarch.rpm
> >>> yum -y localinstall ansible*
> >>> yum -y install git
> >>> git clone https://github.com/activitycentral/dxs.git dxs-master
> >>> cd dxs-master
> >>> git fetch -u --all
> >>> git checkout master
> >>> git pull
> >>> [plug in all your dongles]
> >>> ./runansible xo
> >>> reboot
> >>> cd dxs-master
> >>> ./runansible
> >>> reboot
> >>>
> >>> Default is hostname = schoolserver.local and a one dongle install (WAN
> =
> >>> "ears" and LAN = usb ethernet dongle to AP).
> >>> To change that, edit dxs-master/vars/default_vars.yml accordingly
> before
> >>> doing ./runansible xo:
> >>>
> >>> #Domain name
> >>> xsce_hostname : schoolserver
> >>> xsce_domain: local
> >>>
> >>> #Network
> >>> xsce_networks:
> >>> wan:
> >>> iface: eth0
> >>> ip: dhcp
> >>> lan:
> >>> iface: eth1
> >>> ip: 172.18.96.1
> >>> network: 172.18.96.0
> >>> netmask: 255.255.224.0
> >>>
> >>>
> >>> On Thu, Oct 10, 2013 at 2:18 PM, Tim Moody <t...@timmoody.com> wrote:
> >>>
> >>>> Anna, you mentioned instructions for doing an ansible install. can
> >>>> you point me to them?
> >>>>
> >>>
> >>>
> >>
> >
>
>
>
_______________________________________________
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
