Then some minutes of normality. Then, again, the error 503:

Our servers are having problems at the moment. Please try again in a few minutes. There may be additional information on our Facebook and Twitter pages.

Please provide the details below if you report this error to the system administrators via https://phabricator.miraheze.org:

Error 503 Backend fetch failed, forwarded for 83.247.102.164, 127.0.0.1 (Varnish XID 1737850) via cp1 at Fri, 07 Jul 2017 08:52:38 GMT.

And after one of two minutes back to normal.

Yes, issues are still intermittent, but still should be looked at.

Had this error on my wiki in the once in the past week. As Reception said the error isn't as common as it was and sometimes the wiki just magically comes back out from the 503 errors. Can be a pain sometimes but manageable.

In ITIL-terms: there is a "problem" underlying and causing the incidents. I too had some 503 errors on yesterday 15th of july. Happily, in one or two minutes Mediawiki turns back to normal functioning.

Happened again now.

I don't know how varnish works but it naturally balances itself well. Unfortunately it's not aware of a fairly heavy process on mw1 which means varnish RR won't work.

Unsure if varnish has a weighted system.

I've been experiencing this for well over an hour today when attempting to access my own wiki sea.miraheze.org, or the meta wiki. The error message contains:

Error 503 Backend fetch failed, forwarded for 88.202.151.90, 127.0.0.1 (Varnish XID 3706769) via cp1 at Wed, 04 Oct 2017 11:16:23 GMT.

We are aware of the situation and we think we identified the cause (puppet1), but we currently have no sysadmins with access to puppet1 available, so we need to wait for one.

Error is due to db2 disk space. The temporary solution is dropping dbs in deleted.dblist.

UPDATE: I can now see the wikis :-)

I been trying to create articles but I been seeing Error code 503

In T1979#106378, @Zcook1052 wrote:

I been trying to create articles but I been seeing Error code 503

We're aware of the warning. It appears that the system is undergoing maintenance. It should be fixed in about an minutes or hour. Sorry for the inconvenience.

We should be back once mysql has finished booting back up, please open a new ticket though next time.

I been trying to create an article of NASCAR Xfinity Series but I been seeing this error but I been trying to see it 10 times

In T1979#110570, @Zcook1052 wrote:

I been trying to create an article of NASCAR Xfinity Series but I been seeing this error but I been trying to see it 10 times

please open a new ticket

This is serious
503 Backend fetch failed
Our servers are having issues at the moment.

In T1979#110743, @Zcook1052 wrote:

This is serious
503 Backend fetch failed
Our servers are having issues at the moment.

Per our twitter, which shows on the 503 page, we know but please also open a new ticket rather than using very old ones.

This error is getting on my nerves

In T1979#110751, @Zcook1052 wrote:

This error is getting on my nerves

Please report them in a new ticket when they happen. This one is tracked at https://phabricator.miraheze.org/T5675

This error is getting on my nerves, when are you gonna get it fixed?

In T1979#110756, @Zcook1052 wrote:

This error is getting on my nerves, when are you gonna get it fixed?

We are working on the incident now. Please remain calm.

This error has been popping up one hundred times 😡

In T1979#110758, @Zcook1052 wrote:

This error has been popping up one hundred times 😡

We work as hard as we can. Please avoid letting frustrations get to you.

Can you get it fixed now, I don't want to wait

This error is getting on my nerves, How long until this error is resolved?

In T1979#110761, @Zcook1052 wrote:

This error is getting on my nerves, How long until this error is resolved?

As soon as we can fix it we will, please allow us to handle the incident.

Can you fix it in one hour?

In T1979#110763, @Zcook1052 wrote:

Can you fix it in one hour?

You can not demand we fix it in a set time. We are working as hard as we can to resolve the incident as soon as possible.

This error is getting on my nerves and you need to get it fixed NOW!!!!!!!!!!!