Hi all,
Does anyone know when we will be upgrading the Clouds replica DBs to
MariaDB 10.2? I am asking mainly because we are on 10.1.33, 10.3 is now
out, and since 10.2 support for CTEs (WITH statements) has been added which
is very handy.
Thanks,
Huji
The legacy Ubuntu Trusty grid engine job grid has been shutdown!
Thanks to everyone who was involved in migrating existing tools from
the old grid to the Kubernetes cluster or the new Debian Stretch job
grid.
There were still 385 tools that may have been running jobs or
webservices on the Trusty grid at the time of shutdown. A static list
of these tools is preserved at
<https://tools.wmflabs.org/trusty-tools/>.
Instructions are still available at
<https://wikitech.wikimedia.org/wiki/News/Toolforge_Trusty_deprecation>
for migrating tools that are currently down.
Bryan, on behalf of the Toolforge admin team
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Technical Engagement Boise, ID USA
irc: bd808 v:415.839.6885 x6855
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Because of some issues mounting NFS on the PAWS master, it is being rebooted. Traffic to the front page has already been routed through another node, but server creation won’t work until after the reboot is complete.
Brooke Storm
Operations Engineer
Wikimedia Cloud Services
bstorm(a)wikimedia.org <mailto:bstorm@wikimedia.org>
IRC: bstorm_
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Reminder: Technical Advice IRC meeting this week **(Wednesday) 4-5 pm UTC**
on #wikimedia-tech.
Question can be asked in English, German & Romanian.
⏰ Please note: due to summer time change this week will be the last meeting
at 4 pm UTC. Beginning with next week the meeting will start at 3 pm! ⏰
The Technical Advice IRC Meeting is a weekly support event for volunteer
developers. Every Wednesday, two full-time developers are available to help
you with all your questions about Mediawiki, gadgets, tools and more! This
can be anything from "how to get started" over "who would be the best
contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
Michi (for the Technical Advice IRC Meeting crew)
--
Michael F. Schönitzer
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
As previously announced on this list [0][1] we are in the process of
replacing the old Ubuntu Trusty instances in Toolforge with fancy new
Debian Stretch instances.
This process is reaching its next major milestone on Monday
2019-03-25. During the general US workday on that date (14:00-00:00
UTC) the Toolforge admin team will be dismantling the legacy Ubuntu
Trusty job grid. Any tools that have not migrated to either the
Stretch grid or the Kubernetes cluster at that point will be forcibly
shutdown. Nothing will be deleted in the tools' $HOME directories, but
any Trusty grid jobs will be stopped. Any crontab file remaining on
the
old grid's cron server will be archived as
"$HOME/crontab.trusty.save". Maintainers who somehow missed all of the
announcements will be able to login and restart their tools on the
Stretch grid or Kubernetes.
See <https://wikitech.wikimedia.org/wiki/News/Toolforge_Trusty_deprecation>
for additional information and tips on common problems that have been
found thus far.
[0]: https://lists.wikimedia.org/pipermail/cloud-announce/2019-January/000122.ht…
[1]: https://lists.wikimedia.org/pipermail/cloud-announce/2019-March/000142.html
Bryan, on behalf of the Toolforge admin team
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Technical Engagement Boise, ID USA
irc: bd808 v:415.839.6885 x6855
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hello dear wikifriends,
Yesterday I've sent a job called 'itwiki-orphanizerbot' to the grid using 'jsub -once'. It should ends in minutes. In fact, from my log.out I see yesterday it is apparently quitted successfully, but today I can't run it again with '-once' because it says it's already active.
I followed the [[Help:Toolforge/Grid#Stuck jobs]] but apparently I have not fixed the situation and it's still active.
Tl;dr;
How to kill my 'itwiki-orphanizerbot' task?
Thank you!
--
Valerio Bozzolan
https://it.wikipedia.org/wiki/User:Valerio_Bozzolanhttps://meta.wikimedia.org/wiki/User:Valerio_Bozzolan
E-mail sent from an Android LineageOS device without proprietary Google Apps, with the K-9 Mail client from F-Droid, delivered from my Postfix instance in my Debian GNU/Linux server.
Have fun with software freedom!
Good morning!
As a side-effect of our response to the current gerrit vandalism
epidemic, the 2fa integration between Horizon and Wikitech has been
disabled. That means that existing Horizon sessions are still valid but
fresh logins will fail.
This problem is being actively worked on. In the meantime, don't panic
if you get an error while trying to log in.
-Andrew
_______________________________________________
Wikimedia Cloud Services announce mailing list
Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud-announce
Hi all,
I moved my tool (parliamentdiagram) to Stretch today, and everything
works, except direct upload to Wikimedia Commons. I get the following
error:
"Error: File upload parameter "file" is not a file upload; be sure to
use "multipart/form-data" for your POST and include a filename in the
"Content-Disposition" header."
The request looks like this:
action: upload
uri: /data/project/parliamentdiagram/public_html/svgfiles/2019-03-10-18-07-19-687399-18179320035893093241.svg
filename: My_Parliament.svg
pagecontent: == {{int:filedesc}} ==
(and some more content that I'm snipping for brevity)
This works fine on Trusty, but neither on Gridengine or Kubernetes.
Where should I look for the cause?
For now, I'm going to keep the tool running on Trusty so that my users
still have this option.
--
David Richfield
+49 176 72663368
Hi,
following some vandalism attempts, both Horizon and Toolsadmin are affected by a
general Oauth issue in Wikitech which prevents from proper user authentication.
Affected URLs are:
* https://horizon.wikimedia.org/
* https://toolsadmin.wikimedia.org/auth/login
Horizon is the web UI used to create and manage Cloud VPS.
Toolsadmin (also known as striker) is the web UI used to create and maintain
Toolforge accounts.
We have no estimation right now on when a fix will be available, but several
people are actively involved in trying to get things back to normal.
regards
--
Arturo Borrero Gonzalez
Operations Engineer / Wikimedia Cloud Services
Wikimedia Foundation
Hello,
While trying to troubleshoot performance issues on our NFS server, it
became apparent that we have a peak of requests durings hours 0-3 every
day. This is currently hard to properly manage and results in slower
performance for everybody.
Here's a breakdown of the number of cronjobs scheduled to start in the
new SGE cluster, per hour:
473 * # hourly
213 0
106 1
82 2
78 3
54 9
50 4
48 7
45 12
42 5
You can see that, apart from hourly jobs, we have most cronjobs
starting in hours 1-3.
My advice is that, if your workload permits, *schedule your cronjobs
outside of that time window so you are not competing for resources with
everybody else*. The more spread throughout the day your cronjobs are,
the better.
Also beware of step values like "*/2" which will make your cronjob run
on hours 0 and 2 too.
If you have any questions, please find us on #wikimedia-cloud
Regards,
--
Giovanni Tirloni
Operations Engineer
Wikimedia Foundation