User Details
- User Since
- Oct 23 2014, 3:02 PM (490 w, 4 d)
- Availability
- Available
- LDAP User
- Magnus Manske
- MediaWiki User
- Unknown
Wed, Mar 13
@dcaro thanks, done
Got it working. For future reference:
I have some updates. With php.ini as
extension_dir="/layers/fagiani_apt/apt/usr/lib/php/20210902" extension=mysqlnd extension=mysqli
it loads the mysql library. Still fails with some password error but that seems like something code-wise to debug.
For my own testing, is there a way to get a shell into the docker container? I have seen the docs for the webservice one, but that doesn't seem to fly for non-webservice ones?
I created a custom php.ini and use it in the command:
php8.1 -c /data/project/mix-n-match/mixnmatch_rs/php.ini /data/project/mix-n-match/scripts/person_dates/update_person_dates.php 48922
The php.ini:
extension_dir="/layers/fagiani_apt/apt/usr/lib/php/20210902"
I also added a whole bunch of packages to the Aptfile, just in case.
Tue, Mar 12
@taavi I added php-mysql to the Aptfile and rebuild the image, same error.
Thanks @taavi Is there a list of packages required for a toolforge-equivalent php setup?
Looks like the php setup is incomplete. Running php8.1 path/to/my/php/script dies with Fatal error: Uncaught Error: Class "mysqli" not found.
Would it be possible to add a symlink in $PATH somewhere? php is stable, php8.1 maybe less so
Ah, I found /layers/fagiani_apt/apt/usr/bin/php8.1, I guess it's just not symlinked anywhere?
I added an Aptfile as described and rebuild the image, but:
tools.mix-n-match@tools-sgebastion-10:~/mixnmatch_rs$ toolforge jobs run --mem 2000Mi --cpu 1 --wait --mount=all --image tool-mix-n-match/tool-mix-n-match:latest --command "php --version" single ERROR: job 'single' failed: +-------------+------------------------------------------------------------------+ | Job name: | single | +-------------+------------------------------------------------------------------+ | Command: | launcher php --version | +-------------+------------------------------------------------------------------+ | Job type: | one-off | +-------------+------------------------------------------------------------------+ | Image: | tool-mix-n-match/tool-mix-n-match:latest | +-------------+------------------------------------------------------------------+ | File log: | no | +-------------+------------------------------------------------------------------+ | Output log: | | +-------------+------------------------------------------------------------------+ | Error log: | | +-------------+------------------------------------------------------------------+ | Emails: | none | +-------------+------------------------------------------------------------------+ | Resources: | mem: 2000Mi, cpu: 1 | +-------------+------------------------------------------------------------------+ | Mounts: | all | +-------------+------------------------------------------------------------------+ | Retry: | no | +-------------+------------------------------------------------------------------+ | Status: | Failed | +-------------+------------------------------------------------------------------+ | Hints: | Last run at 2024-03-12T14:23:38Z. Pod in 'Failed' phase. State | | | 'terminated'. Reason 'Error'. Started at '2024-03-12T14:23:39Z'. | | | Finished at '2024-03-12T14:23:39Z'. Exit code '127'. | +-------------+------------------------------------------------------------------+
I also tried commands like "sh -c 'php --version'" but no success.
Mon, Mar 11
Fri, Mar 8
Yes, the third attempt passed. However, 500 errors should be cause for concern, even if it eventually runs through.
Now happening repeatedly for the mix-n-match tool:
toolforge build start https://github.com/magnusmanske/mixnmatch_rs/
this has resolved itself
Tue, Mar 5
Yes, works for me, thanks
Fri, Mar 1
Thu, Feb 29
Ran it again now, works fine. Closing this issue, will re-open if it keeps happening.
Tue, Feb 27
Fri, Feb 23
Now starting to see error 429 (too many requests), which is better (for debugging). Did something change in the meantime?
Thu, Feb 22
This happens ~50% of the time, re-running the exact same command often works.
Wed, Feb 21
Thanks, that works form me. It is much slower than before, as it needs to run full compilation every time, instead of just the changed bits. Ah well.
I tried that and got
[step-results] 2024-02-21T11:49:25.959261833Z Built image tools-harbor.wmcloud.org/tool-listeria/tool-listeria:latest@sha256:24ac86ba3d8e4c11568e158a172016dcf9b8e697312866c674ad5ae6f6b4954b
But the tutorial shows me only how to deploy a webservice. How do I start the bot executable as a normal toolforge job?
/mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main) /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main) /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main) /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /mnt/nfs/labstore-secondary-tools-project/listeria/listeria_rs/target/release/build/openssl-sys-92765f660cd77871/build-script-main)
Ah, gridengine doesn't compile it either... Works fine locally though
Mon, Feb 19
Seems fixed now
The Cloud-Services project tag is not intended to have any tasks. Please check the list on https://phabricator.wikimedia.org/project/profile/832/ and replace it with a more specific project tag to this task. Thanks!
Feb 8 2024
The funny thing is, if you click on the movie https://commons.wikimedia.org/wiki/File:The_Sea_Beast_(1926).webm to play it, the moment the player comes up, it shows the correct duration. Where does it get that from?
Feb 7 2024
I have limited it to 50 API connection at a time. Still throwing 104 errors. Either I did it wrong, or there is some other issue.
Thanks to the recently relaxed limitations per job on Toolforge, I am running this with more async threads, so without actual code change, it would have increased the number of connections.
Please use the bot as you like for testing!
This issue is persisting for the listeria tool. The bot is now down from ~40K edits/day to ~500. Something needs to be done, soon.
Jan 30 2024
Nov 9 2023
I am open to this, as I already have a Trove instance for baglama2, and it works well (after some initial problems).
FWIW I just saw this ticket, and added an index to the log table which should speed things up. I can also rewrite the query if that does not suffice, please let me know. Let's discuss Trove in T350862 .
Nov 1 2023
Webservice is not running, returns only blank page, no error
Seems to be fixed now?
Aaaaand its back again.
Oct 26 2023
@taavi Success! I tried /Users/mm6/php/magnustools/public_html/php/ToolforgeCommon.php which had magically reverted to non-group-writable again, so I changed it to group-writable now, and yes I can edit as before!
Oct 25 2023
Other test case: /Users/mm6/php/magnustools/public_html/php/ToolforgeCommon.php
Odd. Now it does. Same issue.
FWIW, I can edit the files if I become the tool, but I don't like editing in shell, especially for larger code.
Sep 27 2023
Changed the query so it's now working as before the ORES change.
Resolved, see T347367
PetScan restored for now. Waiting for the CORS issue to be resolved.
Sep 12 2023
Restated again, and filed T346126
Aug 22 2023
Jul 19 2023
Done
Manually restarted webservice, as toolforge cannot possible do that automatically </sarcasm>
Jul 7 2023
It might be worth mentioning that the limitations for Mix'n'match have been increased at some point, I can now run a job with 2CPUs/3GB RAM, which is much better.
Jul 6 2023
I have restarted the webservice, all good now.
Jul 3 2023
Ah here's a new one. I start kubernetes job rustbot. It runs. I start rustbot2. Now rustbot2 runs but rustbot has vanished:
tools.mix-n-match@tools-sgebastion-10:~/mixnmatch_rs$ toolforge jobs list Job name: Job type: Status: ----------- ----------- --------- rustbot continuous Running tools.mix-n-match@tools-sgebastion-10:~/mixnmatch_rs$ toolforge-jobs delete rustbot2 ; \rm ~/rustbot2.* ; \ > toolforge-jobs run --image tf-php74 --mem 1000Mi --continuous --command '/data/project/mix-n-match/mixnmatch_rs/run.sh second' rustbot2
Jun 30 2023
@dcaro Listeria was one of them, and quickstatements at some point.
@aborrero To be fair, Mix'n'match used to fire off small/medium-sized jobs to gridengine, unlikely to bring a machine down. The requirement for uniquely named kubernetes jobs, and the limitation on the number of jobs, with no ""waiting queue", forced me to rewrite much of my code, into my own "job engine" that runs as a single kubernetes job. However, now the restrictions to individual kubernetes jobs bite me.
And it doesn't answer the question why the webservice stops pretty much every time I start kubernetes jobs?
That is to say, you say I'd have to move to VPS because you changed the tech stack, not because of resource usage. Resource usage was fine under grid engine. In fact, it was fine running the PHP version of the code. Don't tell me kubernetes can not support the Rust version which uses a lot less resources?
In principle it would (I am already running the petscan VPS), but this is missing my point.
Jun 28 2023
This should do it. Tested and seems to work.
I confirm that "Silly Matlin" has been appearing in Mix'n'Match edits, but it is a straight lie that I "refused to comply". Not entirely surprising though. Anyway, it's a real issue, but User:Solidest seems to have found a bug, which I just saw since I don't follow the [[User_talk:Silly_Matlin]] page. I will look into it, again.
May 17 2023
Apr 27 2023
Apr 4 2023
All good now
Apr 3 2023
Mar 23 2023
Apologies, my mistake, needs two underscores! All is well.
Thanks, better, but not quite there yet:
tools.wdqsbe@tools-sgebastion-10:~$ sql local Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 73249977 Server version: 10.1.44-MariaDB MariaDB Server
Mar 22 2023
Mar 7 2023
Found the problem, on my side. Apologies.
Mar 6 2023
Consumer key is b5dc46b99399f49d03757216abd14e66 (QuickStatements). I didn't change the URL, and I think the toolforge clock is working fine.
Mar 1 2023
Note: Oauth 1, not 2!
The reason I used bitbucket in the past was a (long removed) policy on github that limited the number of free repos. I also have some repos on github, which is owned by M$ and probably not very libre either.
Feb 24 2023
FWIW I started developing an new tool called GULP, now under early development.
Feb 17 2023
After T329853 can we please add something so databases don't stay vanished until I complain at a "a proper support venue" (which seems to be only IRC, with mattermost link broken)?
Feb 16 2023
Feb 7 2023
Thanks, I forgot to check the "URL needs to start with" checkbox...
Jan 24 2023
Just for posterity, I'd like to mention my own wikibase diff engine in Rust: https://gitlab.com/tobias47n9e/wikibase_rs/-/blob/master/src/entity_diff.rs
3 CPUs would be plenty, I think that's actually the per-tool limit, including the webservice?
This stopped working about an hour ago