hi there
hopefully someone can help, i tried to run the update to 5.0.14 today but it will not install it just says i already have 5.0.12 installed ??
i removed all the packages and then stopped all the services... i tried to do the install which caused the below..
what have i done wrong. i downloaded the update this morning from the update portal 5.0.14-2.noarch.rpm
im installing on centos 6 with all the latest updates applied and rebooted...
any help would be greatly appreciated
thanks
jay
[SOLVED] unable to upgrade from 5.0.12 to 5.0.14
Moderator: crythias
-
- Znuny newbie
- Posts: 32
- Joined: 26 Sep 2011, 17:45
- Znuny Version: 5.0.14
- Real Name: justin
- Company: gigasoft
[SOLVED] unable to upgrade from 5.0.12 to 5.0.14
You do not have the required permissions to view the files attached to this post.
Last edited by minijay on 24 Nov 2016, 11:53, edited 1 time in total.
Re: unable to upgrade from 5.0.12 to 5.0.14
Please try again from scratch:
Delete package
Download new package
Update
Just to make sure that it is the rigt package
Delete package
Code: Select all
rm otrs-5.0.14-02.noarch.rpm
Code: Select all
wget http://ftp.otrs.org/pub/otrs/RPMS/rhel/6/otrs-5.0.14-02.noarch.rpm
Code: Select all
rpm -Uvh otrs-5.0.14-02.noarch.rpm
OTRS 5.0.26 with ITSM, and FAQ module on CentOS 7 with MariaDB and Apache
Using LDAPS for customers and agents against Azure AD
Using LDAPS for customers and agents against Azure AD
-
- Znuny newbie
- Posts: 32
- Joined: 26 Sep 2011, 17:45
- Znuny Version: 5.0.14
- Real Name: justin
- Company: gigasoft
[SOLVED] unable to upgrade from 5.0.12 to 5.0.14
that did the trick..
not sure what happened there, i did thei yesterday but kept getting the same results.. i removed all the files and redownloaded this morning and it worked.. very strange..
re ran the update this morning and it all ran fine.
thanks for all your help
Jay
not sure what happened there, i did thei yesterday but kept getting the same results.. i removed all the files and redownloaded this morning and it worked.. very strange..
re ran the update this morning and it all ran fine.
thanks for all your help
Jay