Hi,
I'm new to the 389 DS environment and this probably is some really stupid mistake on my side, but I can't figure it out alone.
What I want: Connect to my server (Debian Wheezy) with the 389-console What I got: A running (and working...well partially) 389-DS (no SSL/TLS! ). What does work: I can login/access http://myservername.org:9830 What does not work: Accessing the same site via 389-console from a remote host.
What happens when I try to connect with '389-console -a http://myhostname.org:9830 -u cn=Directory Manager -w secret -D':
GUI: Changes to 'Initializing' then a message appears "Cannot connect to the Directory Server "ldap://localhost:389. LDAP error: failed to connect to server ldap://localhost:389.
Would you like to attempt to restart the Directory Server?"
(since I know that the server is running, I'm choosing 'No' which exits the program)
Terminal output: http://pastebin.ca/2317259
Slapd-instancename/access log: http://pastebin.ca/2317260
The instance's error log has no new entries.
The content of admin-serv/access and admin-serv/error are only success messages, no real errors.
If you need more informations, please ask.
Few things to check with your 389 setup.
1. Please ensure all hostnames are FQDN4. If you don't have DNS then create hosts file entries for those hostnames. 2. The admin console uses the /etc/dirsrv/admin/conf* . -- Mostly you don't have to touch this file if you have used the setup-ds script. 3. The hostname MUST be resolved from your remote host.
if you are running the 389-console -a http://ldap.server.net:9830
So here the ldap.server.net MUST be defined either in your DNS server or in your host file.
Also check whether server is running on that port "netstat -plunt"
On Tue, Feb 26, 2013 at 1:12 PM, Steffen steffen.linux@gmx.de wrote:
Hi,
I'm new to the 389 DS environment and this probably is some really stupid mistake on my side, but I can't figure it out alone.
What I want: Connect to my server (Debian Wheezy) with the 389-console What I got: A running (and working...well partially) 389-DS (no SSL/TLS! ). What does work: I can login/access http://myservername.org:9830 What does not work: Accessing the same site via 389-console from a remote host.
What happens when I try to connect with '389-console -a http://myhostname.org:9830 -u cn=Directory Manager -w secret -D':
GUI: Changes to 'Initializing' then a message appears "Cannot connect to the Directory Server "ldap://localhost:389. LDAP error: failed to connect to server ldap://localhost:389.
Would you like to attempt to restart the Directory Server?"
(since I know that the server is running, I'm choosing 'No' which exits the program)
Terminal output: http://pastebin.ca/2317259
Slapd-instancename/access log: http://pastebin.ca/2317260
The instance's error log has no new entries.
The content of admin-serv/access and admin-serv/error are only success messages, no real errors.
If you need more informations, please ask.
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Well, myhostname.org is reachable from the PCs I tested it on. Since I'm not sure what you mean by point 3, I added myhostname with it's IP to my /etc/hosts file. Still got the same error message. -------- Original-Nachricht --------
Datum: Tue, 26 Feb 2013 13:41:38 -0800 Von: Chandan Kumar chandank.kumar@gmail.com An: "General discussion list for the 389 Directory server project." 389-users@lists.fedoraproject.org Betreff: Re: [389-users] 389-console: tries to connect to localhost:389 instead of hostname:389
Few things to check with your 389 setup.
- Please ensure all hostnames are FQDN4. If you don't have DNS then
create hosts file entries for those hostnames. 2. The admin console uses the /etc/dirsrv/admin/conf* . -- Mostly you don't have to touch this file if you have used the setup-ds script. 3. The hostname MUST be resolved from your remote host.
if you are running the 389-console -a http://ldap.server.net:9830
So here the ldap.server.net MUST be defined either in your DNS server or in your host file.
Also check whether server is running on that port "netstat -plunt"
On Tue, Feb 26, 2013 at 1:12 PM, Steffen steffen.linux@gmx.de wrote:
Hi,
I'm new to the 389 DS environment and this probably is some really stupid mistake on my side, but I can't figure it out alone.
What I want: Connect to my server (Debian Wheezy) with the 389-console What I got: A running (and working...well partially) 389-DS (no SSL/TLS! ). What does work: I can login/access http://myservername.org:9830 What does not work: Accessing the same site via 389-console from a remote host.
What happens when I try to connect with '389-console -a http://myhostname.org:9830 -u cn=Directory Manager -w secret -D':
GUI: Changes to 'Initializing' then a message appears "Cannot connect to the Directory Server "ldap://localhost:389. LDAP error: failed to connect to server ldap://localhost:389.
Would you like to attempt to restart the Directory Server?"
(since I know that the server is running, I'm choosing 'No' which exits the program)
Terminal output: http://pastebin.ca/2317259
Slapd-instancename/access log: http://pastebin.ca/2317260
The instance's error log has no new entries.
The content of admin-serv/access and admin-serv/error are only success messages, no real errors.
If you need more informations, please ask.
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Got it solved!
In my adm.conf the ldapURL was set to localhost:359, after I changed it to myservername.org:359 and restarted both, the directoryserver and the admin interface, I was able to connect (username has to be 'admin' instead of cn=Directory Manager). Also, of course, I had to open the 359 port in my iptables. -------- Original-Nachricht --------
Datum: Tue, 26 Feb 2013 13:41:38 -0800 Von: Chandan Kumar chandank.kumar@gmail.com An: "General discussion list for the 389 Directory server project." 389-users@lists.fedoraproject.org Betreff: Re: [389-users] 389-console: tries to connect to localhost:389 instead of hostname:389
Few things to check with your 389 setup.
- Please ensure all hostnames are FQDN4. If you don't have DNS then
create hosts file entries for those hostnames. 2. The admin console uses the /etc/dirsrv/admin/conf* . -- Mostly you don't have to touch this file if you have used the setup-ds script. 3. The hostname MUST be resolved from your remote host.
if you are running the 389-console -a http://ldap.server.net:9830
So here the ldap.server.net MUST be defined either in your DNS server or in your host file.
Also check whether server is running on that port "netstat -plunt"
On Tue, Feb 26, 2013 at 1:12 PM, Steffen steffen.linux@gmx.de wrote:
Hi,
I'm new to the 389 DS environment and this probably is some really stupid mistake on my side, but I can't figure it out alone.
What I want: Connect to my server (Debian Wheezy) with the 389-console What I got: A running (and working...well partially) 389-DS (no SSL/TLS! ). What does work: I can login/access http://myservername.org:9830 What does not work: Accessing the same site via 389-console from a remote host.
What happens when I try to connect with '389-console -a http://myhostname.org:9830 -u cn=Directory Manager -w secret -D':
GUI: Changes to 'Initializing' then a message appears "Cannot connect to the Directory Server "ldap://localhost:389. LDAP error: failed to connect to server ldap://localhost:389.
Would you like to attempt to restart the Directory Server?"
(since I know that the server is running, I'm choosing 'No' which exits the program)
Terminal output: http://pastebin.ca/2317259
Slapd-instancename/access log: http://pastebin.ca/2317260
The instance's error log has no new entries.
The content of admin-serv/access and admin-serv/error are only success messages, no real errors.
If you need more informations, please ask.
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org
-
Chandan Kumar -
Steffen