No_Such_Server

vpoorboy · Post by **vpoorboy** » Tue Nov 22, 2005 1:38 pm

The slapd is running, I can telnet localhost 389. (sorry just a typo

)

marcmac · Post by **marcmac** » Tue Nov 22, 2005 1:45 pm

telnet doesn't support host:port - it requires a space between them

vpoorboy · Post by **vpoorboy** » Tue Nov 22, 2005 1:47 pm

yes, and I've editted my post, I can telnet localhost on port 389

marcmac · Post by **marcmac** » Tue Nov 22, 2005 1:51 pm

run (as zimbra) zmldapinit by hand.

vpoorboy · Post by **vpoorboy** » Tue Nov 22, 2005 1:59 pm

Firsts, the errors are:

slapd already running: pid 12591

ldap_bind: Can't contact LDAP server (-1)

ldap_bind: Can't contact LDAP server (-1)

ls: /opt/zimbra/lib/conf/*ldif: No such file or directory

then, I stopped ldap, and run zmldapinit again, it showed:

Started slapd: pid 14819

ldap_bind: Can't contact LDAP server (-1)

ldap_bind: Can't contact LDAP server (-1)

ls: /opt/zimbra/lib/conf/*ldif: No such file or directory

chamo · Post by **chamo** » Tue Nov 22, 2005 2:51 pm

I am getting the same results as Vpoorboy when I ran the commands you requested marcmac..

marcmac · Post by **marcmac** » Tue Nov 22, 2005 3:51 pm

WHat's does zmlocalconfig | grep ldap return?
You can try this:
In zmldapinit, change the ldapmodify lines - add -H ${zimbra_ldap_url} to each and re-run zmldapinit.

marcmac · Post by **marcmac** » Tue Nov 22, 2005 5:23 pm

New information.
Type in this command:
host localhost
If it returns anything other than 127.0.0.1, that's a problem.
After install.sh, in the menu config - ctl-c to exit, and edit /opt/zimbra/libexec/zmldapinit - add -H ldap://127.0.0.1:389 to each ldapmodify line - then re-run /opt/zimbra/libexec/zmsetup.pl
Thanks, Chamo

vpoorboy · Post by **vpoorboy** » Tue Nov 22, 2005 11:17 pm

Thanks Marcmac, it's exactly the problem. I've installed Zimbra successfully.

But why this happened. I used to install Zimbra M1 from source, and the method to uninstall it is just "rm". Maybe it caused the problem.

Because when I run "host localhost", it returned:
localhost.test.homedns.org is an alias for test.homedns.org.

test.homedns.org has address a.b.c.d

localhost.test.homedns.org is an alias for test.homedns.org.

localhost.test.homedns.org is an alias for test.homedns.org.

So if I do something that "host localhost" return the right things (127.0.0.1), maybe the problem will be solved also ?

marcmac · Post by **marcmac** » Wed Nov 23, 2005 2:11 am

it's basically a dns issue. A nice dns server will return 127.0.0.1 for localhost. A not-so-nice server will append the domain name, and return it's own IP.
One possibility is to run a caching-only dns server (I can hear anand laughing from here) on your box, and point resolv.conf to it. Google that, it's beyond the scope of these forums.