You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.
Notify me of new posts via email. Enter your email address to subscribe to this blog and receive notifications of new posts by email. Email Address:. Anupsnair's Blog Anup Nairs techlog. Home About Poll. Share this: Twitter Facebook Reddit. Like this: Like Loading Categories: Amazon ec2 , Zimbra Tags: zimbra amazon ec2.
Comments 0 Trackbacks 0 Leave a comment Trackback. No comments yet. No trackbacks yet. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. If I proceed with the installation, then the next error that I get is: Initializing ldap Failed to start slapd.
Attempting debug start to determine error. Regards Bill Rspamd: A high performance spamassassin replacement Per ardua ad astra. Forum member "SuperMario" would be the one who set that up. I'll let him know about this thread. I think that the best way to troubleshoot this problem is to make sure that you're always correctly pointing your DNS entries in your EC2 instance to the domain DNS entries routing your hostname.
S3 will primarily be used for server backups. I inferred it from the MX lookup information. I let it proceed past the MX record lookup error. If I type domain. For 30 minutes last night, I logged into Zimbra Admin and the user console. The only noticeable issue was the it said logger was not operating. I could not test whether it was working or not. Unfortunately, I rebooted the instance and zimbra ceased to work with zmcontrol and zmstart outcomes below.
Zmcontrol status reveals: Host domuc4. I really appreciate your help any ideas? Jump to. Who is online Users browsing this forum: No registered users and 14 guests.
0コメント