Thanks for your fast reply!

Thanks for such a quick reaction!

It seems related to a temporary shutdown of the Toolforge servers: T291405

Just in case it helps, it also happens with Spanish Wikipedia and the script "replace". For instance with:

Has any action been applied? I haven't seen this error again for days.

This issue also happens every now and then in a webtool (https://replacer.toolforge.org) where users log in with OAuth 1.

In T247455#6095503, @Bstorm wrote:

Ok, at this point, you should be able to interact with dumps NFS in Toolforge Kubernetes in any restarted or newly started service.

In T246252#5924056, @Aklapper wrote:

Assuming this is about Toolforge

I am able to start the jdk8 container. Then I launch the tool the same way as always. But the tool is not available:

I have just stopped it, and started it again. I get again the error: "Pod is not ready in time".

I have just tried again and I can now start again the container. However it is taking a lot for the tool to start.

@Agusbou2015 please any improvement in the tool better report it in the GitHub repository itself, as explained (in Spanish) in the Wipedia user page for the tool (https://es.wikipedia.org/wiki/Usuario:Benjavalero/Replacer#Errores_y_sugerencias), which is also linked in the footer of the tool. Thanks.

@ArielGlenn Yes, it works! And with this additional parameter, it works for both bzip files, so I can already adapt the tool.

I have just tested the two files in the mail-list:

• https://dumps.wikimedia.org/cewiki/20191201/cewiki-20191201-pages-articles.xml.bz2
• https://dumps.wikimedia.org/cewiki/20191201/cewiki-20191201-pages-articles-multistream.xml.bz2

and I get a weird behaviour, but I don't know if it is just my fault.

Hi all,

Aa far as I can see, the tools-db database has been unavailable for the tool. According to the logs, between 21.32 and 22.06 (UTC) of 28-Sep.

The proposed solution has worked for me, so I will stop working with Tomcat. This will allow me also to finally migrate to Java 8.

I have tried the port 8000 with no success.

In my case, my Java tool replacer is prepared to be packaged as a WAR to be run in Tomcat, or as an SpringBoot standalone JAR.

On the other hand, I cannot create a Tomcat environment.

I have eventually been able to run the Maven packaging by reducing the amount of memory to be used:

In T210827#4916841, @zhuyifei1999 wrote:

In T210827#4916265, @Benjavalero wrote:

For the moment, I have logged in the Stretch machine and tried (with no success):

Do you have the commands and the error message?

In T210827#4915033, @zhuyifei1999 wrote:

Also, I might have been unclear that there are two grids available right now. One is the old grid of Ubuntu Trusty with Java 7, and this grid will retire in a few months; another is on Debian Stretch with Java 11. I was wondering Tomcat works on the new grid.

Tomcat is an application server which is already pre-configured on grid, so after your answer I am afraid that you are confirming me that it cannot be used on k8s (yet).

In T210827#4909818, @zhuyifei1999 wrote:

Try with --backend=kubernetes. It's querying the grid with qstat.

First I have "logged in" the JDK8 container:

I have been able to restart the Tomcat server. I think this issue can be closed.

The patch: