Page MenuHomePhabricator

UNRECOVERABLE FATAL ERROR after upgrading to 2016 Week 27
Closed, ResolvedPublic

Description

>>> UNRECOVERABLE FATAL ERROR <<<

Call to undefined method PHUIHeaderView::setActionListID()

/opt/phabricator/src/view/phui/PHUITwoColumnView.php:117


┻━┻ ︵ ¯\_(ツ)_/¯ ︵ ┻━┻

Looking in to this now. This is the first failed upgrade we've encountered.

Versions:

phabricator 58375fa9e6db4a389fd6029ee1ad14ddb0dc9e90 (Sat, Jul 2)
arcanist f1c45a3323ae20eefe29c0a22c7923fe8b151bbf (Fri, Jul 1)
phutil 119e5b12ba068b6554918f3924a449cbaabe1d14 (Fri, Jul 1)

Event Timeline

Getting the following when I visit differential/:

Exception
Bad getter call: getStatusIcon

Just rebooted apache once more and things are looking better.

epriestley claimed this task.

Oh, or Apache.

These errors are pretty typical of things not being fully restarted, so I suspect you'll be in the clear now.

Let us know if you run into anything else.

Thanks for quick response; hadn't seen this before so couldn't tell how serious the errors were.

Is it normal to see our feed re-circulating old diffs?

Ah, I found the problem in our upgrade script. We run our upgrade in the following order:

  • Stop daemons
  • Stop apache
  • Run apt-get upgrade
  • Update phabricator
  • Reboot apache
  • Start daemons

Looks like apache had an update, so when apt-get performed the upgrade it rebooted the apache server.

Ah, interesting.

There was a relatively recent change to make Phabricator discover commits which are only reachable from tags and refs. As it discovers these commits, it will treat them like new commits and publish feed stories about them. This is a one-time event, but a few installs have a lot of tag-reachable commits for whatever reason. You can find a bit more discussion in T11188, and details about the change in T9028 and T6878.

If you have a lot of tag-only or ref-only commits, you can put affected repositories into "importing" mode until everything catches up:

phabricator/ $ ./bin/repository mark-imported --mark-not-imported rXYZ ...

That should silence them until the new imports finish.

Ok; will let it do its thing then.

Are there adverse effects to putting a repository into "importing" mode?

Only that any legitimate commits pushed until things catch up will also be ignored. The repository will automatically leave the mode once everything finishes.

"Ignored" in the sense of: no publishing, no herald rules, no audit triggers. Not, like, "they won't not exist".

they won't not exist

Er, I mean won't not not exist.

Got it. Thank you! I just started the reindexing operations recommended in this release so I may leave things be 'til that finishes.