Hi Rudolf,

"As I had installed 3.2.0.beta5 previously, the MySQL DBUpdate pre and post
scripts reported errors, but only because all the new database entities
already existed."


You should not have executed this script at all! This is only for the 3.1
to 3.2 update. If you ARE already on 3.2, even on a beta, you should skip
this (and a couple of other) steps, as indicated in the docs.

As for the YAML problem, OTRS now has a different YAML parser than in
3.2beta5 because some issue that came up in certain conditions.
It seems like your data triggers a different kind of bug.




On Tue, Jan 29, 2013 at 3:14 PM, Rudolf Bargholz
<bargh...@onlinetravel.ch>wrote:

> Hi,****
>
> ** **
>
> Florian pointed me to other possible causes for general upgrade errors.***
> *
>
> ** **
>
> Even though I installed from the rpm I still executed the following:****
>
> ** **
>
> (Step 7 of the UPGRADING)****
>
> ** **
>
> cd /opt/otrs****
>
> bin/otrs.SetPermissions.pl /opt/otrs --otrs-user=otrs --web-user=wwwrun
> --otrs-group=nogroup --web-group=www****
>
> ** **
>
> After upgrading I executed step 11 of the UPGRADING:****
>
> ** **
>
> bin/otrs.RebuildConfig.pl****
>
> bin/otrs.DeleteCache.pl****
>
> ** **
>
> So these “normal” steps one often forgets when upgrading ought not
> necessarily be the cause of the errors below.****
>
> ** **
>
> Florian mentioned looking in the logfiles. Where can I find the logfiles
> which give me information about the upgrade process?****
>
> ** **
>
> None of the UPGRADING steps reported any “important” errors. As I had
> installed 3.2.0.beta5 previously, the MySQL DBUpdate pre and post scripts
> reported errors, but only because all the new database entities already
> existed.****
>
> ** **
>
> So unfortunately still no idea where to look. Any help very much
> appreciated.****
>
> ** **
>
> Regards****
>
> ** **
>
> Rudolf****
>
> ** **
>
> *Von:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *Im Auftrag
> von *Rudolf Bargholz
> *Gesendet:* Dienstag, 29. Januar 2013 14:41
>
> *An:* User questions and discussions about OTRS.
> *Betreff:* Re: [otrs] YAML error message after upgrade to 3.2.1****
>
> ** **
>
> Hi,****
>
> ** **
>
> Florian advised to install the YAML perl module, but this was installed
> already:****
>
> ** **
>
> Check Perl Modules installed.****
>
> All Perl modules needed are currently installed.****
>
> ...****
>
> ** **
>
>   o YAML::XS.........................ok (v0.38)****
>
> ** **
>
> Perhaps someone has an idea.****
>
> ** **
>
> Regards****
>
> ** **
>
> Rudolf****
>
> ** **
>
> *Von:* otrs-boun...@otrs.org 
> [mailto:otrs-boun...@otrs.org<otrs-boun...@otrs.org>]
> *Im Auftrag von *Rudolf Bargholz
> *Gesendet:* Dienstag, 29. Januar 2013 14:30
> *An:* User questions and discussions about OTRS. (otrs@otrs.org)
> *Betreff:* [otrs] YAML error message after upgrade to 3.2.1****
>
> ** **
>
> Hi,****
>
> ** **
>
> SUSE Linux Enterprise Server 11 (x86_64)****
>
> VERSION = 11****
>
> PATCHLEVEL = 2****
>
> ** **
>
> OTRS 3.2.1****
>
> Was previously 3.1.12, then upgraded to 3.2.0.beta5, then upgraded to 3.2.1
> ****
>
> ** **
>
> We have the following packages installed:****
>
> ** **
>
> FAQ<http://support.onlinetravel.ch/otrs/index.pl?Action=AdminPackageManager;Subaction=View;Name=FAQ;Version=2.2.1>
> ****
>
> 2.2.1****
>
> OTRSMasterSlave<http://support.onlinetravel.ch/otrs/index.pl?Action=AdminPackageManager;Subaction=View;Name=OTRSMasterSlave;Version=1.3.1>
> ****
>
> 1.3.1****
>
> Support<http://support.onlinetravel.ch/otrs/index.pl?Action=AdminPackageManager;Subaction=View;Name=Support;Version=1.4.4>
> ****
>
> 1.4.4****
>
> ** **
>
> I am seeing the following errors in the otrs system log:****
>
> ** **
>
> Tue Jan 29 14:07:49 2013****
>
> error****
>
> OTRS-CGI-10****
>
> Loading the YAML string failed: YAML::XS::Load Error: The problem:****
>
> Tue Jan 29 14:07:49 2013****
>
> error****
>
> OTRS-CGI-10****
>
> Loading the YAML string failed: YAML::XS::Load Error: The problem:****
>
> ** **
>
> There are no other log ****
>
> ** **
>
> Any idea what could be causing this? Or any idea how I can get more
> information in order to possibly find a cause for the message in the log?*
> ***
>
> ** **
>
> Regards****
>
> ** **
>
> Rudolf Bargholz****
>
> ---------------------------------------------------------------------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
>
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Reply via email to