User talk:Daniel78

From Wikimedia Commons, the free media repository
Jump to: navigation, search
I respond to messages left on this talk page here, not on the talk pages of the users who left them.


problem with FPC bot[edit]

Hello Daniel, please look here und here. The bot forgets that the photos have already received their awards. Regards, -- Wolf im Wald (de) 11:27, 3 September 2013 (UTC)

Hi, possibly this was due to the problem discussed in the section above. And I have added a block now for that issue. Ping me if you see it again which would mean my assumption was wrong. /Daniel78 (talk) 18:50, 7 September 2013 (UTC)
Please look here.--ArildV (talk) 14:00, 20 September 2013 (UTC)
That does indeed look bad, I'll have a look. /Daniel78 (talk) 18:41, 20 September 2013 (UTC)
Checked the server logs and I can see this:
Sleeping for 5.0 seconds, 2013-09-20 07:01:21
Updating page [[User talk:Poco a poco]] via API
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 1 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 2 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 4 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 8 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 16 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
HTTPError: 504 Gateway Time-out
WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'.
Maybe the server is down. Retrying in 30 minutes...
:
Unknown Error. API Error code:blocked
Information:You have been blocked from editing
so apparently on each try the current edit got updated. I don't see what the bot code did wrong though it just used the api to try to make an edit. That said the pywikipedia lib that the bot uses has not been updated in a long time. Might be worth investigating an update. But I have no idea if that would solve the above issue. /Daniel78 (talk) 19:52, 20 September 2013 (UTC)

Bot doesn't close new nominations[edit]

Hi Daniel. I saw that the bot didn't close any new nomination in the past few days. For example, this nomination should have been closed three days ago, and it is still not closed, which is the longest delay I had witnessed for the bot. What seems to be the reason? Tomer T (talk) 15:13, 27 September 2013 (UTC)

It seem to again be the above issue with gateway timeout. I have no idea why this has started to happen recently, the bot code has not changed at all. /Daniel78 (talk) 15:21, 27 September 2013 (UTC)
But I killed it manually now and restarted it so it's back to work until it happens again. /Daniel78 (talk) 15:21, 27 September 2013 (UTC)
Maybe it's not a problem in your bot, but some external reason. Maybe there is some problem in the access to the API page. Who is the one to refer to regarding problems with the API? Maybe there is some IRC channel that can be refered in this case?
Anyway, I didn't understand if now the bot works fine and outputs normal logs? Tomer T (talk) 15:51, 27 September 2013 (UTC)
It worked for a short time but stopped again, I found an irc channel and have asked there - but no answer yet. I'll investigate if it's easy to update the pywikibot version to see if that helps. /Daniel78 (talk) 20:37, 27 September 2013 (UTC)
Hi Daniel. I'm willing to try to help you with the current problem, as far as my knowledge reaches, with some advices. Please feel free to consult with me with that, if you like.
I added some ideas in Commons talk:Featured picture candidates: "Maybe you can define the timeout yourself and increase it? Or maybe it's not in your control? Another possible solution is to split the current log page to two parts, and check if it helps." But now after I read your talk page again, I saw it also has problems with long pages like User talk:Poco a poco, so the spliting to two pages is not a general enough solution, but it may be a good idea to check if it helps. It leaves the increasing of timeout solution as an option.
By the way, as the problem arose just lately, and it is related to a timeout error, maybe it is related to some slow-network problem you're experiencing in your home network in the past few days? Or is your network working normal? Tomer T (talk) 20:25, 28 September 2013 (UTC)
Thanks Tomer. I added some answers in the main discussion so it seems it's not a timeout I can change. #wikimedia-tech claimed it would not help for me to be on another network. I have also tried both from home and from my works network seeing exactly the same problem. But yes splitting very long pages could be a workaround if we can't find any other solution, but yes some user talk pages we can't split of course. Quite annoying this as the bot never had any issues with long pages before. /Daniel78 (talk) 07:42, 29 September 2013 (UTC)
Daniel, let us know on the FPC talk page when the bot start functioning normally. Till then, we will close the nominations manually (although it is a tough job). JKadavoor Jee 09:18, 13 October 2013 (UTC)
As I don't know the real problem on the wikimedia side the only thing I can do is to try to start it and hope for the best. /Daniel78 (talk) 08:04, 14 October 2013 (UTC)
Thanks. I think you may consult Dschwen; his bots (QI, VI) seems also showing problems nowadays. JKadavoor Jee 08:12, 14 October 2013 (UTC)
I too getting "504 Gateway Time-out" while trying to save Commons:Featured picture candidates/Log/October 2013. But the data is shown as saved while clicking back and checking the page history. JKadavoor Jee 09:43, 15 October 2013 (UTC)
Weird this, I have asked Dschwen on his talk page to see if he has any ideas. /Daniel78 (talk) 09:59, 15 October 2013 (UTC)
Hope he can help; otherwise we can ask on COM:VP to gather any clue from other bot experts. JKadavoor Jee 10:04, 15 October 2013 (UTC)

With regard to the gateway timeouts, a couple of thoughts though I have not reviewed any code or know much about the bot itself:

  • You may find it useful to set your own error trap around the page upload, you can then play around with skipping a failed upload to return to later, or trying different time-outs compared to the standard. Weirdness might be related to specific pages rather than a general problem.
  • I had a lot of problems with file uploads timing out on my macmini, in Python I had to set my user-config file to change "socket_timeout = None". This means I actually run a different group of settings for uploads compared to other actions, as this may cause indefinite hanging and in other situations it is better to generate a timeout error.

-- (talk) 14:41, 15 October 2013 (UTC)

As I mentioned on the FPCTalk page "...it's a timeout not on my side but on a proxy server between me and commons. #wikimedia-tech claimed that it's a server issue I can't do anything about..." - if that is true it's very hard for me to do anything. I played around with timeouts but it seemed to have no effect. /Daniel78 (talk) 20:29, 16 October 2013 (UTC)
I made a request at Commons:Village_pump#FPCBot; expecting some helps. JKadavoor Jee 02:54, 17 October 2013 (UTC)
Yes, sounds nasty. I wouldn't have a clue of what to do about such a problem from the client end. -- (talk) 16:49, 17 October 2013 (UTC)

Today, I got the message "Our servers are currently experiencing a technical problem. This is probably temporary and should be fixed soon. Please try again in a few minutes." But data was saved. JKadavoor Jee 16:39, 16 October 2013 (UTC)

sounds like (this is just a guess) on the wmf side, rendering the page on the apache side takes longer than the squid timeout. (Rendering the page is part of saving the process). If you are getting the error I think you are, then the message should have a line about technical details. (Probably something like ERR_READ_TIMEOUT, plus a bunch of server names). If this is the case, the page in question would also probably timeout if soneone action=purge it. Sometimes problems like this can be fixed by splitting pages. The best solution is to try to optimize the templates (e.g. convert to lua) that are on the page, but sometimes that can be a little harder. Bawolff (talk) 16:20, 19 October 2013 (UTC)
Yes; frequently getting "ERR_READ_TIMEOUT" while manually trying to save the page Commons:Featured picture candidates/Log/October 2013, even though the data become saved. JKadavoor Jee 16:28, 19 October 2013 (UTC)
Message I got today:

JKadavoor Jee 17:42, 19 October 2013 (UTC)


Hmm, it seems to take 57 seconds to render this page when I tried (I think the limit is 60. Saving probably takes time to save+time to render, pushing it over the edge). When I do profiling though, it seems a lot more time is spent at hook: PageContentLanguage then I would expect. Maybe that can be omptimized on the php side:
I submitted gerrit:90769 to try and reduce the amount of time spend on figuring out what the page language is, which seems to be about 20% of the time spent (Assuming the change gets reviewed/approved). Bawolff (talk) 22:00, 20 October 2013 (UTC)
Thanks, Bawolff. JKadavoor Jee 02:49, 21 October 2013 (UTC)
Thanks, just ping me when I can make another try using FPCBot if the change goes live. /Daniel78 (talk) 07:39, 21 October 2013 (UTC)
The chronological list and log changed to new small files as the month changed. So I think you can restart the bot and make a try. I didn't get any error today. JKadavoor Jee 07:27, 1 November 2013 (UTC)
Ok I started it now, it did one change in the first run which was ok. So I'll enable it again - but keep an eye on it as I so far only have a single change to go on. /Daniel78 (talk) 09:02, 4 November 2013 (UTC)
Thanks; will let you know if anything unexpected happen. JKadavoor Jee 09:14, 4 November 2013 (UTC)
Hope everything is going fine so far. But according to Bawolff, the problems can reborn when the number of entries at the log file increases. He said his "proposed change in that area has not yet been merged". So I think we can create a temporary log file and move the contents to it, in case of an emergency, if the bot starts malfunctioning. When the month is over, we can bring the contents back to the original log file. What you think? JKadavoor Jee 09:22, 5 November 2013 (UTC)
Sounds ok to me as nothing has changed on the bot side so the issue could definitely happen again. /Daniel78 (talk) 09:25, 5 November 2013 (UTC)
The change has now been merged. Its scheduled to be included next time commons gets a software update, which is on Monday update: Tuesday (No software updates on American holidays). As a reminder though, at the end of the day, bigger pages do take longer to render - this will fix some of the slowness and give more breathing room (assuming it actually works, about 20% more), but if the page keeps growing, there eventually would come a point where it is just too large. Hopefully though that will be quite a ways away. Bawolff (talk) 01:47, 7 November 2013 (UTC)
Thanks Brian. JKadavoor Jee 02:49, 7 November 2013 (UTC)
Good to hear, thanks. /Daniel78 (talk) 09:37, 7 November 2013 (UTC)

Hi Daniel; the bot is working fine so far. But today we noticed a minor issue. See User_talk:Jkadavoor#FP_nomination_where_name_doesn.27t_match. It seems there is a conflict between the parameter usage style (with and without the prefix File:) in {{Assessments}} and {{FPC-results-reviewed}}. JKadavoor Jee 13:02, 16 November 2013 (UTC)

See this example too. The "com-nom" doesn't accept "File:" prefix and generates warning if added (by bot as now). JKadavoor Jee 07:04, 17 November 2013 (UTC)

Important: It seems the bot failed to remove File:Bixby Creek Bridge May 2011 panorama.jpg from the Commons:Featured picture candidates/candidate list after adding it to the log file; probably due the DATA READ ERROR due the huge size of the log file. As a precautionary measure, I created a temporary log file and move the contents to it as I suggested earlier. We can restore the contents when the month is over. Hope it works. JKadavoor Jee 15:31, 17 November 2013 (UTC)

@Daniel78: FPCbot hasn't been working for several days now, and since Jkadavoor seems to be inactive, currently I do the promotions (no one else except Jk + me would ever do, as it seems). Please disable FPCbot for the time being, as there are only such edits which aren't really helpful. Thanks --A.Savin 11:55, 24 November 2013 (UTC)

I'm hoping now that the trouble is/was maybe because of this edit [1]. Let's wait what the next run will show. Another question: I'm planning to subdivide Commons:Featured pictures/Places/Architecture in several subpages, for reasons stated in Commons_talk:Featured_picture_candidates#Commons:Featured_pictures/Places/Architecture. Is any adjustment of the FPCBot necessary for that we come through this subdivision without having broken your bot again? --A.Savin 19:58, 24 November 2013 (UTC)
Indeed. I reverted, FPCBot works. --A.Savin 22:36, 24 November 2013 (UTC)

Important: Hi Daniel, the bot is not closing any nomination since 11:33, 4 December 2013. That is the last action from the bot. As per Bawolff, it may be due to the last code update on commons was on 3 December 2013. I requested to report it, but he said "To make a meaningful report I'd need information from the bot author (What error is the bot actually encountering. Is it the previous 503 issue, or is it encountering some new issue)." Please do the necessary. JKadavoor Jee 02:36, 7 December 2013 (UTC)

Hi, the bot had lost its login for some reason so I had to log it in again - not sure why that happened but after doing so a manual run went fine. So assuming it will continue to run in the automatic runs - if not just ping me again :) /Daniel78 (talk) 21:18, 7 December 2013 (UTC)
Hi Daniel. I have uplaoded the code of QICbot here. The crucial change was the tryPut function I put in about three weeks ago. It helped increase the reliability of the bot a lot. --Dschwen (talk) 20:58, 7 December 2013 (UTC)
Hi, this time it was not that problem but I will definitely have a look if I see it again. Thanks. /Daniel78 (talk) 21:18, 7 December 2013 (UTC)
Still, please help: May it be any critical for the bot to subdivide Commons:Featured pictures/Places/Architecture? Thanks. --A.Savin 21:45, 7 December 2013 (UTC)
I think that should work fine - the bot has no list by itself over category pages it just use what is used in {{FPC-results-reviewed}}. /Daniel78 (talk) 09:28, 8 December 2013 (UTC)
Thanks. --A.Savin 10:28, 8 December 2013 (UTC)

Delisting nominations[edit]

FPCBot just closed Commons:Featured picture candidates/removal/File:Panorámica de Las Médulas.jpg early. Could you tell the bot to ignore any FPC that begins with "Commons:Featured picture candidates/removal"? Thanks. -- King of ♠ 01:38, 25 November 2013 (UTC)

FPCBot seems down[edit]

FPCBot seems down; probably lost its login credentials on software update. Please check. Jee 02:54, 8 January 2014 (UTC)

Thanks for reporting. I logged it in again. Doing a run right now... /Daniel78 (talk) 08:29, 8 January 2014 (UTC)
Thanks. Jee 08:42, 8 January 2014 (UTC)

And again. --A.Savin 15:46, 8 February 2014 (UTC)

Thanks again for reporting. Fixed now. /Daniel78 (talk) 10:09, 10 February 2014 (UTC)

Bot didn't run in the evening (15 CET). Down? Jee 15:23, 12 March 2014 (UTC)

Had to type the password again. Wonder why this happen more often now. Anyway a new run ongoing now. /Daniel78 (talk) 08:53, 13 March 2014 (UTC)
Thanks. I think it happens when software updates going on the WMF servers (?). Jee 09:21, 13 March 2014 (UTC)

Bot seems down again. Jee 14:53, 11 April 2014 (UTC)

Sorry for the delay - was travelling. Password needed again, would be really good to automate the login when that happens. /Daniel78 (talk) 13:19, 21 April 2014 (UTC)
Thanks; I too away for a week. :) Jee 04:04, 22 April 2014 (UTC)

ArchiveBot[edit]

Hi, I noticed you have set up User:MiszaBot to archive your talk page. Unfortunately, the bot has stopped working, and given how its operator is inactive, it is unclear when/if this will fixed. For the time being, I have volunteered to operate a MiszaBot clone (running the exact same code). With that said, your input would be appreciated at Commons:Bots/Requests/ArchiveBot 1. Regards, FASTILY 07:37, 20 April 2014 (UTC)