On 20.02.2014 23:28, Mimiko wrote:
Hello.
The scheduler can not start on system start-up, or using
/etc/init.d/otrs-scheduler-linux start. The problem is in this:
bin/otrs.Scheduler.pl -a status
Not Running!
*** glibc detected *** /usr/bin/perl: double free or corruption (!prev):
0x01f9
Hello,
Somewhere along the line glibc has become intolerant of minor memory leaks,
I had a similar problem that was trying to close an already closed file pointer.
There is an environment variable you can set called
MALLOC_CHECK_
see below
Recent versions of Linux libc (later than 5.4.2
On 20.02.2014 23:55, Gerald Young wrote:
perl -v
Oh, I've forgot about perl info:
perl -v
This is perl 5, version 14, subversion 2 (v5.14.2) built for
x86_64-linux-gnu-thread-multi
(with 88 registered patches, see perl -V for more detail)
Copyright 1987-2011, Larry Wall
Summary of my perl
perl -v
On Thu, Feb 20, 2014 at 4:28 PM, Mimiko wrote:
> Hello.
>
> The scheduler can not start on system start-up, or using
> /etc/init.d/otrs-scheduler-linux start. The problem is in this:
>
> bin/otrs.Scheduler.pl -a status
> Not Running!
> *** glibc detected *** /usr/bin/perl: double free o
Hello.
The scheduler can not start on system start-up, or using
/etc/init.d/otrs-scheduler-linux start. The problem is in this:
bin/otrs.Scheduler.pl -a status
Not Running!
*** glibc detected *** /usr/bin/perl: double free or corruption (!prev):
0x01f9a1b0 ***
And script hangs.
I u
