# \[SOLVED\] Gitlab Omnibus 9.3.x installer does not upgrade Mattermost

**URL:** <https://forum.mattermost.com/t/solved-gitlab-omnibus-9-3-x-installer-does-not-upgrade-mattermost/3591>\
**Category:** Troubleshooting\
**Created:** [July 27, 2017, 10:53am UTC](https://forum.mattermost.com/t/solved-gitlab-omnibus-9-3-x-installer-does-not-upgrade-mattermost/3591 "2017-07-27T10:53:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hamadata](https://avatars.discourse-cdn.com/v4/letter/h/d2c977/32.png) [@hamadata](https://forum.mattermost.com/u/hamadata)\
**Post date:** [July 27, 2017, 10:53am UTC](https://forum.mattermost.com/t/solved-gitlab-omnibus-9-3-x-installer-does-not-upgrade-mattermost/3591/1 "2017-07-27T10:53:48Z")

</div>

#### Summary

Gitlab Omnibus installer did not upgrade Mattermost.

#### Steps to reproduce

On Amazon Linux 2017.03

Previously:

- Gitlab and Mattermost are both working.
- gitlab version was 9.3.x.

These command were executed:

- url [https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh](https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh) | sudo bash
- sudo yum install gitlab-ce
- sudo gitlab-ctl reconfigure

#### Expected behavior

- Mattermost is updated to 4.0 as shown in the table ( [https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/gitlab-mattermost#upgrading-gitlab-mattermost](https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/gitlab-mattermost#upgrading-gitlab-mattermost) ) because Gitlab is updated to 9.4.1.

#### Observed behavior

- Mattermost app in brower show the version, but the version is still 3.10.0.

- The log file, /var/log/gitlab/mattermost/current has the line:  
Current version is 4.0.0 (4.0.1/Wed Jul 19 00:54:25 UTC 2017/a350f4dc0754e1aeabb64bd712ce05f7c59cfa60/none)

- The img src of user icons on the app points URI out like this:  
/mattermost.mypage.net/api/v4/users/xztgtqdkjprhzqcskm5dojxdth/image?time=1501070387379

- Directly accessing to the URI, it returns:  
{“id”:“api.context.session\_expired.app\_error”,“message”:“Invalid or expired session, please login again.”,“detailed\_error”:"",“request\_id”:“5wm9ctiyxbdu5q689ea8b7cpgo”,“status\_code”:500}

---

<div class="post-metadata">

**Author:** ![hamadata](https://avatars.discourse-cdn.com/v4/letter/h/d2c977/32.png) [@hamadata](https://forum.mattermost.com/u/hamadata)\
**Post date:** [July 28, 2017, 6:05am UTC](https://forum.mattermost.com/t/solved-gitlab-omnibus-9-3-x-installer-does-not-upgrade-mattermost/3591/2 "2017-07-28T06:05:25Z")

</div>

This problem is fixed.

On previous update, mattermost is restarted in the following way:

> [@Where to find Mattermost after installing GitLab omnibus?](https://forum.mattermost.com/t/where-to-find-mattermost-after-installing-gitlab-omnibus/175/8):
>
> It’s probably NOT that you’re incompatible. In my case, the difficulty of getting this working comes from me not initially understanding all that is going on: I am using mattermost as part of a gitlab “omnibus” installation, and understanding what the “omnibus” thing is doing as it updates and manages things (with chef, I believe) leads to some confusion at times. The mattermost documentation refers to things that don’t exist like some /opt/mattermost/bin/platform executable. The name of …

My mistake was that the mattermost process that kicked by the command described in the article above cannot be killed by the gitlab update procedure. After killing the process, mattermost version 4.0 process can be started.

Thanks,