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.23) and glibc (2.x) include a malloc() implementation which is tunable via environment variables. When MALLOC_CHECK_ is set, a special (less efficient) implementa- tion is used which is designed to be tolerant against simple errors, such as double calls of free() with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap corrup- tion is silently ignored; if set to 1, a diagnostic message is printed on stderr; if set to 2, abort(3) is called immediately; if set to 3, a diagnostic message is printed on stderr and the program is aborted. Using a nonzero MALLOC_CHECK_ value can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down. HTH, Steve On 02/20/2014 04: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 or corruption (!prev): 0x0000000001f9a1b0 ***
And script hangs.
I use Control+C to stop it. I didn't find out why is this error. My system is: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Thank you for help.
-- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@netwolves.com http://www.netwolves.com