Bschalck
(Bschalck)
January 31, 2019, 10:14pm
1
For feature requests, please see: Contributing Feature Proposals - Mattermost .
For troubleshooting questions, please post in the following format:
Summary
When I upgrade my mattermost-team from 5.3.0 to 5.7.0 , the upgrade is not applied
Steps to reproduce
OS : Debian
I download mattermost-team-5.7.0-linux-amd64.tar.gz
systemctl stop mattermost
tar -x --transform='s,^[^/]\+,\0-upgrade,' -f mattermost*.gz
mv mattermost/plugins/ mattermost/plugins~
chown -hR mattermost:mattermost mattermost-upgrade
cp -an mattermost-upgrade/. mattermost/
rm -rf mattermost-upgrade/
systemctl start mattermost
Unitl then that works ( upgrade form 5.0 to 5.1, 5.1 to 5.2, 5.2 to 5.3 ) , but here it makes nothing, my version is still 5.3.0 in about screen
Expected behavior
Expect 5.7.0 , not 5.3.0
Observed behavior
Juste look th About Screen
Regards,
amy.blais
(Amy Blais)
January 31, 2019, 11:13pm
2
Hi @Bschalck ,
Confirming that you followed all the steps in the upgrade notes: https://docs.mattermost.com/administration/upgrade.html ?
Also, confirming that you have taken a look at the Important upgrade notes for scenarios that may apply to you: https://docs.mattermost.com/administration/important-upgrade-notes.html ?
If yes, can you help post here the Mattermost logs?
Bschalck
(Bschalck)
February 1, 2019, 8:51am
3
Hi,
Thanks for the answer.
In fact, I didn’t view the Important upgrade notes for scenario https://docs.mattermost.com/administration/important-upgrade-notes.html .
And as I understand, that should correct the mistake.
I’ll tell you if it is OK.
Regards,
Bschalck
(Bschalck)
February 20, 2019, 2:42pm
4
Hy,
the problem is still alive.
I try with 5.8.0 and have the same mistake.
Regards,
amy.blais
(Amy Blais)
February 20, 2019, 3:51pm
5
Hi @Bschalck ,
Confirming that you used the whole command (wget https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz )?
Do you see any Mattermost log errors that we can take a look at?
JtheBAB
February 21, 2019, 5:37am
6
Can please do a
less /lib/systemd/system/mattermost.service
and share the output?
And also can you do pwd in that folder where you do the steps from post 1?
Bschalck
(Bschalck)
February 21, 2019, 8:30am
7
Hello,
I see no errors in the mattermost log.
Here is the content of less /lib/systemd/system/mattermost.service
:
[Unit]
Description=Mattermost
After=network.target
After=postgresql.service
Requires=postgresql.service
[Service]
Type=notify
ExecStart=/opt/mattermost/bin/mattermost
TimeoutStartSec=3600
Restart=always
RestartSec=10
WorkingDirectory=/opt/mattermost
User=mattermost
Group=mattermost
LimitNOFILE=49152
[Install]
WantedBy=multi-user.target
JtheBAB
February 21, 2019, 8:43am
8
Just to be sure. You are in /opt when you do the update steps?
Bschalck
(Bschalck)
February 21, 2019, 8:51am
9
Yes I am.
In fact, all my actions are done in /opt
cd /opt
systemctl stop mattermost
wget https://releases.mattermost.com/5.8.0/mattermost-team-5.8.0-linux-amd64.tar.gz
tar -x --transform=‘s,+,\0-upgrade,’ -f mattermost*.gz
mv mattermost/plugins/ mattermost/plugins~
chown -hR mattermost:mattermost mattermost-upgrade
cp -an mattermost-upgrade/. mattermost/
rm -rf mattermost-upgrade/
systemctl start mattermost
JtheBAB
February 21, 2019, 11:04am
10
Strange.
Can you do this command?
md5sum /opt/mattermost/bin/mattermost
This is my md5hash for 5.8.0:
a0158993520893c65a3331c9335aea31 /opt/mattermost/bin/mattermost
Bschalck
(Bschalck)
February 21, 2019, 11:36am
11
Here is mine:
/root $ md5sum /opt/mattermost/bin/mattermost
198ea30af87524496988147c36a62b76 /opt/mattermost/bin/mattermost
and in the upgrade directory , it’s OK .
/opt/mattermost-upgrade/bin $ md5sum mattermost
891ac7c43a786fb719904a3158901725 mattermost
it seems that the “cp -an mattermost-upgrade/. mattermost/” does not work fine.
I will find why
Bschalck
(Bschalck)
February 21, 2019, 11:45am
12
If fact , th option “-n” is the mistake I thnik:
-n, --no-clobber
ne pas écraser un fichier existant (annule une précédente option
-i)
So it is not overwrite existing file …
Bschalck
(Bschalck)
February 21, 2019, 11:50am
13
I copy the binary mattermost file , anf now it s OK :
JtheBAB
February 21, 2019, 4:32pm
14
You missed this command:
sudo find mattermost/ -mindepth 1 -maxdepth 1 ! ( -type d ( -path mattermost/config -o -path mattermost/logs -o -path mattermost/plugins -o -path mattermost/data ) -prune ) | sudo xargs rm -r
And the hash is different due to the fact that i use the enterprise edition.
Sorry didn’t see it
Bschalck
(Bschalck)
February 26, 2019, 10:11am
15
Hy ,
in fact yes, the mistake is the missing line find mattermost/ -mindepth 1 -maxdepth 1 ! ( -type d ( -path mattermost/config -o -path mattermost/logs -o -path mattermost/plugins -o -path mattermost/data ) -prune ) | sudo xargs rm -r in my proc.
Thank you for the analyse , I note the missing line.
Regards,
1 Like