I will give it a go next chance I get. It seemed to happen a lot in cronjobs. It also seemed to happen, when I opened a ticket from the Dashbord or Ticket overview (in which case I also got a 500 error, as far as I recall). As far as I can tell, the changes to the database should not be able to cause the issue, so most likely it is somewhere in the code... I will report back when I have tried these suggestions. /Martin.
>>> James Michael DuPont <mike.dup...@otrs.com> 11. februar 2012 08:49 >>> Hi there, You could easily rename the installed version of YAML and then perl will use your version. If you cannot find the problem, please post a detailed bug report with files that I can look at and I will try and reproduce the problem. thanks, mike On Fri, Feb 10, 2012 at 10:18 AM, Michiel Beijen <michiel.bei...@otrs.com> wrote: Hi Martin, 2012/2/8 Martin Møller <m...@itq.dk>: > On my original 2.4 system, the previous administrator have installed YAML > through CPAN in site_perl. This version is 0.70 > > Now, with 3.1, you package YAML yourselves, and I guess that the site_perl > catalog is checked before cpan-lib, so it sees the old version of YAML, not > version 0.73 that OTRS delivers. > > Would it sound reasonable that an older version of YAML might choke on > certain things in OTRS 3.1? It is working correctly on 3.0.11, where you > don't distribute your own YAML: You don't mention which kind of issues you are experiencing, so it would be very difficult to tell whether or not YAML causes these. We bundle some Perl modules in Kernel/cpan-lib for two reasons: you'll have to install less dependencies if you will set up OTRS, and second, we can control the version that OTRS uses; we do not need to bother about distribution X shipping version 0.1 and distribution Y shipping with version 0.9 of the same module; it gives us more control. Apart from that, typically OTRS will always use the version in Kernel/cpan-lib, even if you have installed a different version on your system using CPAN, yum or apt-get. Also, the rest of your system (everything else but OTRS) will not use these modules, so you will not have to worry that OTRS will break the rest of your system by shipping its own set of libraries. So that's why I think it would be very unlikely that the YAML version you installed via CPAN and the version you'll get with OTRS will actually cause issues here. Of course, it *could* be that somewhere in the OTRS code we don't properly check Kernel/cpan-lib before searching the rest of the system, but again, that would be unlikely I think. Also, the YAML code is only used in few places; for instance in saving the configuration for the new OTRS web services. So if you can share the error message you ran in to, maybe we can help you pin-point the exact cause. -- Mike --------------------------------------------------------------------- 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 -- James Michael DuPont Custom Engineering/Research & Development OTRS AG Norsk-Data-Straße 1 D-61352 Bad Homburg T: +49 (0) 9421 56818 0 F: +49 (0) 9421 56818 18 I: http://www.otrs.com/ Geschäftssitz: Bad Homburg, Amtsgericht Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn
--------------------------------------------------------------------- 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
