Re: [Launchpad-users] Translations import queue stopped (again)
У пон, 14. 09 2009. у 13:20 +0200, Danilo Šegan пише: I managed to come up with a work-around for the problem. Thus, I hope we'll be using slower version only when we hit the postgres bug. We should be getting a fix up on production machines later today. For anyone into technical details, please see https://bugs.launchpad.net/rosetta/+bug/408718 Imports have been re-enabled and the import script is happily churning along. It will take around a day for it to fully catch up. Cheers, Danilo -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Re: Translations import queue stopped (again)
У пет, 11. 09 2009. у 20:01 +0200, Danilo Šegan пише: On Monday, we'll roll out a slower version of the script out which excludes the query which causes postgres to misbehave, but that will mean that imports will go noticably slower. We will actively work on finding a solution to the problem after we get at least the basic imports back up and running. I managed to come up with a work-around for the problem. Thus, I hope we'll be using slower version only when we hit the postgres bug. We should be getting a fix up on production machines later today. For anyone into technical details, please see https://bugs.launchpad.net/rosetta/+bug/408718 Cheers, Danilo -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
Translations import queue stopped (again)
Hi all, Translation import queue will not be processing any entries until at least Monday evening (which is the earliest time we can get changes into Launchpad production machines). What happened? Last night a poimport script caused a problem in Launchpad database and caused overall system problems. Basically, all of Launchpad was affected. Nothing so far indicates that it is a problem with the script itself, but it seems to have pushed our postgres instance over the edge by making it eat all the disk space on database server. To preserve other services, poimport script has been stopped until we come up with adequate workaround. I know this is unfortunate and may make it impossible for you to do your work, but in order to avoid causing problems for everybody else (along with causing them for you), the script will stay disabled over the weekend. What will we do about it? On Monday, we'll roll out a slower version of the script out which excludes the query which causes postgres to misbehave, but that will mean that imports will go noticably slower. We will actively work on finding a solution to the problem after we get at least the basic imports back up and running. I thoroughly apologize for the reduced service quality. Cheers, Danilo -- ubuntu-translators mailing list ubuntu-translators@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
