I nearly finished this before noticing there's INI file that had the memory limit set to 256MB. I've increased this to 512. Let's see if that helps first.

@ifried I asked Leon to go ahead and start on this because it was becoming really problematic and nearly unusable.

@MusikAnimal Good catch. Maybe that will help.

Note that wsexport did used to be on its own VPS, at wsexport.wmflabs.org. I can't find anything about why it was moved. I guess it was just easier to maintain (and maybe some required packages became available on toolforge?).

Oh yes, and we also have https://tools.wmflabs.org/wsexport-test/ — not sure if we want to migrate that as well?

Note that wsexport did used to be on its own VPS, at wsexport.wmflabs.org. I can't find anything about why it was moved. I guess it was just easier to maintain (and maybe some required packages became available on toolforge?).

ToolsForge was not available yet when Wsexport has been created. @coren and I moved it to ToolsForge to ease maintenance.

Increasing the memory limit on Toolforge apparently didn't do the trick.

Agreed. The downtime emails are pretty much back to their original state.

I'm still not convinced there isn't something programmatically wrong but I cannot figure out what that might be.

You will improve the uptime, sure. Follow instructions in Cloud-VPS (Project-requests) (example of task is T237222: Request creation of srwiki-dev VPS project.

Okay, VPS is up and running https://wsexport.wmflabs.org/, and https://tools.wmflabs.org/wsexport is being redirected there. Documentation for the instance is at https://wikitech.wikimedia.org/wiki/Tool:CommTech#Wikisource_Export. UptimeRobot is now monitoring the new location.

I do see some requests are getting 500s (example), but from my testing the Toolforge installation had the same problem. It looks like exporting to the mobi format is broken? I'll ignore this for now.

Let's see how she flies!

@MusikAnimal Thank you!

Two (maybe dumb) questions:

1. Why installing PHP 7.2 and not PHP 7.3 that is provided by Buster?
2. It would be maybe nice to install the calibre version from Buster backport that contains some improvements from the newer versions of Calibre.

In T242760#5847713, @Tpt wrote:

@MusikAnimal Thank you!

Two (maybe dumb) questions:

1. Why installing PHP 7.2 and not PHP 7.3 that is provided by Buster?
2. It would be maybe nice to install the calibre version from Buster backport that contains some improvements from the newer versions of Calibre.

Good question! I guess I didn't pay much mind to what came with Buster. I just installed everything like we did for our other VPS instances.

We don't have enough quota right now to create a new instance, so we'll have switch traffic back to Toolforge if we want to redo this. Maybe we should start a new project, that way you can be added to it. I suspect more resources and a test instance will be desirable as we work on the 2020 wish anyway. From T242760#5810687 it sounded like you might already have a VPS project for wsexport?

Thanks! Maybe we should make a separate task for fixing the mobi export?

Thank you!

+1 for a new project and having a test instance. Everything is working well, let's wait for the new project before bothering about these package updates if you are ok with it.

The old wsexport project has been deleted a few years ago. Feel free to create a new one.

New VPS project requested at T244307: Request creation of wikisource VPS project

The wikisource project has been created! I went ahead and set up the dev instance, now available at https://wsexport-test.wmflabs.org/

Documentation is at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikisource

I am not sure how to upgrade calibre, or what to look for as far as the improvements it may bring. @Tpt did you want to work on that now? Or just wait, if you'd like, as we'll be doing all of this anyway when we tackle the 2020 wish.

I'll get a new production instance set up next, so we can get that out of the commtech project.

Okay both production and staging now live in the new wikisource project:

• https://wsexport.wmflabs.org (wsexport-prod01.wikisource.eqiad.wmflabs)
• https://wsexport-test.wmflabs.org (wsexport-dev01.wikisource.eqiad.wmflabs)

Awesome. I hope this shows benefits for the reliability. Initial signs look good.

I have upgraded Calibre to 3.48 (version in Buster backports) on both wsexport-prod01.wikisource.eqiad.wmflabs and wsexport-dev01.wikisource.eqiad.wmflabs.

Thanks. @Samwilson and I were wondering if that might fix T244825 as calibre's developer says the problem doesn't exist for them in the newer version.

The database config was not moved over, so https://wsexport.wmflabs.org/tool/stat.php was showing an error. I've fixed it up now. We'll have missed a few days of stats.

See T244837: Upgrade Calibre on wsexport VPSs for the Calibre stuff; in my local testing it certainly improves a few things.

Mentioned in SAL (#wikimedia-cloud) [2020-02-11T23:14:17Z] <wm-bot> <tools.community-tech-tools> Redirected this tool to wsexport-test.wmflabs.org T242760