From samsongoddy at gmail.com Wed Mar 13 10:09:29 2019 From: samsongoddy at gmail.com (Samson Goddy) Date: Wed, 13 Mar 2019 15:09:29 +0100 Subject: [SoaS] Collaboration Between Activities Fail Message-ID: Hi Everyone, We've been working on installing SOAS on some computers in a school and we were testing collaboration using CAT5 cables connected to a router and also connected to the two computers running the SOAS instances, the both instances are seen on the two computers but after joining an activity the "Joining activity" alert and collaboration doesn't happen. Logs here . -- Samson Goddy Twitter: https://twitter.com/samson_goddy Email: samsongoddy at sugarlabs.org samsongoddy at gmail.com Website: https://samsongoddy.me/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pbrobinson at gmail.com Wed Mar 13 12:19:13 2019 From: pbrobinson at gmail.com (Peter Robinson) Date: Wed, 13 Mar 2019 16:19:13 +0000 Subject: [SoaS] Collaboration Between Activities Fail In-Reply-To: References: Message-ID: You might want to check the local firewall ports On Wed, Mar 13, 2019 at 2:09 PM Samson Goddy wrote: > Hi Everyone, > > We've been working on installing SOAS on some computers in a school and we > were testing collaboration using CAT5 cables connected to a router > and also connected to the two computers running the SOAS instances, the > both instances are seen on the two computers but after joining an activity > the "Joining activity" alert and collaboration doesn't happen. > > Logs here . > > -- > > Samson Goddy > > Twitter: https://twitter.com/samson_goddy > Email: samsongoddy at sugarlabs.org > samsongoddy at gmail.com > > Website: https://samsongoddy.me/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aperez at alexperez.com Wed Mar 13 13:53:30 2019 From: aperez at alexperez.com (Alex Perez) Date: Wed, 13 Mar 2019 10:53:30 -0700 Subject: [SoaS] [Sugar-devel] Collaboration Between Activities Fail with Fedora 29 SoaS In-Reply-To: <599470b0-f27c-4e25-3a90-b04dc777e6c9@alexperez.com> References: <599470b0-f27c-4e25-3a90-b04dc777e6c9@alexperez.com> Message-ID: <3ffef1d5-2669-7888-9544-3905e16c6169@alexperez.com> Samson, Based on my previous conversations with you, you had indicated you were using Fedora 29 32-bit SoaS. Please confirm that this is still the case. I have changed the subject line to reflect this. I believe you are encountering the issue which we thought we had fixed with a previous patch (see https://github.com/sugarlabs/sugar/issues/814 ). This patch is now upstream in F29, but _only_ if you use the updated 32-bit SoaS image, which is not yet generally available. Even with the fix in place, collaboration still fails with the same message. After starting Sugar, open the Terminal, and type 'grep key ~/.sugar/default/logs/shell.log' If you see a message which says "ERROR root: Error parsing public key" then you are running into a bug that has been present in the last several versions of Fedora, and completely breaks collaboration. The underlying problem is still not fully understood, however we know it's related to SSH keys. Additionally, for collaboration to function, you must also make sure that your Ethernet interfaces have IP addresses (self-assigned is fine), and that there is a default route set on each computer that is attempting to collaborate. You can check this from the terminal with "ip route", and if there is no line that starts with "default" or no output at all, then there is no default route set, and collaboration will not work. Here is an example of the output of shell.log which shows the error: http://alexperez.com/xo1/VirtualBox_Fedora29-soas-shell.log.png > > Samson Goddy wrote on 3/13/19 7:09 AM: >> Hi Everyone, >> >> We've been working on installing SOAS on some computers in a school >> and we were testing collaboration using CAT5 cables connected to a router >> and also connected to the two computers running the SOAS instances, >> the both instances are seen on the two computers but after joining an >> activity >> the "Joining activity" alert and collaboration doesn't happen. >> >> Logs here . >> >> -- >> >> Samson Goddy >> >> Twitter: https://twitter.com/samson_goddy >> Email: samsongoddy at sugarlabs.org >> samsongoddy at gmail.com >> >> Website: https://samsongoddy.me/ >> >> >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel at lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Sent from Postbox > -- Sent from Postbox -------------- next part -------------- An HTML attachment was scrubbed... URL: From samsongoddy at gmail.com Wed Mar 13 18:29:09 2019 From: samsongoddy at gmail.com (Samson Goddy) Date: Wed, 13 Mar 2019 23:29:09 +0100 Subject: [SoaS] [Sugar-devel] Collaboration Between Activities Fail with Fedora 29 SoaS In-Reply-To: <599470b0-f27c-4e25-3a90-b04dc777e6c9@alexperez.com> References: <599470b0-f27c-4e25-3a90-b04dc777e6c9@alexperez.com> Message-ID: On Wed, Mar 13, 2019, 6:30 PM Alex Perez wrote: > Samson, > > Based on my previous conversations with you, you had indicated you were > using Fedora 29 32-bit SoaS. Please confirm that this is still the case. I > have changed the subject line to reflect this. > Yes, I am using 29 32-bit SoaS. > > I believe you are encountering the issue which we thought we had fixed > with a previous patch (see https://github.com/sugarlabs/sugar/issues/814 > ). This patch is now upstream in F29, but _only_ if you use the updated > 32-bit SoaS image, which is not yet generally available. Even with the fix > in place, collaboration still fails with the same message. > > After starting Sugar, open the Terminal, and type 'grep key > ~/.sugar/default/logs/shell.log' If you see a message which says "ERROR > root: Error parsing public key" then you are running into a bug that has > been present in the last several versions of Fedora, and completely breaks > collaboration. The underlying problem is still not fully understood, > however we know it's related to SSH keys. > > Additionally, for collaboration to function, you must also make sure that > your Ethernet interfaces have IP addresses (self-assigned is fine), and > that there is a default route set on each computer that is attempting to > collaborate. You can check this from the terminal with "ip route", and if > there is no line that starts with "default" or no output at all, then there > is no default route set, and collaboration will not work. > > Here is an example of the output of shell.log which shows the error: > http://alexperez.com/xo1/VirtualBox_Fedora29-soas-shell.log.png > Thanks Alex, I will be giving an update by Wednesday. As soon as I get my hands on the computers again. Regards > > > Samson Goddy wrote on 3/13/19 7:09 AM: > > Hi Everyone, > > We've been working on installing SOAS on some computers in a school and we > were testing collaboration using CAT5 cables connected to a router > and also connected to the two computers running the SOAS instances, the > both instances are seen on the two computers but after joining an activity > the "Joining activity" alert and collaboration doesn't happen. > > Logs here . > > -- > > Samson Goddy > > Twitter: https://twitter.com/samson_goddy > Email: samsongoddy at sugarlabs.org > samsongoddy at gmail.com > > Website: https://samsongoddy.me/ > > _______________________________________________ > Sugar-devel mailing listSugar-devel at lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > Sent from Postbox > > -------------- next part -------------- An HTML attachment was scrubbed... URL: