On 05/18/2016 11:37 AM, [email protected] wrote:
> 
> 
>> Gesendet: Mittwoch, 18. Mai 2016 um 10:43 Uhr Von: "Martijn
>> Brinkers" <[email protected]> An: [email protected] 
>> Betreff: Re: [Djigzo users] Problem after java-Update in CentOS 6
>> 
>> On 05/17/2016 06:16 PM, Martijn Brinkers wrote:
>>> On 05/17/2016 06:02 PM, [email protected] wrote:
>>>> Hi, I`m using a ciphermail on a CentOS 6 fully patched and it
>>>> worked fine for quite a while, but after an update to 
>>>> java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64 today, I
>>>> found this in the /var/log/djigzo.log:
>>>> ...ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
>>>> [vsyscall] JVM process is gone. JVM exited while loading the
>>>> application. Launching a JVM... JVM received a signal UNKNOWN
>>>> (6). java version "1.6.0_39" OpenJDK Runtime Environment
>>>> (IcedTea6 1.13.11) (rhel-1.13.11.0.el6_7-x86_64) OpenJDK 64-Bit
>>>> Server VM (build 23.25-b01, mixed mode)
>>>> 
>>>> *** glibc detected *** 
>>>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java:
>>>> double free or corruption (!prev): 0x0000000001e5ac c0 ***
>>>> ======= Backtrace: =========
>>>> /lib64/libc.so.6(+0x75f4e)[0x7fc450e82f4e] 
>>>> /lib64/libc.so.6(+0x78cf0)[0x7fc450e85cf0] 
>>>> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java[0x402fbb]
>>>>
>>>>
>>>
>>>> 
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.39.x86_64/jre/bin/java(JavaMain+0x51c)[0x40373c]
>>>> /lib64/libpthread.so.0(+0x7aa1)[0x7fc4515b0aa1] 
>>>> /lib64/libc.so.6(clone+0x6d)[0x7fc450ef593d] ....
>>>> 
>>>> There were 10 failed launches in a row, each lasting less than
>>>> 300 seconds.  Giving up. There may be a configuration problem:
>>>> please check the logs. <-- Wrapper Stopped
>>>> 
>>>> On the Weblogin-page I got the message about a not fully
>>>> started background problem.
>>>> 
>>>> Any suggestions are welcome
>>> 
>>> This looks like a bug in Java 6. A similar bug was reported last
>>> week:
>>> 
>>> https://jira.djigzo.com/browse/GATEWAY-101
>>> 
>>> For now the best solution is to upgrade to Java 6. See bug
>>> report #GATEWAY-101 for more information.
>>> 
>>> A possible workaround is to add the following line to the file 
>>> djigzo.wrapper.conf
>>> 
>>> wrapper.debug=true
>>> 
>>> Let me know whether this work around works for you. It looks like
>>> some interaction between Java wrapper (which starts the Java
>>> process) and Java 6 update.
>>> 
>>> I will investigate this further.
>> 
>> As a workaround (instead of installing Java 7), you can add 
>> wrapper.disable_console_input=FALSE to the Java wrapper config. You
>> can add this option by editing the file /etc/init.d/djigzo
>> 
>> Change
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE"
>> 
>> To:
>> 
>> WRAPPER_OPTS="wrapper.daemonize=TRUE
>> wrapper.disable_console_input=FALSE"
>> 
>> I'll contact the java wrapper developers. It might be some
>> interaction bug between changes in Java 6 and java wrapper.
>> 
> Hi Martin,
> 
> thank you very much for your fast support. Mailencrypt and decrypt
> works fine with the last workaround. But we are running in a new
> problem with the weblogin. I always get an ssl-error
> (ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION -> Chrome) messages in FF
> and Chrome when I try to open the login page.

Works for me with CipherMail 2.10.0-3 on CentOS 6 with Java 6 and
Firefox and Chrome.

Which version of CipherMail are you using?

Kind regards,

Martijn Brinkers

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail

-- 
CipherMail email encryption

Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.

https://www.ciphermail.com

Twitter: http://twitter.com/CipherMail
_______________________________________________
Users mailing list
[email protected]
https://lists.djigzo.com/lists/listinfo/users

Reply via email to