On XO-1.5 with 11.3.0/11.3.1 -- hang during shutdown?
Hi folks, the Dextrose team has been hunting a bug on XO-1.5, on their variant of 11.3.x (Dextrose 3 or DX3), and they are pointing out that it could be a latent or unreported problem in 11.3.x series. It could also be a problem in their modifications. While they continue to investigate, it is important to hear whether anyone has seen XO-1.5s handing during shutdown, on the Warnings screen. - It seems to affect some units, not all. So far it has been seen on 3 units with SN starting with SHC037 . - Units affected show the symptoms 2 out of 5 boots. - Seems to be related to umount of /home failing. Adding sync ; sleep 2; before umount seems to cure it; that's their current workaround. - Their debugging adventures are documented at http://dev.laptop.org.au/issues/1033 - They will be checking whether the symptoms follow the microSD card or the motherboard, swapping microSD with a good unit. Why is this important? When the unit hangs during shutdown, it is left in a condition where it can overheat, potentially damaging the unit. The bottom line: have you seen this issue on XO-1.5 + 11.3.x? Even if ocassionally? Let us know, and join the bug-hunting party. cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: On XO-1.5 with 11.3.0/11.3.1 -- hang during shutdown?
On Tue, Jun 5, 2012 at 10:37 AM, Martin Langhoff mar...@laptop.org wrote: - Seems to be related to umount of /home failing. Adding sync ; sleep 2; before umount seems to cure it; that's their current workaround. Cutting the CC list down to only devel@ for debugging -- Anish, thanks for reporting this. Couple of questions/requests: - can you give us the exact patch showing the workaround you are applying? - very interested in the microSD swap between good and bad units. Let us know how it goes. On 12.1.0 the switch to systemd completely reworks the shutdown / umount process; so if it affects Fedora or OLPC releases, the scope is 11.3.x / F14. Very unlikely that we see it, at least in this particular incarnation, on 12.1.0. cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [PATCH RFC powerd] Add support for inhibiting suspend via UPower
Sascha Silbe si...@activitycentral.com writes: For UPower support to actually work, you'll need some fixes to UPower. One of them has already landed in upstream git, the others are queued for review. [3] All fixes have landed in git master now and should be part of the next UPower release (alongside a fix for a bug triggered on XO-1.75, reported by Martin Langhoff). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ pgpxkxdHfWTx6.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: On XO-1.5 with 11.3.0/11.3.1 -- hang during shutdown?
On 06/06/12 02:37, Martin Langhoff wrote: The bottom line: have you seen this issue on XO-1.5 + 11.3.x? Even if ocassionally? Let us know, and join the bug-hunting party. We have seen this sort of problem in Auckland recently. However I can't really be sure if what we see is related. We test XO-1.5s, XO-1.75s, 11.3.1, olpc-au's dextrose release and 12.1.0 and I don't recall which laptops and which releases have hung. We have seen a wide variety of shutdown misbehaviour, ranging from shutdown doesn't do anything at all through to everything appears to be off except the power light is on solid. We'll do some explicit testing of shutdown on Saturday. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: On XO-1.5 with 11.3.0/11.3.1 -- hang during shutdown?
On Tue, Jun 5, 2012 at 4:43 PM, Tom Parker t...@carrott.org wrote: We'll do some explicit testing of shutdown on Saturday. Fantastic, thanks! m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] failed to register
On Tue, 2012-06-05 at 07:22 -0400, Holt wrote: On 6/4/2012 9:16 PM, Sameer Verma wrote: On Mon, Jun 4, 2012 at 6:11 PM, Jerry Vonaujvo...@shaw.ca wrote: OK, let's check if the XS has the serial numbers, what is the output of /usr/bin/xs-list-registration? If that shows as correct the XOs timed out like in ticket 11056. Can you use the register again option from the home view? If that option is not available you'll have to manually add schoolserver.providence.uwimona.edu.jm to network-control-panel's server field and you should be good to go. Jerry [sverma@schoolserver ~]$ /usr/bin/xs-list-registration Listing students from /home/idmgr/identity.db roshaun marchall SHC03801C2E userSHC03801C74 userSHC03801C78 userSHC03801C65 xo SHC03801C40 Ti-Annah Grant SHC03801C31 userSHC03801C4F xo SHC03801C33 dadrique hamilton cianna SHC03801C6B xo SHC03801C77 malikha Algeca BradnockSHC03801C32 user jahleel foster SHC03801C51 makada SHC03801C7F userSHC03801C34 shanell moss SHC03801C57 userSHC03801C18 I'm logging in remotely from San Francisco. Adam can give you the answer on the register again option cheers, Sameer XO-1.5s do not show a Register Again option, except on that 1 single machine that registered successfully back on Saturday. That single XO-1.5 registered successfully (back on Saturday) regardless whether its My Settings - Network - Server was set to schoolserver.providence.uwimona.edu.jm or was not set to anything at all. As of Monday/now however, XO-1.5s cannot similarly register, no matter if My Settings - Network - Server is set or not, even with schoolserver.providence.uwimona.edu.jm remaining pingable. Anything else I can try? Is idmgr running? Should show as running on port 8080 with netstat. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] failed to register
On 6/5/2012 7:22 AM, Holt wrote:
XO-1.5s do not show a Register Again option, except on that 1 single
machine that registered successfully back on Saturday.
That single XO-1.5 registered successfully (back on Saturday)
regardless whether its My Settings - Network - Server was set to
schoolserver.providence.uwimona.edu.jm or was not set to anything at all.
As of Monday/now however, XO-1.5s cannot similarly register, no matter
if My Settings - Network - Server is set or not, even with
schoolserver.providence.uwimona.edu.jm remaining pingable.
Anything else I can try?
Aside: all XO-1.5s are running 11.2.0, and if we can resolve this
register-then-backup dilemma, our intent is to reflash all to 11.3.1.
Jerry Vonau's not only Canajun, he also has PAPAL powers (!) exposing a
serious bug blocking Jamaica's XO-1.5s (Release 11.2.0 for now) from
registering with their XS 0.7 _unless_ live DNS is turned on.
Workaround:
1) Turn on DNS in /etc/named-xs.conf.in then run:
[root@schoolserver ~]# nano /etc/named-xs.conf.in
changing this line...
forwarders {196.2.1.2; 196.2.1.3;};
to this line...
forwarders { 192.168.1.1; };
[root@schoolserver ~]# xs-domain-config
[root@schoolserver ~]# service named restart
2) Turn off all Internet except pings for our 4- and 5- year olds, at
XS's firewall:
[root@schoolserver ~]# nano /etc/sysconfig/olpc-scripts/iptables-xs.in
# COMMENTED OUT THESE LINES BELOW, TO BLOCK KIDS FROM INTERNET
# -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
# -A FORWARD -o @@WAN@@ -j ACCEPT
[root@schoolserver ~]# xs-setup-network
[root@schoolserver ~]# service iptables restart
[root@schoolserver ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywherestate
RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywherestate NEW
tcp dpt:ssh
ACCEPT all -- anywhere anywherestate NEW
REJECT all -- anywhere anywherereject-with
icmp-host-prohibited
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywherereject-with
icmp-host-prohibited
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
3) APACHE WOULD NOT START; was misconfigured, so...
[root@schoolserver ~]# mv /etc/httpd/conf.d/munin.conf
/etc/httpd/conf.d/munin.conf.SAVE
[root@schoolserver ~]# service httpd restart
4) Jerry hasn't yet figured out why ejabberd (collaboration) isn't
working, but will try to hack thru these error msgs with me tomorrow,
when I can get back inside the school:
[root@schoolserver ~]# service moodle restart
Disabling Moodle access and cron job: [ OK ]
Enabling Moodle access and cron job: [ OK ]
[root@schoolserver ~]# service pgsql-xs restart
Stopping pgsql-xs service: [ OK ]
Starting pgsql-xs service: . [ OK ]
[root@schoolserver ~]# service ejabberd-xs restart
Shutting down ejabberd: already stopped[WARNING]
Starting ejabberd: [ OK ]
[root@schoolserver ~]# ejabberdctl registered-users `hostname -f`
*The node ejabberd@schoolserver is started with status: started
ejabberd is not running in that node
Check for error messages: /var/log/ejabberd/ejabberd.log
or other files in that directory.*
[SNIP]
[root@schoolserver ~]# cp -pr /var/lib/ejabberd/spool
/var/lib/ejabberd/spool.SAVE
[root@schoolserver ~]# rm -f /var/lib/ejabberd/spool/*
/var/lib/ejabberd/spool/.erlang.cookie
[root@schoolserver ~]# cat /etc/sysconfig/ejabberd_domain_name
providence.uwimona.edu.jm
[root@schoolserver ~]# rm -f /etc/sysconfig/ejabberd_domain_name
[root@schoolserver ~]# cat /etc/sysconfig/ejabberd_domain_name
INTENTIONALLYBOGUSprovidence.uwimona.edu.jm
[root@schoolserver ~]# service ejabberd-xs start
Starting ejabberd: /etc/sysconfig/xs_domain_name
/etc/sysconfig/ejabberd_domain_name differ: byte 1, line 1
[ OK ]
*Failed RPC connection to the node ejabberd@schoolserver: nodedown*
[SNIP]
[root@schoolserver ~]# ejabberdctl registered-users `hostname -f`
*Failed RPC connection to the node ejabberd@schoolserver: nodedown*
[SNIP]
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
