
I'm going to bite the bullet and finally try to upgrade off of 1.3.x up to the latest version. Since the 2.3.2 UPGRADING instructions say they're for those going from 2.2 to 2.3 I imagine I'm going to have to upgrade from 1.3 to 2.0 then to 2.1 then to 2.2 and finally 2.3. That's fine. But the 2.0 UPGRADING instructions start off by saying...
These instructions are for people upgrading OTRS from "1.3" to "2.0".
*) Stop all your services (e. g. rcotrs stop-force)
When I try to enter "rcotrs stop-force" my OTRS system replies... -bash: rcotrs: command not found Help? Thanks. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

Wes Plate wrote:
I'm going to bite the bullet and finally try to upgrade off of 1.3.x up to the latest version.
Since the 2.3.2 UPGRADING instructions say they're for those going from 2.2 to 2.3 I imagine I'm going to have to upgrade from 1.3 to 2.0 then to 2.1 then to 2.2 and finally 2.3. That's fine.
You only need to upgrade the database through all those versions, not the program files.
But the 2.0 UPGRADING instructions start off by saying...
These instructions are for people upgrading OTRS from "1.3" to "2.0".
*) Stop all your services (e. g. rcotrs stop-force)
When I try to enter "rcotrs stop-force" my OTRS system replies...
-bash: rcotrs: command not found
Help? Thanks.
Your distribution probably uses a different method for managing services. On Red Hat you'd do 'service otrs stop' for instance. But I don't know what OS you're running. Nils Breunese.

On 9/20/08 2:18 PM, "Nils Breunese (Lemonbit)" wrote:
Your distribution probably uses a different method for managing services. On Red Hat you'd do 'service otrs stop' for instance. But I don't know what OS you're running.
I am on Red Hat. And that worked! Thank you! Now, to try upgrading the database... -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

On 9/20/08 2:27 PM, "Wes Plate" wrote:
Now, to try upgrading the database...
Hmmm, I'm sorry to bombard the list with questions, once I get this upgrade done I can go back to lurking. Thank you Nils for answering so far, I hope you can continue. :-) I downloaded the PRM for Redhat 8.0 and installed it. Then I ran the script to upgrade my database to 2.0 then I ran SetPermissions.sh. I restarted the services but cannot log in to OTRS, no matter what I enter I am told the login failed with incorrect username or password. I followed this step to reset the root password via mysql but still I can't log in... http://doc.otrs.org/1.3/en/html/problems-misc.html -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

I downloaded the PRM for Redhat 8.0 and installed it. Then I ran the script to upgrade my database to 2.0 then I ran SetPermissions.sh.
I restarted the services but cannot log in to OTRS, no matter what I enter I am told the login failed with incorrect username or password.
I thought long and hard about this and realized that when I installed OTRS from the RPM I actually installed the latest 2.3.2 version, so I needed to upgrade my DB from 2.0 to 2.1 and so on. Ok, did all that now I can log in to OTRS 2.3.2. Crisis averted. Now to start learning about this new version. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

Wes Plate wrote:
I downloaded the PRM for Redhat 8.0 and installed it. Then I ran the script to upgrade my database to 2.0 then I ran SetPermissions.sh.
I restarted the services but cannot log in to OTRS, no matter what I enter I am told the login failed with incorrect username or password.
I thought long and hard about this and realized that when I installed OTRS from the RPM I actually installed the latest 2.3.2 version, so I needed to upgrade my DB from 2.0 to 2.1 and so on.
Ok, did all that now I can log in to OTRS 2.3.2.
Yeah, you need to match your DB upgrades to the software version. Good to hear it's working now.
Crisis averted.
Crisis averted? You did make backups, right? (Or test the upgrade in a virtual machine so you can figure out all the steps before you apply them to the live installation.) Nils Breunese.

On 9/20/08 3:49 PM, "Nils Breunese (Lemonbit)" wrote:
Yeah, you need to match your DB upgrades to the software version. Good to hear it's working now.
Crisis averted.
Crisis averted? You did make backups, right? (Or test the upgrade in a virtual machine so you can figure out all the steps before you apply them to the live installation.)
I backed everything up, I just didn't want to have to go back. I don't have a virtual machine for Redhat, that would be a nice thing. I should look into that for VMWare. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

Wes Plate wrote:
I don't have a virtual machine for Redhat, that would be a nice thing. I should look into that for VMWare.
VMware Server is available free of charge these days, but if you're looking for desktop virtualization check out the free and open source VirtualBox: http://www.virtualbox.org/ (VMware Workstation isn't open source nor available free of charge.) Nils Breunese.

On 9/20/08 5:06 PM, "Nils Breunese (Lemonbit)" wrote:
VMware Server is available free of charge these days, but if you're looking for desktop virtualization check out the free and open source VirtualBox: http://www.virtualbox.org/ (VMware Workstation isn't open source nor available free of charge.)
I have VMWare Fusion on my main laptop. I'll find a redhat appliance for testing, that's a great idea. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

I installed OTRS on a Leopard system and am trying to get the cron jobs set up to check mail periodically. The jobs seem to run fine but I get the following error in my console log: 9/21/08 10:40:00 AM com.apple.launchd[1] (0x10bff0.cron[8110]) Could not setup Mach task special port 9: (os/kern) no access Any ideas why this is happening and what I can do about it? Thanks!! Manoj Patwardhan

I had a problem recently where my upgrade from OTRS 1.3.x to 2.3.2 failed but then I wasn't able to get back to my 1.3.x backup. I had dumped the original OTRS MySQL database to a 2.3GB .sql file and thought that was an adequate backup so I foolishly dropped the db from the system. When trying to recover back to 1.3.x MySQL would fail to import the .sql file. I didn't get any meaningful error messages, just and error. We finally got the DB back up by splitting the large .sql file into separate files for each table and importing them separately. Some records still had problems, it seemed that some of the records in article_plain were too big, as the import would die on some large entries so we just skipped those and continued on. It took some work but the original OTRS setup is back. I still hope to get upgraded to the latest version, but we'll hold off for a bit. When we do we'll do it on a Virtual Machine where we can easily try different strategies as well as easily roll back when things don't work. -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

Dumb question: Which RPM do I download? I'm running "Red Hat Enterprise Linux WS release 3 (Taroon Update 4)" -- Wes Plate Automatic Duck, Inc. http://www.automaticduck.com

Wes Plate wrote:
Dumb question: Which RPM do I download? I'm running "Red Hat Enterprise Linux WS release 3 (Taroon Update 4)"
The OTRS download page is a bit vague on this. They are still referring to Red Hat 7 and 8, while those have reached end of life quite some time ago AFAIK and they don't mention any current versions Red Hat Enterprise Linux. It's also not clear what the differences between the RPMs are. You might want to contact OTRS about this and/or file a bug report at http://bugs.otrs.org/ I have succesfully used the Red Hat 8 RPM on both CentOS 4 and 5, but I don't know about RHEL 3. Nils Breunese.
participants (3)
-
Manoj Patwardhan
-
Nils Breunese (Lemonbit)
-
Wes Plate