[solved] Installed 4.0.5 but seeing 3.3.11

Moderator: crythias

Locked
ptay
Znuny newbie
Posts: 85
Joined: 13 Jul 2010, 18:55
Znuny Version: 5.0.10

[solved] Installed 4.0.5 but seeing 3.3.11

Post by ptay »

I installed OTRS 4.0.5 from RPM.

Code: Select all

rpm -Uvh otrs-4.0.5-01.noarch.rpm
When I log into OTRS via index.pl or customer.pl web interface it shows 3.3.11.

Code: Select all

]# rpm -qa | grep -i otrs
otrs-4.0.5-01.noarch
I removed RPM

Code: Select all

rpm -e otrs-4.0.5-01.noarch
I notice after removing RPM that /opt/otrs is still present. I manually remove the directory.

Code: Select all

rm -rf /opt/otrs
Installed OTRS 4.0.5 from RPM again.

Code: Select all

rpm -Uvh otrs-4.0.5-01.noarch.rpm
When I log into OTRS via index.pl or customer.pl web interface it shows 3.3.11.

Not sure how I am getting 3.3.11. I'd like to wipe everything OTRS from RHEL7 system or figure out why 3.3.11 is showing.

At some point the box had 3.2 and was upgraded to 3.3. I can't find the RPM that was used or was removed by a peer.
Last edited by ptay on 28 Sep 2015, 21:57, edited 2 times in total.
Test:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
Prod:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
wurzel
Znuny guru
Posts: 3270
Joined: 08 Jul 2010, 22:25
Znuny Version: x.x.x
Real Name: Florian

Re: Installed 4.0.5 but seeing 3.3.11

Post by wurzel »

Hi,

can be some different things.

what tells you the /opt/otrs/RELEASE file? If this is 4.0.5 then your webserver does not use it.
So you need to check your webserver.

if it shows 3.3.11 your rpm is wrong

always check caches (browser, client + server)

Flo
OTRS 2025 SILVER (Prod)
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12

-- Ich beantworte keine Forums-Fragen PN - No PN please

I won't answer to unfriendly users any more. A greeting and regards are just polite.
ptay
Znuny newbie
Posts: 85
Joined: 13 Jul 2010, 18:55
Znuny Version: 5.0.10

Re: Installed 4.0.5 but seeing 3.3.11

Post by ptay »

Thanks for the advice. You led us to find the issue.

We checked the RPM and it was good. The RELEASE file was showing 3.3.11. We found out someone had grabbed the wrong backup (older 3.3.11 version) so we kept restoring 3.3.11 version on a 4.0.5 install. We identified the correct backup and we're operational now.

The restore step was left out of the identified steps. We restored after fresh install of 4.0.5 RPM.

Thanks!
Test:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
Prod:: OTRS 5.0.10 w/MariaDB 5.5.47 backend on RHEL7
Locked