Page MenuHomePhabricator

test.orain.org is unsupported
Closed, ResolvedPublic

Description

All builds are failing with:

python pwb.py generate_family_file 'https://test.orain.org/' oraintest
NOTE: 'user-config.py' was not found!
Generating family file from https://test.orain.org/
WARNING: Http response status 522
Traceback (most recent call last):
  File "pwb.py", line 239, in <module>
    if not main():
  File "pwb.py", line 233, in main
    run_python_file(filename, [filename] + args, argvu, file_package)
  File "pwb.py", line 111, in run_python_file
    main_mod.__dict__)
  File "./generate_family_file.py", line 205, in <module>
    FamilyFileGenerator(*sys.argv[1:]).run()
  File "./generate_family_file.py", line 64, in run
    w = Wiki(self.base_url)
  File "./pywikibot/site_detect.py", line 89, in __init__
    raise RuntimeError('Unsupported url: {0}'.format(self.fromurl))
RuntimeError: Unsupported url: https://test.orain.org/
<class 'RuntimeError'>
CRITICAL: Closing network session.

https://travis-ci.org/wikimedia/pywikibot-core/jobs/80034585#L226

Event Timeline

jayvdb raised the priority of this task from to Needs Triage.
jayvdb updated the task description. (Show Details)
jayvdb added a project: Pywikibot-tests.
jayvdb subscribed.

Their server is down ATM, iirc. isup reports it is dead too.

Orain op here

I've used puwikibot to upload files to test.orain.org and bog.orain.org

This may have just been because our servers were down a lot of yesterday (and tbh I haven't checked if they're up right now..)

jayvdb set Security to None.
jayvdb claimed this task.

Fixed in latest test build. \o/

XZise removed jayvdb as the assignee of this task.Sep 13 2015, 2:26 PM

Failing again with HTTP 522

@jayvdb Orain's loadbalancer is currently being null routed by our host after cloud flare decided to pass a long 1GB of uncached requests to our servers in an hour.

Hoping after the null route that changing some settings can prevent this from happening again.

No worries.

If this issue is with orain 522ing the task might be invalid? I'm not sure but if it's just an issue with our site being down that's not a problem with the code. The site is actuall erroring.

If this issue is with orain 522ing the task might be invalid? I'm not sure but if it's just an issue with our site being down that's not a problem with the code. The site is actuall erroring.

This task is mostly tracking that our test is failing. It can be re-closed when the problem is resolved on your side.

There is also a slight problem with our code, that it is interpreting 522 as 'not supported', when it should give a better error message.

Oh okay I understand now. Well a better error message would be useful, should I close this when our site is working? (Like i said, I've used pwb with Orain testwiki)

Ps sorry for being new to phabricator :p

Looking good again; *fingers crossed*

Yep, FYI it looked like Orain got ddosed a couple of times over the weekened

@Addshore I raised the security level for our domain on CF. Might wanna take a look.

Also glad it appears to be up

Oh okay I understand now. Well a better error message would be useful, should I close this when our site is working? (Like i said, I've used pwb with Orain testwiki)

Afaik this should be partially an Orain bug, as the server responds with a 522 error code. Is there an Orain project?

Oh okay I understand now. Well a better error message would be useful, should I close this when our site is working? (Like i said, I've used pwb with Orain testwiki)

Afaik this should be partially an Orain bug, as the server responds with a 522 error code. Is there an Orain project?

On Phabricator? Not sure if there's an Orain project. I'm not sure if this was actually a bug though? The 522 HTTP error code was valid. Connections timed out because our server was taken offline by our host :P

Wouldn't mind there being a project for it though if others felt the need.

It could be considered a bug on your side, because it was offline. Now I'm not sure what @jayvdb intended with this bug? Raise awareness for you Orain people or find a solution on our side to avoid that the test fail. After all it's considered a failure of our bot (for Travis) that your site as down (not that I blame Orain for it more like that we need to prevent failures when it's not our fault).

Ah true. Maybe something in Travis or your script could check the HTTP code? Pretty sure 200 would be optimal but some things (timeout, for instance) are likely not your fault. Maybe things like 301 etc should still error but gateway / site timeout shouldn't.