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
  #31 (permalink)  
Old 02-21-2006, 10:25 AM
Zimbra Employee
 
Posts: 2,103
Default

can you log into the web client?

Are you doing so via https?

If not, can you set it to use https mode, and try logging in?

To set it to https mode:
zmtsctl https
tomcat stop
tomcat start
Reply With Quote
  #32 (permalink)  
Old 02-21-2006, 11:37 AM
Intermediate Member
 
Posts: 22
Default

Quote:
Originally Posted by marcmac
can you log into the web client?
I have not tried, not having been able to log in as administrator to set up accounts. Is there some default account/password to log in from that is set up on installation?
Reply With Quote
  #33 (permalink)  
Old 02-21-2006, 12:59 PM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

The admin also has a mail account that you can login to.
__________________
Regards


Bill
Reply With Quote
  #34 (permalink)  
Old 02-21-2006, 08:47 PM
Intermediate Member
 
Posts: 22
Default

I believe that the answer (for me) is to uninstall and try again when the next release comes out.

Please identify the configuration changes I need to root out. I want to completely reverse the installation, not just remove the files. (OS X Client)
Reply With Quote
  #35 (permalink)  
Old 03-05-2006, 10:09 AM
Junior Member
 
Posts: 7
Default tomcat errors

I'm getting the following errors and can't get to the admin screen

zimbra@www bin]$ zmtlsctl https; tomcat restart
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
Error: no pid in /opt/zimbra/log/tomcat.pid

ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)

[zimbra@www bin]$
[zimbra@www bin]$
[zimbra@www bin]$ tomcat restart
Error: tomcat not running (pid 11044), stale pid file?


[zimbra@www bin]$ tomcat restart
Error: tomcat not running (pid 11044), stale pid file?

[zimbra@www bin]$ tomcat stop
Error: tomcat not running (pid 11044), stale pid file?
[zimbra@www bin]$ tomcat start
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException localhost:389)
[zimbra@www bin]$
__________________
Paul Terry Walhus
http://spring.net
terry@spring.net

searching for a web developer who can build a complex calendar site that pulls from other websites and allows users to have their own customized calendars.

Need: immediate
Reply With Quote
  #36 (permalink)  
Old 03-05-2006, 10:39 AM
Zimbra Employee
 
Posts: 2,103
Default

FOUR posts on one error? That's actually a new record.

LDAP init failed, widely covered topic, please search the forums.
Reply With Quote
  #37 (permalink)  
Old 11-12-2008, 07:15 AM
Junior Member
 
Posts: 5
Default

may be iptables is runing .Stop iptables and check
Reply With Quote
  #38 (permalink)  
Old 11-12-2008, 07:22 AM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

Quote:
Originally Posted by untripathy View Post
may be iptables is runing .Stop iptables and check
Please don't answer posts in a thread that's over two and a half years old.
__________________
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.