Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 08-25-2009, 05:10 AM
Special Member
 
Posts: 104
Default Zimbra 6 RC1 x64 on Fedora 11 * Segfault *

Before console Login this message repeats over and over

Segfault at 8 IP and the cpu runs runs at 100%

error 4 at nginx

nginx log:
2009/08/24 17:47:01 [notice] 16536#0: start worker process 16560
2009/08/24 17:47:01 [notice] 16536#0: signal 29 (SIGIO) received
2009/08/24 17:47:01 [notice] 16536#0: signal 17 (SIGCHLD) received
2009/08/24 17:47:01 [alert] 16536#0: worker process 16555 exited on signal 11
2009/08/24 17:47:01 [alert] 16536#0: worker process 16557 exited on signal 11
2009/08/24 17:47:01 [alert] 16536#0: worker process 16559 exited on signal 11
2009/08/24 17:47:01 [alert] 16536#0: worker process 16560 exited on signal 11
2009/08/24 17:47:01 [alert] 16563#0: socket() failed (97: Address family not supported by protocol)
2009/08/24 17:47:01 [error] 16563#0: cannot connect to memcached server ^R^@^@^@^@^@^@^@ÃÃ^@^@^@^@ (rc:-1)
2009/08/24 17:47:01 [notice] 16536#0: start worker process 16563
2009/08/24 17:47:01 [alert] 16564#0: socket() failed (97: Address family not supported by protocol)
2009/08/24 17:47:01 [error] 16564#0: cannot connect to memcached server ^R^@^@^@^@^@^@^@ÃÃ^@^@^@^@ (rc:-1)
2009/08/24 17:47:01 [notice] 16536#0: start worker process 16564
2009/08/24 17:47:01 [alert] 16567#0: socket() failed (97: Address family not supported by protocol)
2009/08/24 17:47:01 [error] 16567#0: cannot connect to memcached server ^R^@^@^@^@^@^@^@ÃÃ^@^@^@^@ (rc:-1)
2009/08/24 17:47:01 [notice] 16536#0: start worker process 16567
@

Stack trace - repeating error:
"Timer-223" daemon prio=10 tid=0x00007f17c8bb3000 nid=0x292c in Object.wait() [0x00007f173ca89000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00007f176ef14e60> (a java.util.TaskQueue)
at java.lang.Object.wait(Object.java:485)
at java.util.TimerThread.mainLoop(Timer.java:483)
- locked <0x00007f176ef14e60> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)

Last edited by powrrrplay; 08-25-2009 at 05:53 AM..
Reply With Quote
  #2 (permalink)  
Old 08-26-2009, 08:32 AM
Special Member
 
Posts: 104
Default

I have spent a few days working on this.

With no help, I have decided to drop working on fedora11/zimbra/x64. will go back to centos5 x64 as i have a working zimbra 6 beta system there. Not solved just not working on it anymore.
Reply With Quote
  #3 (permalink)  
Old 08-26-2009, 08:43 AM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

Is this a single server and if so, why are you running the proxy? If it's not single server then you've given no details of your configuration.
Quote:
Originally Posted by powrrrplay View Post
With no help, I have decided to drop working on fedora11/zimbra/x64. will go back to centos5 x64 as i have a working zimbra 6 beta system there.
Have you reported this problem in bugzilla as that's the point of a beta release.
__________________
Regards


Bill
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.