When I try to access https://phab-01.wmflabs.org, it returns a 502 error. I tried a hard refresh, but no success. I was using Google Chrome (49.0.2623.112 (Official Build) m (32-bit)) in a Microsoft Windows XP 5.1.2600 (Service Pack 3) computer.
|Invalid||None||T127617 Upgrade phab-01.wmflabs.org|
|Resolved||Paladox||T137270 https://phab-01.wmflabs.org returns a core exception|
|Resolved||mmodell||T125666 can't log in to phab-01.eqiad.wmflabs|
I actually looked a bit deeper into phab-02, it turns out the problems were manyfold:
- It had a puppetmaster set to 'deploy.phabricator.eqiad.wmflabs' which is a host that does not exist
- It now fails puppet due to something scap related
I think if you remove the roles it has from it, it should work?
(Salt was able to get access to it)
phab-02 to phab-04 are working, but not phab-01. The error message was:
[Core Exception/PhutilBootloaderException] Include of extension file '/srv/deployment/phabricator/deployment/phabricator/src/extensions/LDAPUserpageCustomField.php' failed!
Re opening this.
I tried ssh into it but failed I looked at the website and it showed http 500 error so I rebooted it but now it failed to reboot.
This instance needs upgrading to a medium please.
Resolving this now.
I had help with setting some things by @Luke081515
Please reopen if the problems continue.
You will notice a performance increase plus it will be more stable since we chose a large instance since daemons can cause it to stop working on a small instance.
Uptime will also improve now.
@Krenair ive deleted phab-02 and recreated as phab-05. The url is still the same but just running under a different instance.
Reason is because phab-02 is using port 222 and should be using port 22. Recreating didn't help either just kept setting it at port 222. So I will wait a see if I can recreate phab-02 or not.
@Paladox Phab-02 doesn't have the same puppet class assigned as all the other instances. It is using role::phabricator::labs::diffusion instead of role::phabricator::labs to test potential Diffusion changes that would include hosting a git server on port 22. So, yes, SSH is supposed to be hosted on port 222. Whether it is still topical is another issue.
You shouldn't be removing or modifying machines you don't fully understand the purpose or setup of.