- See the Bibliowiki site status page at https://status.biblio.wiki/. Bookmark for later.
- See the Resolved Issues Archive for those items that have been resolved/fixed.
Wikilivres Functionality Status - UPDATE 30 April 2017 - Loss of Pages
On 30 there was a loss of an unknown number of User/User_talk pages and Templates. The templates have been restored from a previous backup, however the user pages will require longer to retrieve from a database backup. It is unclear what the source of the delete was, though this could be a spam admin tool that was used accidentally, or a maintenance process that acted out of bounds. The normal delete log is not showing these deletions. --Sysadmin (talk) 13:34, 30 April 2017 (UTC)
- comment -- it is NOT just userpages & templates. some author pages are gone too, &
not sure about actual "content" pages & files.can now confirm that some content is gone too: https://wikilivres.ca/index.php?title=Tarzan_and_the_Leopard_Men_(serialized_version,_1_of_6)&action=edit&redlink=1 example: https://wikilivres.ca/index.php?title=Winston_Leonard_Spencer-Churchill&action=edit&redlink=1 Victor Hugo categories are gone too https://wikilivres.ca/index.php?title=Category:Henry_Louis_Mencken&action=edit&redlink=1 (subject's author page also mia) & just recreated the cat for a.a. milne & this was a "hard delete", not just a "hidden from public view" delete. why does ANY bot on this project have "hard-delete" powers? i think that is a bad idea, for obvious reasons... >__< ditto for any "mass-delete" tools for that matter. --Lx 121 (talk) 23:34, 30 April 2017 (UTC)
Wikilivres Functionality Status - UPDATE 26 April 2017 - Heavy Load Resolved
On 25 April the site experienced heavy load. There were three combining factors involved that lead to a heavy load on the CPU and delay in responding to site page requests: job processing of thumbnail images, the ElectronPDF service running amok, and heavy indexing by spiders. Individually each could be handled, but together they were too much. Each of these issues have been mitigated: the large set of Pauly-Wissowa files have been removed (>2,700, which was the massive drag both on thumbnail generation and on search engine spidering), the ElectronPDF service (which was being tested) has been removed, and the sitemap.xml and robots.txt files have been optimized for a leaner spider load and cleaner set of indexed files. --Sysadmin (talk) 04:23, 26 April 2017 (UTC)
- comment -- slightly lost; why did we remove all that content, & is it available elsewhere online? o__0 Lx 121 (talk) 23:43, 30 April 2017 (UTC)
- 1 Templates needed (right away) - WAITING ON FEEDBACK
- 2 Check User - STILL BROKEN
- 3 Authority Control (New Feature Request) - UNDER DISCUSSION
- 4 HotCat (Gadget) -- BROKEN, OPEN ISSUE
- 5 Favicon - ON TASK LIST
- 6 Bibliowiki:Interwiki - OPEN ISSUE
- 7 Wikilivres website footer -- FILED AS TASK
- 8 Localization -- ONGOING ISSUES
- 9 category stuff -- OPEN ISSUE
- 10 header template vs page menu - OPEN ISSUE
- 11 "collapsing" -- OPEN ISSUE
- 12 Extension:Math is needed - STILL NOT WORKING, OPEN ISSUE
- 13 Spam bots -- TASK UNDERWAY
- 14 needed templates: category redirect - UNDER DISCUSSION
- 15 restoring items from accidental mass-delete
- 16 biblio.wiki SSL Cert issue - RESOLVED
- 17 Index and Page Namespaces - Open Task
- 18 Website Space Limitations Roadmap
- 19 bug report: database search error - FIXED
- 20 Imported scripts from Wikisource in Common.js
- 21 autoconfirmed
- 22 creation of new accounts is suspended?
- 23 Index:Rush Galpo Sankalan - Part I.pdf
- 24 Delete revisions right
- 25 Downtime on 23-24 November
- 26 Downtime 07 Jan 2017
- 27 Ongoing slowdown/errors 09 Jan
- 28 Database error on Special:Search - FIXED
- 29 Problem with pages import
- 30 Wiki Platform Change
Templates needed (right away) - WAITING ON FEEDBACK
- PD-pma|deathyear template
- author page header template
- fixing the author-biblio page header-template should also be on the shortlist; this whole experience sort of shows how we (mw projects in general) are over-dependent on separately-loaded templates! Lx 121 (talk) 15:57, 3 April 2017 (UTC)
- I need more info on this please. What the functionality is/was, etc. --Sysadmin (talk) 16:38, 6 April 2017 (UTC)
- I understand that many templates have not been restored, and definitely that is a part of the restore priority --Sysadmin (talk) 16:46, 2 April 2017 (UTC)
- & i absolutely understand the size & difficulty of the work. not nagging; it'll get done when it gets done. but this one is by far the most critical & most-used "licensing" tag for our content; all the others are "secondary" (which i why i listed it as a single-item, rather than just saying "licensing templates") Lx 121 (talk) 16:38, 3 April 2017 (UTC)
Check User - STILL BROKEN
Authority Control (New Feature Request) - UNDER DISCUSSION
- (& we should start using an authority-control thing, now that we can)
- Not clear what that is. Please provide urls or examples I can follow up on. --Sysadmin (talk) 16:46, 2 April 2017 (UTC)
- "authority control" identifiers are unique, standardised alphanumerics for a specific person or thing; library/data science -thing. naturally, there are presently many different standards/systems... https://en.wikisource.org/wiki/Wikisource:Authority_control the wm projects are now using them & templates are available see the bottom of this page, for an example https://en.wikisource.org/wiki/Author:Henry_Louis_Mencken -- Lx 121 (talk) 18:46, 2 April 2017 (UTC)
- This looks like work without much value to visitors. We are in the Google world so having exact unique identifiers don't do much. I could be wrong and am open to further discussion. And, if enough people feel differently we can implement. It should be seen as valuable by the majority of editors, since it ads to everyone's work. Comments from other editors encouraged. --Sysadmin (talk) 11:48, 19 April 2017 (UTC)
HotCat (Gadget) -- BROKEN, OPEN ISSUE
- HotCat is enabled and editors can select that in their Preferences>Gadgets. It is under gadget-section-editing-gadgets, and is the third option which reads "Easily add / remove / change a category on a page, with name suggestions.".--Sysadmin (talk) 16:41, 2 April 2017 (UTC)
Favicon - ON TASK LIST
As I stated it's fine to have this new favicon, might be we could improve it in the next time: some time ago I saw a similiar favicon used by a project like wiktionary or so, which was ver similar and black and white (I cannot find it now). Nevertheless, if we could change the color of the present favicon to sepia or brown or something like the new logo it would be very nice, I think. -jkb- (talk) 20:21, 4 April 2017 (UTC)
- just a thought, but what if we "rotated" (or randomised) a bunch of different "W"-symbols as icon? Lx 121 (talk) 09:10, 17 April 2017 (UTC)
Bibliowiki:Interwiki - OPEN ISSUE
We have to arrange imports (interwiki import + import upload or better both) from wikisources to here an vice versa (I need urgently in the next time imports from here to cs.source) -jkb- (talk) 21:57, 2 April 2017 (UTC)
We had our own interwiki that were put on meny pages, and that not working now, see Bibliowiki:Interwiki, eg. de.wp:Johann Wolfgang von Goethe should go to article on German Wikipedia, and de.ws:Johann Wolfgang von Goethe should go to article on German Wikisource, and so on.
- I'm afraid the syntax of the interwikis has changed, e.g. instead of :cs:ws:XXXYYY works now wiksource:cs:XXXYYY etc. -jkb- (talk) 16:20, 6 April 2017 (UTC)
- OK. You are right, some syntax we have "built-in" in this MediaWiki already, but there is possibility to add new... and they were added on wikilivres.ca as additional interwiki. OK, we can change them by bot, but a good idea is to add them as it was in previous wiki. Electron ツ ➧☎ 16:43, 6 April 2017 (UTC)
Localization -- ONGOING ISSUES
The localization seems to work good now, so if I set in my prefereces eg. Polish language I see most of information and templates in Polish...
But is not all we have on wikilivres.ca. There on wikilivres.ca we have the feature, that if I set eg. Polish, my main page was not Main Page (like it is now) but Strona główna, and on Special:RecentChanges I had seen no MediaWiki:Recentchangestext but MediaWiki:Recentchangestext/pl as default and so on... It works for others our main languages, too. Now it don't work, I see their English version as default.
What's more, as I remember if the page has English version, eg. Bibliowiki:Community Portal/en and there were their local vesions, eg. Polish -> Bibliowiki:Community Portal/pl and others language versions, there in left sidebar were put interwiki links to them. Now it dosn't work any more. Electron ツ ➧☎ 14:14, 7 April 2017 (UTC)
- OK. Btw. Meanwhile I've tried other way of lokalization of Main Page and MediaWiki:Recentchangestext-lang. They transcluded other pages in local language. It's working properly now , so I see Strona główna (Polish main page) and MediaWiki:Recentchangestext-lang/pl on default if I set Polish language in my Prefences. And it works for others our main language, now (if there is the page in an lokal language, or in English, if there is not). Maybe in the future we should change it to work in the way it was working before, but now it works not bad, I think. Electron ツ ➧☎ 10:17, 13 April 2017 (UTC)
category stuff -- OPEN ISSUE
1. something seems to be lagging today in the categorization "-thing". newly-added items & subcats are not showing up in category pages (purge is NOT clearing it); & i don't recall that happening before. (the added pages still show as "categorised" @ their page-bottom, they just don't appear on the cat-page)
- This could be maintenance tasks that have been sitting in a job queue. I'm manually forcing them through. The restore created a lot of this backlog. Still plunging away. SIgned, your Wiki plumber. --Sysadmin (talk) 10:33, 11 April 2017 (UTC)
- Please test HotCat again and let me know. Sorry to keep asking, but things are changed/updated since this last post, and I need to get feedback. --Sysadmin (talk) 10:33, 11 April 2017 (UTC)
- Filed as a task/issue as Github issue #67
hi; something in our present title/header template seems to be "supressing" the display of the page-section menu box. can we fix this? being able to navigate sections hugely increases page-useability; especially on longer texts. also sectioning makes it easier to "break down" a book into multiple pages later on. best, --Lx 121 (talk) 01:44, 8 April 2017 (UTC)
- Is it a __NOTOC__ somewhere in a template? Can you give me some example pages of where it doesn't work (and what expected behavior is), I'm not exactly sure I know what is broken. --Sysadmin (talk) 10:30, 11 April 2017 (UTC)
- hi, sorry it's taken me so long to get back to you on this one! here is an on-wiki example of a working submenu for page-sections: https://wikilivres.ca/wiki/The_Complete_Ian_Fleming but on any page formatted up "book-style" (header, etc.) the page-section menu won't display. at least not on my screen; am running current firefox, on current ubuntu. like here, the page has been sectioned, but no menu do i see(?): https://wikilivres.ca/wiki/Once_on_a_Time i am tentatively assuming it is something in the header template that suppresses it, but that's just a guess. would be VERY useful for page-navigation, if we got it back; they are bog-standard on long wikipedia articles. --Lx 121 (talk) 08:44, 17 April 2017 (UTC)
"collapsing" -- OPEN ISSUE
not "top of the list", but some kind of "collapse" function would be useful for more involved bibliographies; & would have many uses elsewhere. https://en.wikipedia.org/wiki/Template:Collapse --Lx 121 (talk) 06:03, 8 April 2017 (UTC)
- Added to Github Issue #50
Extension:Math is needed - STILL NOT WORKING, OPEN ISSUE
See: Extension:Math, it allows to render mathematical formulas.
Spam bots -- TASK UNDERWAY
On my mind on the first we should install:
- Abuse Filter -> https://www.mediawiki.org/wiki/Extension:AbuseFilter
- the scripts for filters for Abuse Filter can be taken from here -> https://en.wikisource.org/wiki/Special:AbuseFilter
- ConfirmEdit -> https://www.mediawiki.org/wiki/Extension:ConfirmEdit
- FancyCaptcha -> https://www.mediawiki.org/wiki/Extension:ConfirmEdit#FancyCaptcha
as it is on wikisource -> https://en.wikisource.org/wiki/Special:Version
- Thanks for this @Electron:. I've done some research on this on the Github security and anti-spam documentation page, however I have not yet implemented these items. I will add your comments to the Github Issue #1 Antispam/Antivandal Measures and Best Practices. I have this on the Wikilivres 1.1 release schedule which is 30 April. --Sysadmin (talk)
- I've implemented about 10 things that will help reduce attack surface and catch some of the bad actors. However, I still have a number of additional items to do. Detail here.
needed templates: category redirect - UNDER DISCUSSION
i have just noticed that we do not seem to have a "category redirect" template anymore? this should be on the shortlist of essential tools for categorization work. --Lx 121 (talk) 12:40, 23 April 2017 (UTC)
- Hi @Lx 121:, is this what you have in mind? Please advise. --Sysadmin (talk) 13:11, 23 April 2017 (UTC)
- @ @Sysadmin:; yes that's it. it's "bog standard" on all the wikimedia (wmf project) wikis i've ever edited on. commons has the same thing, which is where i've used it the most. there may also be "hard" & "soft' variations someplace. but the standard one is fine. Lx 121 (talk) 05:52, 24 April 2017 (UTC)
- I don't see a problem if an admin wants to use category redirects, that sounds reasonable, even if other admins don't think they are worthwhile. Unless they break something, or introduce some kind of burden on the system, which I don't forsee. That said, we should stay away from mass-creation of all possible template redirects. As mentioned below, I will look into ways of automating fixes to this kind of case-sensitivity problem. Also, realize we can get data on errors (404s) that are encountered on the site from search and from the weblog. So we can see practical, actual problems that occur, and respond to them. The category redirect pages on wikipedia and wikisource are different. See:
- Looking closer, there are some useful things to learn about how Wikipedia policy uses category redirects and also Wikisource. From what I can tell:
- * Category Redirects are not used on misspellings, but things like diacritics vs. non-diacritics, punctuation (hyphen vs. m-dash or n-dash), and of course, capitalization (which is not a spelling error, per se).
- * On misspellings, Wikisource suggests the use of https://wikisource.org/wiki/Template:Bad_name
- * Also note that these redirects are soft based on what a category is (technically different than pages), and effectively work by means of bots that patrol and move things from one category (the redirecting one) to another (the redirected one).
- Comment: In my opinion such category redirects are useful on big projects only, where is big traffic and it is problem to solve some bad things withould automatic tools. On small projects (as us is now) they are not worth to waste the time on it... Do not shoot the cannon to kill the fly. I will fix this "big problem" in a minute. But is is only my own opinion... If you think it would be very usefull I have no other objections. Electron ツ ➧☎ 10:00, 24 April 2017 (UTC)
Case-Sensitivity in MediaWiki
This gets at a bigger issue which is a design problem in MediaWiki, which is case-sensitivity. This can actually be fixed in Search (with a different API), which I've logged as a new task. However, the case-sensitivity in things like pages and categories is a pain. I will look more into this, as I am sure there is some way to get this going better, if only some regular bots that can auto-correct capitalization errors. I've logged this also as a separate task to look into. --Sysadmin (talk) 13:38, 23 April 2017 (UTC)
restoring items from accidental mass-delete
hi; can we have an update, & e.t.a. for restoring the content lost in the recent unintentional mass-delete, please? :) we still don't know exactly how much is gone, & recreating is a lot of work; also frustrating. as well as the lost content, it takes a lot of time to do up a "proper" complete biblio-page for an author. (& idk abt the other & unknown lost pages, but the mencken & churchill pages were pretty decent) -- Lx 121 (talk) 22:13, 4 May 2017 (UTC)
- Sorry for delay on this, I've not been able to spend time here the last week. To be frank, the new backup process is not fully in place. That will be corrected in the next few days. I understand the frustration. Will advise as info is available. --Sysadmin (talk) 19:00, 7 May 2017 (UTC)
please could we get the biblio-pages for churchill, mencken, & victor hugo restored from whatever most-recent backup there is, asap? it's really a lot of work to re-create those pages, especially once they are "complete" (full biblio, full links on & off -wiki; including links to off-wiki content). that's at least an hour's work for me, as well as an hour for simon. not to mention how frustrating it is having to redo all the work, yet again! xD & (>__<) Lx 121 (talk) 18:50, 16 May 2017 (UTC)
biblio.wiki SSL Cert issue - RESOLVED
- Hi @Lx 121: what is the error message? Currently wikilivres.ca is still the primary site, but biblio.wiki SSL cert should be working. Github has been moved to Gitlab: https://gitlab.com/Sysadmin/bibliowiki/issues --Sysadmin (talk) 16:25, 22 May 2017 (UTC)
- status page works fine, or seems to. but when i try to go to just plain biblio.wiki i get this:
- Your connection is not secure. The owner of biblio.wiki has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website. Learn more… Report errors like this to help Mozilla identify and block malicious sites. biblio.wiki uses an invalid security certificate. The certificate is only valid for the following names: wiki.classics.io, wikilivres.ca, www.wikilivres.ca Error code: SSL_ERROR_BAD_CERT_DOMAIN
- help/infolink from error msg: https://support.mozilla.org/en-US/kb/what-does-your-connection-is-not-secure-mean --Lx 121 (talk) 17:34, 22 May 2017 (UTC)
- Hi @Lx 121:, thanks for the info. The biblio.wiki domain redirects to wikilivres.ca (because the MediaWiki install controls redirection), but as you discovered, if you just replace a page url on wikilivres.ca with the biblio.wiki domain (but preserve the filename part), then it generates an error. I could have sworn I had already installed/configured the cert, but I had not. I've done so now. The error message should no longer persist. When it comes time to switch domains, it is a matter of substituting two lines in httpd.conf and one in LocalSettings.php. --Sysadmin (talk) 16:15, 23 May 2017 (UTC)
Index and Page Namespaces - Open Task
- hello, & welcome! :)
- can you explain the problem more thoroughly, please?
- (also: we may need you help in translating the chinese side, to fix it)
- Lx 121 (talk) 07:23, 8 June 2017 (UTC)
- wikisource:zh:Index:Manifesto of the Communist Party, translated by Bo Gu.pdf is considered copyright-restricted in the USA even in the public domain in Greater China and Canada with 1946 death of the translator and posthumous publication in 1949. I cannot import it or its related pages.Jusjih (talk) 01:44, 13 June 2017 (UTC)
- Yes, I comfirm the problem. The import of file with "Index" namespace causes the error: The content model 'proofread-index' is not registered on this wiki. See https://www.mediawiki.org/wiki/Content_handlers to find out which extensions handle this content model. There is possibility to import pages only without "index". So I impoted them and created index page manually, see: Index:Manifesto of the Communist Party, translated by Bo Gu.pdf. Maybe it is because there are on wikilivres and on wikisource different numbers of namespaces of Index: and Page: and others connected with proofread extension (see also: ) and the import is puzzled what to do? Electron ツ ➧☎ 23:52, 13 June 2017 (UTC)
Website Space Limitations Roadmap
Currently we have about 30gb of space. This cannot all be used, as when there is around 2gb left, the database will not resize itself. Also, any backup that would make a copy before export ofsite would need to be half the size in order to work, which means something like 14gb max usable space for a functioning site, but closer to 12gb.
This model can be much improved when using Amazon EC2/S3 including elastic store backups. This means that backups happen as snapshots to a backup file rather than needing to duplicate/compress the data first. The price can be managed as well, but before we migrate from the current host, it would be best to wait until Amazon Lightsail is available in the Canada Central region (currently not available). If lightsail is not available by the end of 2017, we should migrate anyway to allow for better filesystem management, and overall management. The current host SSDnodes has a bit too much downtime for my liking (several hours every month or so). --Sysadmin (talk) 13:23, 3 July 2017 (UTC)
bug report: database search error - FIXED
search is failing a lot right now (but not QUITE everytime, for everything; searching 'laura worked, but 'sinclair lewis' did not, nor lewis sinclair, nor 'x'). i keep getting error message like this: A database query error has occurred. This may indicate a bug in the software.[WWhgmgMKe5ykigN2gRp8hwAAAA8] 2017-07-14 06:11:38: Fatal exception of type "DBQueryError" --Lx 121 (talk) 06:18, 14 July 2017 (UTC)
- Hi @Lx 121:. I can confirm the error. I have run maintenance scripts and also restart the servers, but the error persists. I will log this as a task with high priority. More information as it becomes available. --Sysadmin (talk) 08:38, 14 July 2017 (UTC)
Imported scripts from Wikisource in Common.js
Googlebot complains about not being able to process pages correctly (because it is blocked by Wikisource for certain assets), in particular:
Unless there is some reason, it would make sense to simply duplicate these scripts locally at Bibliowiki and run them locally. Any thoughts/history on this? --Sysadmin (talk) 11:40, 15 July 2017 (UTC)
- Please let me know what behavior is not working as expected. Autoconfirmed caused a lot of extra work and trouble in the past, for new-ish users. Is Autoconfirmed supposed to help stop spam? Are certain pages supposed to be protected from new users? I need more information, please, as to expected behavior and unexpected behavior. --Sysadmin (talk) 04:00, 17 July 2017 (UTC)
- Well it can help stop spam and vandalism. It is a protection level between "allow all" and "allowe admins only". See autoconfirmed (and extended confirmed bellow - as we have this on German WP as well), and we have it in the protection options here, see MediaWiki:Protect-level-autoconfirmed. When a page is beeing vandalized - just like User:K67y in the past, so I can protect it with "allow autoconfirmed users" that meanas: User K67y can edit it, but a new user cannot. I tried to protect it (and Zephyrus as well) but it doesn't work. The next protection level "allow admins only" would cause that User:K67y can edit it neither. -jkb- (talk) 09:15, 17 July 2017 (UTC)
- Also: the most templates (main pages as well) etc. should be protected on this level to avoid sudden and mass vandalism on hundreds of pages. -jkb- (talk) 10:39, 17 July 2017 (UTC)
- Hello Jeff, very shortly as I leave tommorow for a fortnight approx for the nice swiss country :-) ... We do not have sudden and mass vandalism here at present, but we had a huge ampount of it some time ago: now, this domain is quite new and it is the question of time when it comes. It is or it is not difficult to revert it - but with the proposed level protection a great part of such accounts will not try it (or, the had to wait for some 4 days and make some edits first - no immediate succes, so the will not do it). And, it is the normally protection level on all projects of the WMF. Cheers -jkb- (talk) 21:22, 27 July 2017 (UTC)
- I'll look into checkuser again, I don't recall why it was turned off (or just didn't work when I tried to enable it). I agree we need better anti-vandalism in place. I'm not convinced about autoconfirm as the answer, since the impact is also on non-vandals. I'll revisit the checklist of antispam stuff to do. I think we were about halfway through the process. Enjoy Switzerland! --Sysadmin (talk) 11:21, 12 August 2017 (UTC)
creation of new accounts is suspended?
paraphrasing but: "the creation of new accounts has been suspended, due to technical issues"
what's up with that? & for how long? o__0
- My guess is that this is the (unhelpful) error message when the database gets a wedgie (technical term). I've kicked it and it seems to allow new account creation (as it should). --Sysadmin (talk) 11:18, 12 August 2017 (UTC)
- I am afraid that pdf format is not supported on this wiki, yet. The same is with -> Index:Manifesto of the Communist Party, translated by Bo Gu.pdf. Electron ツ ➧☎ 08:45, 6 August 2017 (UTC)
- I've looked into this error message and it is the result of a failure in indexing the document. This kind of failure is not uncommon, but not being fixed by Mediawiki. See for example the various references to the error message from this search: . Try uploading a different version of the work (a different PDF or some other file type). This doesn't affect all PDFs as far as I am aware. --Sysadmin (talk) 06:33, 29 December 2017 (UTC)
Delete revisions right
- Do you know how/where to change those rights? Happy to oblige but do not know how/where to make a change. --Sysadmin (talk) 03:30, 27 October 2017 (UTC)
Downtime on 23-24 November
Hi folks, there was intermittant downtime for Bibliowiki on 23-24 November. This is due to the hosting companies networks (the server itself was fine, but network routes were disrupted). Our hosting people are cheap, but this kind of thing has happened before with these guys. A more reliable system will cost about 2x what we currently pay. I'm willing to carry that additional cost to get a better system in place (use of Amazon EC2 in the Montreal location). The current average of $10/mo in contributions currently covers our (very inexepensive) hosting costs, but with cheap, comes a lack of reliability. --Sysadmin (talk) 03:10, 24 November 2017 (UTC)
Downtime 07 Jan 2017
Our host SSDNodes alerted us to a security issue and need to patch the server.
- 10:07 ICT (GMT+7) - Notification via email - 10:15 ICT (GMT+7) - Bibliowiki becomes unavailable - 10:39 ICT (GMT+7) - Bibliowiki becomes available
Here is the text of the email notification:
- SSD Nodes Engineers have been notified of a security vulnerability affecting your server(s). Due to the nature of this vulnerability and the components which are affected, a kernel update and reboot is required. OpenVZ released a kernel update today.
- We will be rebooting your server shortly and expect minimal downtime. The process will involve suspending your server's memory, which keeps all processes intact and running after the reboot is completed. In some rare cases, your server won't properly suspend and will be temporarily shut down and booted back online.
- We apologize for the late notice, but due to the critical nature of these vulnerabilities we must act quickly to apply updates and protect our customers.
- You can learn more here: https://access.redhat.com/errata/RHSA-2018:0008
Ongoing slowdown/errors 09 Jan
- Back up at the moment, but unsure if this is temporary. Will continue to monitor. --Sysadmin (talk) 05:40, 9 January 2018 (UTC)
Database error on Special:Search - FIXED
Special:Search dosn't work properly. If I try find eg. "xyz" it produces something like this: Database error A database query error has occurred. This may indicate a bug in the software.[WlYMBQGfwmRg-KB4bw@hogAAAAE] 2018-01-10 12:50:13: Fatal exception of type "DBQueryError" Electron ツ ➧☎ 12:52, 10 January 2018 (UTC)
- Reproduced. I did a search for Tolkein and got:
- A database query error has occurred. This may indicate a bug in the software.
[WlvM7lgMiStrTXWpTTDqdgAAAAM] 2018-01-14 21:34:38: Fatal exception of type "DBQueryError"
- A database query error has occurred. This may indicate a bug in the software.
- Then I went to Tolkein (which is a redlink at the moment) and clicked thru the text which reads "You can search for this page title in other pages":
- A database query error has occurred. This may indicate a bug in the software.
[WlvNI3x6J3SLA8Jkki@N-AAAAAA] 2018-01-14 21:35:31: Fatal exception of type "DBQueryError"
- A database query error has occurred. This may indicate a bug in the software.
- Any idea what is happening, how to fix it, or an ETA? Koavf (talk) 21:40, 14 January 2018 (UTC)
- Maybe this can help -> DBQueryError when I try to search for anything on test Wiki Electron ツ ➧☎ 23:17, 14 January 2018 (UTC)
Problem with pages import
Special:Import dosn't work properly. Usually I must try 3 times to upload the file to import takes affect. Usually it do nothing after file's upload. Sometimes it produces the warning like this:
A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? Query: INSERT IGNORE INTO `page` (page_id,page_namespace,page_title,page_restrictions,page_is_redirect,page_is_new,page_random,page_touched,page_latest,page_len) VALUES (NULL,'0','Wyspa_błądząca',,'0','1','0.227220419957','20180111231106','0','0') Function: WikiPage::insertOn Error: 1205 Lock wait timeout exceeded; try restarting transaction (localhost)
- I'm not sure the issue, but also, I'm not sure why this is being used at all (what is being imported?). I will need a copy of the file(s) that are trying to be uploaded in order to duplicate the error/troubleshoot. Email firstname.lastname@example.org the file(s). Please advise. --Sysadmin (talk) 04:13, 18 January 2018 (UTC)
Wiki Platform Change
Hi folks, Mediawiki is basically impossible to maintain (unless funded by the WikiMedia Foundation), and so we need something better, faster, cheaper, more up-to-date, more lightweight, and of course meeting all our other needs, while maintaining an identity as a wiki.
From what I can tell, there are two options:
- I have no experiences with them. If they are very different from Mediawiki there will be problem to change our files to meet new requirements. To say the truth I am to old to change... And I do not want it. Electron ツ ➧☎ 18:07, 12 January 2018 (UTC)
- DokuWiki is not appropriate to publish texts. It seems that you want to change totally the politics of bibliowiki. This is a very bad idea. El Verdugo (talk) 07:41, 13 January 2018 (UTC)