How was your OTRS 3.1 upgrade?

[earwax]

Anybody care to share their experience of how their OTRS upgrade went to the new OTRS 3.1? I have not upgraded mine yet and I am waiting for the success and/or horror stories.

[prrole]

Pretty smooth. I use centos Centos 5.7, and just followed the instructions. Did a yum upgrade all before I started.

One problem I have is the init script, there seems to be an error there with OTRS_CHECKSCHEDULER vs OTRS_SCHEDULER_TEST - so I have to start it like this:

Code: Select all

[root@otrs init.d]# /opt/otrs/bin/otrs.Scheduler.pl -a status
Not Running!
[root@otrs init.d]# /opt/otrs/bin/otrs.Scheduler.pl -a start
[root@otrs init.d]# /etc/init.d/otrs start
Starting OTRS..
 Checking httpd ... done.
 Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=localhost;
DatabaseUser: otrs

It looks Ok! done.
 Checking OTRS Scheduler Service...  done.
 Enable /opt/otrs/bin/otrs.PostMaster.pl ... done.
 Checking otrs spool dir...  done.
 Creating cronjobs (source /opt/otrs/var/cron/*) ...
 done.

  -->> http://otrs.gigbone.net/otrs/index.pl <<--
Final start of OTRS.. done

If I do a restart, it fails:

Code: Select all

[root@otrs init.d]# /etc/init.d/otrs restart
Shutting down OTRS
 Disable /opt/otrs/bin/otrs.PostMaster.pl ... done.
 Shutting down cronjobs ...
 done.
 Shutting down OTRS scheduler ...
 done.
Final shutdown of OTRS.. done
Starting OTRS..
 Checking httpd ... done.
 Checking database connection... Trying to connect to database
DSN: DBI:mysql:database=otrs;host=localhost;
DatabaseUser: otrs

It looks Ok! done.
 Checking OTRS Scheduler Service...  Error!
  This can happen if your database is not configured yet.
[root@otrs init.d]#

[mac_mac74]

Anyone done a windows upgrade from 3.0.11 ?

Anyone know if there is a walk through?

[earwax]

Pretty smooth. I use centos Centos 5.7, and just followed the instructions. Did a yum upgrade all before I started.

How did you install OTRS 3.1? RPM? Or source file? Another thread (http://forums.otrs.org/viewtopic.php?f= ... 864#p54431) claims that the RPM files have some out of date files in them. Maybe related?

[miguelmz]

Anybody care to share their experience of how their OTRS upgrade went to the new OTRS 3.1? I have not upgraded mine yet and I am waiting for the success and/or horror stories.

The workflows with acl not working well on the front agent. The acl work all at once and never stop to selecting the next state in the interface.
However the client works perfectly frontal. I hope to fix soon because the dynamic fields and synchronization of folders are a great improvement

[cici6160]

I am experiencing exactly what prrole has described above. I'm running Centos 5.5 - installed OTRS 3.1.1-02 using RPM package.

When i restart otrs i get "Checking OTRS Scheduler Service... Error!" - and when i check crontab for otrs user (crontab -u otrs -e) it is empty.

Running the following (thank you prrole) re-creates crontab for OTRS user:
/opt/otrs/bin/otrs.Scheduler.pl -a start
/etc/init.d/otrs start

"Checking OTRS Scheduler Service... done."

[breun]

I also see the following when trying to start OTRS after upgrading to the 3.1.1-02 RPM on CentOS 5:

Checking OTRS Scheduler service.... /etc/init.d/otrs: line 251: -s: command not found
Error!
Maybe your database isn't configured yet?

Indeed running /opt/otrs/bin/otrs.Scheduler.pl -a start before trying to start OTRS seems to help. I left a comment at the following bug report: http://bugs.otrs.org/show_bug.cgi?id=7940

[paulthomas123321]

HI,
I have done a test upgrade myself following the instructions in the source code "UPGRADING", I did not have a problem but also did not test all the functionality.
I would suggest to try this on a copy of the database, just in case.

thanks,
Paul

[survivaltosuccess]

I was looking for some updates as well so I can decide whether to upgrade my OTRS or not yet. Looking forward for more information.

[earwax]

I was looking for some updates as well so I can decide whether to upgrade my OTRS or not yet. Looking forward for more information.

Yup! Exactly the reason why I started this post. From the amount of views this post is getting, it is apparent that others want to know, too! I hope more people share their experiences. I want to see if the upgrade is smooth or not. Seems like the RPM users are having that little issue, but that seems to be the worst of it.

[fandango]

Upgraded from 2.4.7 here.
Apart the schedule problem, fixed with the -a start command, my main problem is that otrs returns blank pages when agents works with tickets or queue.
I've tested all the option, even a fresh install (new config files, only DB remain the same).
I could expect the refresh issue was due to old sessions files, cache, etc.
But now, with a fresh install (CentOs 5.5), I'm confident that there are not problem with old files somewhere.
The Support page returns all fine, all the modules are ok.
If I restart Apache, users say the problem seems fixed, but after some hours the frequence of the blank pages increase.
We tested with Firefox, IE, etc.
We don't use proxy, URL filtering, etc..
I haven't found a "debug" command that can help in debugging this situation.

Anyone experiencing this problem ?

Many thanks.

UPDATE: fixed the blank page problem disabling the mod_perl (removed the mod_perl section in apache conf).

[carnold]

Not an upgrade but installed from RPM on SLES 11 SP1 and i encountered the exact same thing. Ran the otrs.Scheduler.pl -a and it seems to go away.

[jojo]

thats a known issue with SUSE and RedHat, and will be fixed in 3.1.2

[marv]

Anyone done a windows upgrade from 3.0.11 ?

I've done an "upgrade" on windows tyesterday and it seems to work relativly fine.

There was a problem with the update script "DBUpdate-to-3.1.mysql.sql"
I had to comment line 187 to get it to work. Though I'm not sure about the side effects.

Today is going to be a lot of testing. Especially the extenstions (i.e. time accounting).

Anyone know if there is a walk through?

There is ... kinda.
The most things from the Linux Tutorial also apply for windows:
http://doc.otrs.org/3.1/en/html/upgrading.html

The Windows tutorial is 'funny':
http://doc.otrs.org/3.1/en/html/upgrade ... aller.html
The FAQ Link is broken, but the youtube *sigh* video contains pretty much all the information needed.

[se-mh]

HI,

after Upgrade to 3.1.2 still the same issue here with the Scheduler agent and in addition to this the start-foce check of apache2 also fails, even though it is running ....

Code: Select all

server:~ # rcotrs start-force
Starting OTRS (completely)
 Starting Apache ... done.
Starting OTRS
 Checking Apache ... failed!
  --> Please start the web server first! (rcapache2 start) <--
                                                                      failed
server:~ # rcapache2 start
Apache is already running (/var/run/httpd2.pid)                       done
server:~ # rcotrs start
Starting OTRS
 Checking Apache ... done.
 Checking database connection... (Trying to connect to database
DSN: DBI:mysql:database=otrs_live;host=localhost;
DatabaseUser: otrs

It looks Ok!).
 Checking OTRS Scheduler Service...  Error!
  This can happen if your database is not configured yet.

server:~ # /opt/otrs/bin/otrs.Scheduler.pl -a start
server:~ # rcotrs start
Starting OTRS
 Checking Apache ... done.
 Checking database connection... (Trying to connect to database
DSN: DBI:mysql:database=otrs_live;host=localhost;
DatabaseUser: otrs

It looks Ok!).
 Checking OTRS Scheduler Service...  done.
 Enable /opt/otrs/bin/otrs.PostMaster.pl ... done.
 Checking otrs spool dir...  done.
 Creating cronjobs (source /opt/otrs/var/cron/*) ... done.

  -->> http://server/otrs/index.pl <<--
                                                                      done

The workaround with manual startup of the Agent is a thing you need to know, then you get the system rolling. But it would be nice to see if others also have problems even after installing the Update 3.1.2 which was meant to also fix this issue...

Anyone else having also problem with the apache2 now?

I also have good news, the unlock of the ticket when reverting the reply does now work --> no "invalid challenge token"...

[imant1]

Hi, I've error below.. Anyone can help?

Checking OTRS Scheduler service.... /etc/init.d/otrs: line 241: -s: command not found
Error!

[sweetchariot]

thats a known issue with SUSE and RedHat, and will be fixed in 3.1.2

Is version 3.1.2 is out now??

[jojo]

since some weeks...


3.1.3 is planned for end of the week

[artjoms15]

Well after update to 3.1.1 I' ve got a lot of junk queues, agents and different test data in my database
It seems that update script updates some unnecessary test data which has to be disabled later...
Maybe I ve got some outdated update script, or it is normal for every update?

[deragoku]

I have no problems, but have not yet tested all the features. I would suggest to try a copy of the database, just in case.

[cesarcain]

No problem with my upgrade

[Andydba]

Wow otrs help desk v3.1.5 came out today. Hard to keep up!

[robjons21]

Wow otrs help desk v3.1.5 came out today. Hard to keep up!

Well Thats great news. i was really hoping it will come soon. now i am gonna find it and play wid it

[traduceresimultana]

I haven't tested all the features but it was pretty smooth at first.The upgrade did feel like a new thing and proved to be better .