Jump to content
RP286

docwiki.embarcadero.com is not working

Recommended Posts

23 minutes ago, David Heffernan said:

Perhaps they don't know it's broken?

I can assure they do know.

  • Like 1

Share this post


Link to post

If this problem was with an online bank, Idera would be out of business.

Share this post


Link to post
27 minutes ago, Lars Fosdal said:

Delivery times for new in-house HW can be appalling these days. 

Go cloud.

Cloud is just someone else's computer and those fail, too. 

  • Like 4
  • Thanks 1

Share this post


Link to post
1 hour ago, David Heffernan said:

Perhaps they don't know it's broken?

There are several reports at their quality Portal

Share this post


Link to post
Guest

dockwiki embarcadero working now! rad11 help ok

 

... not at all  😂

Edited by Guest

Share this post


Link to post
27 minutes ago, joaodanet2018 said:

dockwiki embarcadero working now! rad11 help ok

 

... not at all  😂

Hold your horses.

 

I just check a number of pages I have BM in my browser. Most are OK but not all.

Share this post


Link to post

For some pages it works: refresh the page after the error.

Share this post


Link to post
11 minutes ago, Stano said:

For some pages it works: refresh the page after the error.

Thanks for the tip.

For some pages, a refresh does the trick. For others I found multiple clicks on the refresh button eventually results in the desired page. However, I found one page that just is not ready for prime time: https://docwiki.embarcadero.com/CodeExamples/Seattle/en/Main_Page

Share this post


Link to post
Quote

Not Found

The requested URL /codeExamples/Sydney/en/DateUtils_(Delphi) was not found on this server.

 

 

I guess 50% back.

 

The accept cookie text should be another concern on viewing blog.  https://blogs.embarcadero.com/

 

The cookie text reads 

Quote

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.

 

Clicking on do not sell my personal information returns: "You really want to opt out."  Hopefully this is not implicit when using the help.   Since I have a subscription they have more personal information to sell. 

 

  • Like 1

Share this post


Link to post

Not sure if this makes any difference, but if I access site from US I get partial results, some show up some have error. Using VPN from other countries works 99%, rarely, but every now and then the error shows up.

Share this post


Link to post

It's amazing how low expectations have become.

 

"It sometimes works, sort of, if you refresh the page a few times"

 

"You might get better results by spoofing your IP with a VPN"

  • Sad 1

Share this post


Link to post

It's flaky. Again.

I archived https://archive.ph/TIWRy from https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Main_Page:

[8c1240dd3d6ee2e766657d26] /RADStudio/Alexandria/en/Main_Page Wikimedia\Rdbms\DBQueryError from line 1457 of /var/www/html/shared/BaseWiki31/includes/libs/rdbms/database/Database.php: A connection error occured.
Query: SELECT lc_value FROM `rad_alexandria_en_l10n_cache` WHERE lc_lang = 'en' AND lc_key = 'preload' LIMIT 1
Function: LCStoreDB::get
Error: 2006 MySQL server has gone away (etnadocwikidb01)
Backtrace:
#0 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/database/Database.php(1427): Wikimedia\Rdbms\Database->makeQueryException(string, integer, string, string)
#1 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/database/Database.php(1200): Wikimedia\Rdbms\Database->reportQueryError(string, integer, string, string, boolean)
#2 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/database/Database.php(1653): Wikimedia\Rdbms\Database->query(string, string)
#3 /var/www/html/shared/BaseWiki31/includes/libs/rdbms/database/Database.php(1479): Wikimedia\Rdbms\Database->select(string, string, array, string, array, array)
#4 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LCStoreDB.php(52): Wikimedia\Rdbms\Database->selectField(string, string, array, string)
#5 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(357): LCStoreDB->get(string, string)
#6 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(271): LocalisationCache->loadItem(string, string)
#7 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(471): LocalisationCache->getItem(string, string)
#8 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(334): LocalisationCache->initLanguage(string)
#9 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(371): LocalisationCache->loadItem(string, string)
#10 /var/www/html/shared/BaseWiki31/includes/cache/localisation/LocalisationCache.php(292): LocalisationCache->loadSubitem(string, string, string)
#11 /var/www/html/shared/BaseWiki31/languages/Language.php(3177): LocalisationCache->getSubitem(string, string, string)
#12 /var/www/html/shared/BaseWiki31/includes/MagicWord.php(352): Language->getMagic(MagicWord)
#13 /var/www/html/shared/BaseWiki31/includes/MagicWord.php(280): MagicWord->load(string)
#14 /var/www/html/shared/BaseWiki31/includes/parser/Parser.php(4848): MagicWord::get(string)
#15 /var/www/html/shared/BaseWiki31/extensions/TreeAndMenu/TreeAndMenu_body.php(24): Parser->setFunctionHook(string, array)
#16 /var/www/html/shared/BaseWiki31/includes/Setup.php(948): TreeAndMenu->setup()
#17 /var/www/html/shared/BaseWiki31/includes/WebStart.php(88): require_once(string)
#18 /var/www/html/shared/BaseWiki31/index.php(39): require(string)
#19 {main}

 

The main page gives a HTTP 404, but also loads https://docwiki.embarcadero.com/RADStudio/Alexandria/e/load.php?debug=false&lang=en&modules=ext.fancytree%2Csuckerfish|jquery.accessKeyLabel%2CcheckboxShiftClick%2Cclient%2Ccookie%2CgetAttrs%2ChighlightText%2Cmw-jump%2Csuggestions%2CtabIndex%2Cthrottle-debounce|mediawiki.RegExp%2Capi%2Cnotify%2CsearchSuggest%2Cstorage%2Cuser|mediawiki.api.user|mediawiki.page.ready%2Cstartup|site|skins.duobook2.js&skin=duobook2&version=149306z which delivers a nice 500.

 

 

A long time ago I made https://stats.uptimerobot.com/3yP3quwNW for monitoring http(s) status in the hope they would be watching it.

 

That one monitors the home page, but maybe I should have it monitor a sub-page like the main page for XE8 or so, as this one also gives a nice 500 error: https://docwiki.embarcadero.com/RADStudio/XE8/en/Main_Page

 

On the other hand: from a bigger organisation like Idera, one would exepct more IT infrastructure competence (hello 24x7 monitoring!) than back in the days when just the core CodeGear DevRel team was keeping the documentation sites up and running (and by using Delphi web front-end plus InterBase database back-end provided valuable quality feed back to the R&D team).

Guessing from `BaseWiki31` I guessed they might still be on MediaWiki 1.31 which was an LTS version, but is unsupported now and has been replaced by 1.35 LTS.

My guess was right as in https://docwiki.embarcadero.com/ (archived as https://web.archive.org/web/20220217084835/http://docwiki.embarcadero.com/) you see this:

 

	<meta name="generator" content="MediaWiki 1.31.1">

MediaWiki versions are at:

 

https://www.mediawiki.org/wiki/MediaWiki_1.31

https://www.mediawiki.org/wiki/MediaWiki_1.35

https://www.mediawiki.org/wiki/Version_lifecycle

Back in the days they were keen in advocating life cycle management. Maybe time to show they indeed still understand what that means.

 

--jeroen

  • Thanks 1

Share this post


Link to post
2 hours ago, jeroenp said:

It's flaky. Again.

 

 

It says it cannot connect to MySQL database server, so the problem would probably happen with newer MediaWiki, too.

Share this post


Link to post
59 minutes ago, Vandrovnik said:

 

It says it cannot connect to MySQL database server, so the problem would probably happen with newer MediaWiki, too.

The MySQL uptime and the connection to are still responsibilities of the IT department.

Anyway: made it UptimeRobot watch a deeper link which is now available at https://stats.uptimerobot.com/3yP3quwNW/780058619 for anyone to keep an eye on.

Luckily, https://web.archive.org and https://archive.is have a lot of pages archived.

  • Thanks 1

Share this post


Link to post

That monitor is nice but how can these numbers be correct?

 

image.thumb.png.aba0b6b0f6a348dbe64881cc845314d2.png

 

 

Share this post


Link to post
1 hour ago, DJof SD said:

That monitor is nice but how can these numbers be correct?

As the free plan is limited to 50 entries, I redirected an existing monitor to the new URL () then turned it on. My guess is that even while the old URL was turned off off, it was counted as "up", and reflected in these numbers.

 

The numbers are already going down, as while writing it is this from the ~53% you noticed:

Quote

39.050%

Last 24 hours

39.050%

Last 7 days

39.050%

Last 30 days

39.050%

Last 90 days

 

--jeroen

  • Thanks 1

Share this post


Link to post

Thanks for the explanation.

 

What I thought odd was the exact same percentages were posted for all 4 time periods. I would have guessed all 4 values would have been different. But I'll assume that the free plan is the limiting factor and the explanation for that sameness being seen.

 

Share this post


Link to post
2 hours ago, DJof SD said:

Thanks for the explanation.

 

What I thought odd was the exact same percentages were posted for all 4 time periods. I would have guessed all 4 values would have been different. But I'll assume that the free plan is the limiting factor and the explanation for that sameness being seen.

 

It is indeed confusing. In 30 days it should all be "clear".

 

 

When you look at the event history of that monitoring page (I saved it at https://archive.ph/RNeuP) and you see that it is oscillating between down and up. Since the free monitoring is only every 5 minutes, the oscillation appears a very regular interval which might not be that regular.

Being up part of the time, that will also likely influence these numbers.

 

 

I also searched and found back where I originally created the monitoring pages https://stats.uptimerobot.com/3yP3quwNW (there are close to 50 of them, but I did not keep track of which sites went permanently down as there is no clear documented Embarcadero provided list of them).
The original article was at https://wiert.me/2022/01/19/some-uptime-monitoring-tools-that-are-still-free-and-understand-more-than-http-https which I started writing at 20210528. The monitors themselves are way older: I tracked them back in my email archive to February 2018, so slightly more than 4 years ago.

 

 

 

Share this post


Link to post

At the end it could be just a simple explanation, like with Bookmarks plugin: one of the managers is personally responsible and they would rather have current situation then to explain why someone else could be better suited to sort out the issue and manage in the future.

 

Probably someone just needs to press reset button on the server.

Share this post


Link to post
8 hours ago, Mike Torrettinni said:

Probably someone just needs to press reset button on the server.

The person responsible is sitting in Australia, the access to the server is only available during business hours in California and needs the approval from somebody in Europe. And the server does not have a reset button because that would be a security risk. 😉

  • Haha 5

Share this post


Link to post

16th during the webinar we should all ask the question whenever the future of Delphi includes some kind of online documentation or not. I believe that will be the perfect place to ask!

  • Like 2

Share this post


Link to post
Guest
This topic is now closed to further replies.

×