# Upgrading to GitLab Mattermost in GitLab 8.9

**URL:** <https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735>\
**Category:** Troubleshooting\
**Created:** [June 21, 2016, 10:53pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735 "2016-06-21T22:53:20Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [June 21, 2016, 10:53pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/1 "2016-06-21T22:53:20Z")

</div>

This is a thread started to help troubleshoot issues with upgrading to GitLab 8.9, which upgrades users to Mattermost 3.1.

If you’re having issues with the automated install, try running:

```auto
sudo -u mattermost -i bash
cd /opt/gitlab/embedded/service/mattermost
/opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30

```

If this doesn’t work, please [post a new topic](https://forum.mattermost.com/c/general/gitlab) to this forum with:

1. A brief description of your issue as title
2. The step on which you’re having issues
3. The relevant portion of the Mattermost log file at `/var/log/gitlab/mattermost/mattermost.log`

To start a new topic, [click this link to the Gitlab Mattermost forum category](https://forum.mattermost.com/c/general/gitlab) then click **New Topic**. See bottom right button in screenshot for an illustration:

 ![](https://us1.discourse-cdn.com/flex020/uploads/mattermost/original/1X/a507c97d7b4bc64f77badad348802df7dd2d14cc.png)

---

<div class="post-metadata">

**Author:** ![manuel](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/manuel/32/307_2.png) [@manuel](https://forum.mattermost.com/u/manuel)\
**Post date:** [June 22, 2016, 11:27am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/2 "2016-06-22T11:27:24Z")

</div>

Thanks for the topic!  
How can i login with a renamed user/account when the login method is GitLab SSO?  
I can’t login to the other teams anymore, because the renamed users/accounts have no credentials like username/passwort.

---

<div class="post-metadata">

**Author:** ![therox](https://avatars.discourse-cdn.com/v4/letter/t/5f9b8f/32.png) [@therox](https://forum.mattermost.com/u/therox)\
**Post date:** [June 22, 2016, 2:46pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/3 "2016-06-22T14:46:46Z")

</div>

Hi. When upgrading gitlab to 8.9 mattermost was not started.  
in /etc/gitlab/gitlab.rbi’ve added  
mattermost[‘db2\_backup\_created’] = true  
mattermost[‘db2\_team\_name’] = “TEAMNAME” with proper teamname.

/var/log/gitlab/mattermost/mattermost.log :

```auto
   [2016/06/22 09:24:03 MSK] [EROR] /havana/town-square: code=404 ip=10.46.2.183
   !!!!Automatic database upgrade failed.!!!

    If you are upgrading from Mattermost v2 to v3
    make sure that you have backed up your database
    and then in /etc/gitlab/gitlab.rb set:

    mattermost['db2_backup_created'] = true
    mattermost['db2_team_name'] = TEAMNAME

    where TEAMNAME is the name of the default team.
    Run gitlab-ctl reconfigure again.
    See: 

    http://docs.gitlab.com/omnibus/gitlab-mattermost/#upgrading-gitlab-mattermost-in-gitlab-8.9 

    for more information.

```

and that’s all.  
I was trying to manual run commands above, but get

```auto
 $ /opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: interface conversion: interface is runtime.errorString, not string
[signal 0xb code=0x1 addr=0x0 pc=0x78090f]

goroutine 1 [running]:
panic(0xcd1aa0, 0xc820140180)
        /usr/local/go/src/runtime/panic.go:481 +0x3e6
main.doLoadConfig.func1(0xc820167d48)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:73 +0x6f
panic(0xccbec0, 0xc8200100e0)
        /usr/local/go/src/runtime/panic.go:443 +0x4e9
github.com/mattermost/platform/utils.TestConnection(0xc820080b00)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/utils/mail.go:82 +0x9f
github.com/mattermost/platform/utils.LoadConfig(0x7fff53bf3794, 0x26)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/utils/config.go:181 +0x10aa
main.doLoadConfig(0x7fff53bf3794, 0x26, 0x0, 0x0)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:76 +0x6a
main.main()
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:84 +0x43

```

Please help.

---

<div class="post-metadata">

**Author:** ![revxx14](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/revxx14/32/104_2.png) [@revxx14](https://forum.mattermost.com/u/revxx14)\
**Post date:** [June 22, 2016, 6:31pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/4 "2016-06-22T18:31:41Z")

</div>

How exactly do I back up the database? I can’t find any documentation other than “just do what you normally do with postgres databases,” but I don’t normally do that kind of thing 😕

---

<div class="post-metadata">

**Author:** ![Korni22](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/korni22/32/761_2.png) [@Korni22](https://forum.mattermost.com/u/Korni22)\
**Post date:** [June 22, 2016, 7:20pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/5 "2016-06-22T19:20:39Z")

</div>

Hey guys!

I’m having trouble upgrading mattermost.

I added the config parameters, ran `apt-get upgrade`, it worked fine but now mattermost won’t start.

The log says:

`Error creating database tables: pq: trigger "truncate_trigger" for relation "teams" already exists`

So I ran

`sudo -u mattermost -i bash cd /opt/gitlab/embedded/service/mattermost /opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30`

Which returned …nothing and did not help.

Any ideas?

---

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [June 23, 2016, 1:53am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/6 "2016-06-23T01:53:49Z")

</div>

Hi @manuel, duplicate accounts are switched to email login, you can use “reset password” to get credentials sent to your email, and you can switch to GitLab SSO under Account Settings \> Security Sign In Method.

---

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [June 23, 2016, 1:57am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/7 "2016-06-23T01:57:20Z")

</div>

Hi @revxx14, try `pg_dump dbname > outfile`, you can just web search for your database type and version to find documentation for backup, for example: [https://www.postgresql.org/docs/9.4/static/backup-dump.html](https://www.postgresql.org/docs/9.4/static/backup-dump.html)

---

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [June 23, 2016, 1:58am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/8 "2016-06-23T01:58:28Z")

</div>

Hi @Korni22, Mattermost doesn’t use database triggers, did you or someone on your team manually modify the Mattermost database to add triggers?

---

<div class="post-metadata">

**Author:** ![Blist](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/blist/32/759_2.png) [@Blist](https://forum.mattermost.com/u/Blist)\
**Post date:** [June 23, 2016, 1:58am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/9 "2016-06-23T01:58:40Z")

</div>

Hi,  
I’ve just update my gitlab installation using apt-get upgrade. My gitlab install work well but the mattermost embedded doesn’t work any more.  
I check log, and mattermost ask me to upgrade the mattermost database.

> [2016/06/22 10:01:12 EDT] [CRIT] The database version of 2.2.0 cannot be automatically upgraded to 3.0 schema  
> [2016/06/22 10:01:12 EDT] [CRIT] You will need to run the command line tool ‘./platform -upgrade\_db\_30’

So i launch this command :

> mattermost@Kalay:/opt/gitlab/embedded/bin$ /opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json -upgrade\_db\_30

> Please see [Mattermost | Secure Collaboration for Technical Teams](http://www.mattermost.org/upgrade-to-3-0/)  
> **WARNING** This upgrade process will be irreversible.  
> Have you performed a database backup? (YES/NO): YES  
> We found 14 teams.  
> datexim  
> …  
> nhb9ns1omtbdxkd8fpfzqcsyre  
> vikings  
> Please pick a primary team from the list above: datexim  
> panic: runtime error: invalid memory address or nil pointer dereference  
> [signal 0xb code=0x1 addr=0x20 pc=0x4a6653]

> goroutine 1 [running]:  
> panic(0xccbec0, 0xc82000e090)  
> /usr/local/go/src/runtime/panic.go:481 +0x3e6  
> html/template.(\*Template).lookupAndEscapeTemplate(0x0, 0xddb800, 0xf, 0x0, 0x0, 0x0)  
> /usr/local/go/src/html/template/template.go:125 +0x63  
> html/template.(\*Template).ExecuteTemplate(0x0, 0x7f90facb4790, 0xc820149f80, 0xddb800, 0xf, 0xcfda40, 0xc820437680, 0x0, 0x0)  
> /usr/local/go/src/html/template/template.go:114 +0x4b  
> [github.com/mattermost/platform/utils.(\*HTMLTemplate).Render](http://github.com/mattermost/platform/utils.(*HTMLTemplate).Render)(0xc820437680, 0x0, 0x0)  
> /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/utils/html.go:98 +0x103  
> main.convertTeamTo30(0xc820407af0, 0x7, 0xc82040e020, 0xc82015f5e8, 0xc82015f5b8, 0xc82015f588, 0x0, 0x0, 0x0)  
> /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:686 +0x2bae  
> main.cmdUpdateDb30()  
> /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:462 +0x2a75  
> main.main()  
> /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:102 +0x9c4

Each time i try to update the mattermost database, the mattermost cli crash … do you have any idea to re-up my mattermost installation ?  
Thanks a lot in advance. best regards, Vianney

---

<div class="post-metadata">

**Author:** ![it33](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/it33/32/3_2.png) [@it33](https://forum.mattermost.com/u/it33)\
**Post date:** [June 23, 2016, 2:27am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/10 "2016-06-23T02:27:48Z")

</div>

Please try running:

```auto
sudo -u mattermost -i bash
cd /opt/gitlab/embedded/service/mattermost
/opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30

```

Let us know what happens?

---

<div class="post-metadata">

**Author:** ![kgyk](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/kgyk/32/762_2.png) [@kgyk](https://forum.mattermost.com/u/kgyk)\
**Post date:** [June 23, 2016, 5:28am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/11 "2016-06-23T05:28:53Z")

</div>

Hi.

I was trying to upgrade mattermost and encounterd the same error as [previous comment 3](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/3).

Following commands were worked on my system (centos 6).

```auto
sudo -u mattermost -i bash
cd /opt/gitlab/embedded/service/mattermost
/opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json -upgrade_db_30

```

Thank you.

---

<div class="post-metadata">

**Author:** ![therox](https://avatars.discourse-cdn.com/v4/letter/t/5f9b8f/32.png) [@therox](https://forum.mattermost.com/u/therox)\
**Post date:** [June 23, 2016, 5:56am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/12 "2016-06-23T05:56:02Z")

</div>

Ok, I’ve found the reason.

It’s all becouse of enabled `mattermost['email_send_email_notifications'] = true` setting in `/etc/gitlab/gitlab.rb`

---

<div class="post-metadata">

**Author:** ![manuel](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/manuel/32/307_2.png) [@manuel](https://forum.mattermost.com/u/manuel)\
**Post date:** [June 23, 2016, 9:27am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/13 "2016-06-23T09:27:32Z")

</div>

@it33, thank you. But…  
The automatic generated email addresses does not exists in the real world. So I can’t reset my password through the UI.  
All migrated email addresses are in this format: ‘[real-email-name]+[mattermost-team-name]@[real-email-domain]’.

---

<div class="post-metadata">

**Author:** ![rsokoll](https://avatars.discourse-cdn.com/v4/letter/r/dfb087/32.png) [@rsokoll](https://forum.mattermost.com/u/rsokoll)\
**Post date:** [June 23, 2016, 9:56am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/14 "2016-06-23T09:56:57Z")

</div>

All I get after picking the primary team:

```
panic: Failed to create index pq: could not create unique index "idx_users_email_unique"

goroutine 1 [running]:
panic(0xb8dd80, 0xc820252880)
        /usr/local/go/src/runtime/panic.go:481 +0x3e6
github.com/mattermost/platform/store.SqlStore.createIndexIfNotExists(0xc8205870e0, 0xc8200211f8, 0x1, 0x1, 0x7f1ef69bd480, 0xc820021218, 0x0, 0x0, 0x0, 0x0, ...)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:511 +0x6df
github.com/mattermost/platform/store.SqlStore.CreateUniqueIndexIfNotExists(0xc8205870e0, 0xc8200211f8, 0x1, 0x1, 0x7f1ef69bd480, 0xc820021218, 0x0, 0x0, 0x0, 0x0, ...)
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:475 +0xba
main.cmdUpdateDb30()
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:516 +0x1fc7
main.main()
        /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:102 +0x9c4
```

---

<div class="post-metadata">

**Author:** ![Korni22](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/korni22/32/761_2.png) [@Korni22](https://forum.mattermost.com/u/Korni22)\
**Post date:** [June 23, 2016, 10:15am UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/15 "2016-06-23T10:15:04Z")

</div>

Hey @it33,

Thanks for replying, it was BDRs fault, but I resolved it!

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![revxx14](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/revxx14/32/104_2.png) [@revxx14](https://forum.mattermost.com/u/revxx14)\
**Post date:** [June 23, 2016, 1:14pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/16 "2016-06-23T13:14:07Z")

</div>

Thanks @it33, but that doesn’t much help. I was able to make _some_ progress with the following command:

```
sudo /opt/gitlab/embedded/bin/pg_dump -U gitlab_mattermost -h /var/opt/gitlab/postgresql -p 5432 mattermost_production > mattermost_production_backup

```

But that returns the error

```
pg_dump: [archiver (db)] connection to database "mattermost_production" failed: FATAL: Peer authentication failed for user "gitlab_mattermost"

```

See my standalone post: [[Solved] How do I back up a GitLab Mattermost database?](https://forum.mattermost.com/t/how-do-i-back-up-the-database/1748/3)

* * *

Tried some more stuff, I found the pg\_hba.conf, and it looks like there’s a peer map, whatever that means. I think that’s what’s causing the error but I don’t know what to do.

–

OMG! I got it. Here’s what I did:

```
sudo -u mattermost -i bash
/opt/gitlab/embedded/bin/pg_dump -U gitlab_mattermost -h /var/opt/gitlab/postgresql -p 5432 mattermost_production > mattermost_production_backup

```

And now I have a backup! Jeez, that was overly difficult.

---

<div class="post-metadata">

**Author:** ![wpostma](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/wpostma/32/669_2.png) [@wpostma](https://forum.mattermost.com/u/wpostma)\
**Post date:** [June 23, 2016, 3:35pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/17 "2016-06-23T15:35:10Z")

</div>

Same thing here. Panic looks like this:

```
2016-06-23_15:11:53.39476 main.main()
2016-06-23_15:11:53.39476 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:104 +0x9c9
2016-06-23_15:11:55.05863 panic: Failed to open sql connection pq: the database system is starting up
2016-06-23_15:11:55.05867
2016-06-23_15:11:55.05868 goroutine 1 [running]:
2016-06-23_15:11:55.05868 panic(0xb8dd80, 0xc8202dd300)
2016-06-23_15:11:55.05869 /usr/local/go/src/runtime/panic.go:481 +0x3e6
2016-06-23_15:11:55.05869 github.com/mattermost/platform/store.setupConnection(0xdb97c0, 0x6, 0xc820135d80, 0x8, 0xc82004efc0, 0x5d, 0xa, 0xa, 0xc8202dcf00, 0x10)
2016-06-23_15:11:55.05870 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:218 +0x894
2016-06-23_15:11:55.05871 github.com/mattermost/platform/store.initConnection(0x41da0f)
2016-06-23_15:11:55.05871 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:63 +0x11b
2016-06-23_15:11:55.05872 github.com/mattermost/platform/store.NewSqlStore(0x0, 0x0)
2016-06-23_15:11:55.05872 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:85 +0x49
2016-06-23_15:11:55.05873 github.com/mattermost/platform/api.NewServer()
2016-06-23_15:11:55.05874 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/api/server.go:36 +0xe8
2016-06-23_15:11:55.05874 main.main()
2016-06-23_15:11:55.05875 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:104 +0x9c9
2016-06-23_15:19:52.39029 panic: Failed to open sql connection pq: the database system is starting up
2016-06-23_15:19:52.39128
2016-06-23_15:19:52.39129 goroutine 1 [running]:
2016-06-23_15:19:52.39129 panic(0xb8dd80, 0xc82040b480)
2016-06-23_15:19:52.39129 /usr/local/go/src/runtime/panic.go:481 +0x3e6
2016-06-23_15:19:52.39130 github.com/mattermost/platform/store.setupConnection(0xdb97c0, 0x6, 0xc82012dd78, 0x8, 0xc82004f020, 0x5d, 0xa, 0xa, 0xc82040ae00, 0x10)
2016-06-23_15:19:52.39130 /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/store/sql_store.go:218 +0x894

```

Is this due to the failed upgrade?

I also tried a clean install and that doesn’t work at all either.

[http://forum.mattermost.com/t/clean-install-of-gitlab-8-9-not-upgrade-enable-mattermost-bad-gateway/1760](http://forum.mattermost.com/t/clean-install-of-gitlab-8-9-not-upgrade-enable-mattermost-bad-gateway/1760)

In my opinion, the whole point of the “omnibus” is that you should be able to turn on Mattermost on a clean installed new system (that has never run a pre-8.9 gitlab) and have it WORK.

---

<div class="post-metadata">

**Author:** ![dnoe](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dnoe](https://forum.mattermost.com/u/dnoe)\
**Post date:** [June 23, 2016, 4:42pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/18 "2016-06-23T16:42:37Z")

</div>

After upgrading to 3.1, I no longer have access to the system console. I have tried running the ./platform command that will add my access back, but I get an error when attempting that.

---

<div class="post-metadata">

**Author:** ![dnoe](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@dnoe](https://forum.mattermost.com/u/dnoe)\
**Post date:** [June 23, 2016, 4:57pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/19 "2016-06-23T16:57:44Z")

</div>

I was able to get mine fixed, by copying the en.json to the directory that the mattermost process runs out of. Hopefully this will help someone.

---

<div class="post-metadata">

**Author:** ![wpostma](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/wpostma/32/669_2.png) [@wpostma](https://forum.mattermost.com/u/wpostma)\
**Post date:** [June 23, 2016, 5:05pm UTC](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735/20 "2016-06-23T17:05:34Z")

</div>

What directory did you find en.json in and where did you copy it to?

[Next page](https://forum.mattermost.com/t/upgrading-to-gitlab-mattermost-in-gitlab-8-9/1735.md?page=2)