<div dir="ltr">Hello all,<div><br></div><div>The instance is back, I had to made a few changes:</div><div><ol><li>added ".conf" extension to the site configuration file<br></li><li>temporarily removed caching directives, I still need to figure what can be use to replace them.<br>
</li><li>changed some permissions [1].<br></li></ol></div><div><br></div><div>@matthew can you re-check the configuration file? I am not expert in apache so my fixes could be more like hacks.</div><div><br></div><div>Next step is trying to upgrade pootle version...</div>
<div><br></div><div>Refs:</div><div>1. <a href="http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/">http://dabase.com/blog/AH01630:_client_denied_by_server_configuration/</a>  </div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 28, 2014 at 9:41 PM, Matthew Ciao <span dir="ltr"><<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Done! <div><br></div><div>Sent it from my private email bashintosh at gmail dot com</div><div><div class="h5"><div><div class="gmail_extra"><br><div class="gmail_quote">On 29 July 2014 10:43, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">By the way, you don't even have a shell account yet:<br>
<br>
  <a href="http://wiki.sugarlabs.org/go/Service/shell" target="_blank">http://wiki.sugarlabs.org/go/Service/shell</a><br>
<br>
Please apply now, you can use me as your sponsor.<br>
<div><br>
On 07/28/2014 07:52 PM, Matthew Ciao wrote:<br>
> As a quick suggestion, if you haven't done it already I recommend to<br>
> start debugging by looking at the Apache logs (/var/log/apache2 on most<br>
> Debian-based systems).<br>
><br>
> A general health-check on Apache itself could also include:<br>
><br>
</div>>   * verify the server is running (process)<br>
>   * verify the server is listening on the desired ports (netstat, lsof)<br>
>   * check firewall rules (iptables being a good place to start)<br>
>   * inspect vhosts configurations<br>
<div>><br>
> Lemme know if you need any help Martin,<br>
><br>
</div>> /Matthew/<br>
<div>><br>
><br>
> On 29 July 2014 01:27, Martin Abente <<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a><br>
</div><div>> <mailto:<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a>>> wrote:<br>
><br>
>     Ok!<br>
><br>
><br>
>     On Mon, Jul 28, 2014 at 11:25 AM, Bernie Innocenti<br>
</div><div>>     <<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>>> wrote:<br>
><br>
>         Yes, I did it yesterday. The machine boots, but the apache<br>
>         virtual host<br>
>         doesn't seem to work any more.<br>
><br>
>         I'll leave the rest to you!<br>
><br>
><br>
>         On 07/28/2014 10:53 AM, Martin Abente wrote:<br>
>         > Hey Bernie!<br>
>         ><br>
>         > Did you get the time to update the machine?<br>
>         ><br>
>         ><br>
>         > On Thu, Jul 24, 2014 at 7:56 PM, Matthew Ciao<br>
>         <<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a> <mailto:<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a>><br>
</div>>         > <mailto:<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a> <mailto:<a href="mailto:matthew@laptop.org.au" target="_blank">matthew@laptop.org.au</a>>>><br>

<div>>         wrote:<br>
>         ><br>
>         >     Guys please let me know if there's anything I can do to help!<br>
>         ><br>
>         ><br>
>         >     On 25 July 2014 04:01, Martin Abente<br>
>         <<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a><br>
>         <mailto:<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a>><br>
</div>>         >     <mailto:<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a><br>
<div><div>>         <mailto:<a href="mailto:martin.abente.lahaye@gmail.com" target="_blank">martin.abente.lahaye@gmail.com</a>>>> wrote:<br>
>         ><br>
>         >         Hey Bernie!<br>
>         ><br>
>         >         I (literally) just finished my first round of tests<br>
>         setting up a<br>
>         >         pootle 2.5.1.1 instance from scratch. The results are<br>
>         promising:<br>
>         ><br>
>         >          1. Setting up a pootle instance from scratch was very<br>
>         >             straightforward.<br>
>         >          2. Creating a new project and integrating it with git<br>
>         >             versioning was also surprisingly straightforward.<br>
>         In fact,<br>
>         >             no custom bits were require to make pootle import<br>
>         Sugar<br>
>         >             project and start making commits to the remote<br>
>         repository.<br>
>         ><br>
>         >         Other premature comments:<br>
>         ><br>
>         >           * pootle imported _almost_ all the languages, but I<br>
>         had to<br>
>         >             manually add languages like "guarani". I still<br>
>         don't know<br>
>         >             why, ideas?<br>
>         >           * I still need to check the SL wiki to have some<br>
>         ideas of how<br>
>         >             it would be better to organize the projects. IIRC, our<br>
>         >             previous pootle instance followed the same sugar<br>
>         modules<br>
>         >             like sucrose, fructose, etc. Suggestions?<br>
>         ><br>
>         ><br>
>         >         I don't think I will have the time to work on this<br>
>         during the<br>
>         >         weeking (because of the wedding), but if you could<br>
>         make sure the<br>
>         >         server is ready, I can continue over the week.<br>
>         ><br>
>         ><br>
>         >     Bernie if you don't have time to work on what Martin needs<br>
>         I can<br>
>         >     step in, no problems at all.<br>
>         ><br>
>         >     Cheers!<br>
>         ><br>
>         ><br>
>         ><br>
>         ><br>
>         >         On Thu, Jul 24, 2014 at 1:03 PM, Bernie Innocenti<br>
>         >         <<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>><br>
</div></div><div><div>>         <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>>>> wrote:<br>


>         ><br>
>         >             Martin is taking Pootle, but if you have time to<br>
>         help with<br>
>         >             it, I think<br>
>         >             it would be appreciated.<br>
>         ><br>
>         >             I think I'll start the work on Sunday. Martin,<br>
>         would you<br>
>         >             have time?<br>
>         ><br>
>         ><br>
>         >             On 07/21/2014 07:08 AM, Matthew Ciao wrote:<br>
>         >             > Hi folks,<br>
>         >             ><br>
>         >             > it looks like you're already in a good position<br>
>         in terms<br>
>         >             of help from<br>
>         >             > rgs and/or icarito so I don't think I would be<br>
>         very useful<br>
>         >             at the meeting.<br>
>         >             ><br>
>         >             > This said, if all goes bad please involve me in<br>
>         the Pootle<br>
>         >             mission as I<br>
>         >             > am more than keen to lend a hand! :)<br>
>         >             ><br>
>         >             > Best,<br>
>         >             ><br>
>         >             > Matthew<br>
>         >             ><br>
>         >             > On Jul 21, 2014 4:15 AM, "Bernie Innocenti"<br>
>         >             <<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>><br>
>         <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>>><br>
>         >             > <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a><br>
>         <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>> <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a><br>
>         <mailto:<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>>>>><br>
>         >             wrote:<br>
>         >             ><br>
>         >             >     +rgs, +icarito (both of which expressed<br>
>         interest in<br>
>         >             supporting Pootle)<br>
>         >             ><br>
>         >             ><br>
>         >             >     On 07/20/2014 01:36 PM, Martin Abente wrote:<br>
>         >             >     > Hello everyone,<br>
>         >             >     ><br>
>         >             >     > What about investing some minutes this<br>
>         week to talk<br>
>         >             about Pootle's<br>
>         >             >     > status, what is missing and how can we get<br>
>         it back<br>
>         >             to life?<br>
>         >             >     ><br>
>         >             >     > I suggest this Wednesday 23 July, 13:00 UTC.<br>
>         >             ><br>
>         >             >     It's a bit early for me, and definitely too<br>
>         early for rgs.<br>
>         >             >     Can we do 15:00 UTC?<br>
>         >             ><br>
>         >             ><br>
>         >             >     In case I miss the meeting, here's a full<br>
>         dump of my mind:<br>
>         >             ><br>
>         >             >      - you, rgs and icarito already have root to<br>
>         >             <a href="http://newpootle.sugarlabs.org" target="_blank">newpootle.sugarlabs.org</a><br>
>         <<a href="http://newpootle.sugarlabs.org" target="_blank">http://newpootle.sugarlabs.org</a>> <<a href="http://newpootle.sugarlabs.org" target="_blank">http://newpootle.sugarlabs.org</a>><br>
>         >             >     <<a href="http://newpootle.sugarlabs.org" target="_blank">http://newpootle.sugarlabs.org</a>><br>
>         >             ><br>
>         >             >      - full backups of the old pootle machine are on<br>
>         >             freedom, and all of you<br>
>         >             >     have root access there too<br>
>         >             ><br>
>         >             >      - Sysadmin documentation is in the usual<br>
>         place (the<br>
>         >             wiki). There are<br>
>         >             >     several pages written by the previous Pootle<br>
>         maintainers:<br>
>         >             ><br>
>         >             >       <a href="http://wiki.sugarlabs.org/go/Service/translate" target="_blank">http://wiki.sugarlabs.org/go/Service/translate</a><br>
>         >             >       <a href="http://wiki.sugarlabs.org/go/Service/Pootle" target="_blank">http://wiki.sugarlabs.org/go/Service/Pootle</a><br>
>         >             >       <a href="http://wiki.sugarlabs.org/go/Service/Pootle2.5" target="_blank">http://wiki.sugarlabs.org/go/Service/Pootle2.5</a><br>
>         >             >       <a href="http://wiki.sugarlabs.org/go/Machine/pootle" target="_blank">http://wiki.sugarlabs.org/go/Machine/pootle</a><br>
>         >             ><br>
>         >             >      The documentation needs to be consolidated<br>
>         into a<br>
>         >             single page and<br>
>         >             >     updated. *PLEASE*, don't neglect this step;<br>
>         it will<br>
>         >             save a lot of time<br>
>         >             >     to future maintainers.<br>
>         >             ><br>
>         >             >      - The newpootle machine is still running<br>
>         Ubuntu 12.04<br>
>         >             LTS. I strongly<br>
>         >             >     recommend upgrading it to 14.04 (trusty) before<br>
>         >             proceeding. It won't<br>
>         >             >     take more than 1h of work and I can do this.<br>
>         >             ><br>
>         >             >      - There's an outdated instance of Pootle<br>
>         already<br>
>         >             running on newpootle.<br>
>         >             >     It was setup by a previous volunteer, but never<br>
>         >             transitioned into<br>
>         >             >     production due to difficulties with the git<br>
>         >             integration (iirc, cjl might<br>
>         >             >     have more on this).<br>
>         >             ><br>
>         >             >      - I strongly recommend upgrading to the latest<br>
>         >             release of Pootle before<br>
>         >             >     doing anything else.<br>
>         >             ><br>
>         >             >      - Then, the database and data from the<br>
>         backups needs<br>
>         >             to be restored and<br>
>         >             >     probably converted to the Pootle 2.5 format<br>
>         (good luck<br>
>         >             with Django db<br>
>         >             >     migration!)<br>
>         >             ><br>
>         >             >      - Finally, the part where all past<br>
>         maintainers seem<br>
>         >             to get stuck: make<br>
>         >             >     the Pootle <-> git integration work. I don't<br>
>         know what<br>
>         >             the actual<br>
>         >             >     problem is; pushing to git should be a basic<br>
>         feature<br>
>         >             of a translation<br>
>         >             >     system and I'm surprised this can't be made<br>
>         to work<br>
>         >             out of the box.<br>
>         >             ><br>
>         >             >      - When everything works (and please test it<br>
>         well,<br>
>         >             Pootle likes to crash<br>
>         >             >     and burn under load), we can change the DNS<br>
>         to point<br>
>         >             the CNAME<br>
>         >             >     <a href="http://translate.sugarlabs.org" target="_blank">translate.sugarlabs.org</a><br>
>         <<a href="http://translate.sugarlabs.org" target="_blank">http://translate.sugarlabs.org</a>><br>
>         >             <<a href="http://translate.sugarlabs.org" target="_blank">http://translate.sugarlabs.org</a>><br>
>         >             <<a href="http://translate.sugarlabs.org" target="_blank">http://translate.sugarlabs.org</a>> to<br>
>         >             >     newpootle. Follow the Service/nameserver<br>
>         >             >     documentation page to do this, or I can do<br>
>         it in 2<br>
>         >             minutes.<br>
>         >             ><br>
>         >             >     --<br>
>         >             >      _ // Bernie Innocenti<br>
>         >             >      \X/  <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
>         >             ><br>
>         ><br>
>         ><br>
>         >             --<br>
>         >              _ // Bernie Innocenti<br>
>         >              \X/  <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
>         ><br>
>         ><br>
>         ><br>
>         ><br>
><br>
><br>
>         --<br>
>          _ // Bernie Innocenti<br>
>          \X/  <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
><br>
><br>
><br>
<br>
<br>
--<br>
 _ // Bernie Innocenti<br>
 \X/  <a href="http://codewiz.org" target="_blank">http://codewiz.org</a><br>
</div></div></blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div>