Re: [systemd-devel] systemd-socket-proxyd slapd
Would you be willing to post the entire unit files for everything here, just so future users can see them? Presumably, you're using JoinsNamespaceOf=proxy-to-directory-400.service in vgp.master-ldap-400.service? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-socket-proxyd slapd
Thanks now it works, But does it mandatory to start slapd on same port as ListenStream= of socket file of systemd-socket-proxyd. e.g in following example port 400. # cat proxy-to-directory-400.service [Unit] Requires=master-ldap-400.service After=master-ldap-400.service [Service] ExecStart=/usr/lib/systemd/systemd-socket-proxyd ${HOSTNAME}:400 PrivateTmp=yes PrivateNetwork=yes # cat proxy-to-directory-400.socket [Socket] ListenStream=400 [Install] WantedBy=sockets.target --- #cat vgp.master-ldap-400.service ... ExecStart=/usr/local/libexec/slapd -d 0 -f conf_400.conf -h ldap://${HOSTNAME}:400; -l LOCAL1 ... --- On Thu, Jul 17, 2014 at 11:08 PM, David Timothy Strauss da...@davidstrauss.net wrote: On Thu, Jul 17, 2014 at 4:51 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: I'd try without Private* settings. Also, replace /usr/lib/systemd/systemd-socket-proxyd with '/bin/strace -o /tmp/log /usr/lib/systemd/systemd-socket-proxyd' and look at the log file. Yes, get it working without Private*= first. JoinsNamespaceOf= is simply useful if you want to add it back after it's working. Another thing to try is targeting systemd-socket-proxyd at a different target (like a public website) to make sure it's activating properly. Also try connecting directly to the directory service without going through the proxy. -- Suvendu Mitra GSM - +358504821066 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-socket-proxyd slapd
On Wed, Jul 23, 2014 at 11:13:50AM +0300, Suvendu Mitra wrote: Thanks now it works, But does it mandatory to start slapd on same port as ListenStream= of socket file of systemd-socket-proxyd. e.g in following example port 400. Maybe the protocol embeds the port number in the stream? That wouldn't be so unusual, HTML does such braindead things too. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-socket-proxyd slapd
I have changed proxy-to-directory-400.service as # cat proxy-to-directory-400.service [Unit] Requires=vgp.master-ldap-400.service After=vgp.master-ldap-400.service JoinsNamespaceOf=vgp.master-ldap-400.service [Service] ExecStart=/usr/lib/systemd/systemd-socket-proxyd ${HOSTNAME}:400 PrivateTmp=yes PrivateNetwork=yes But still ldapsearch not working with ${HOSTNAME}:401. Some useful info # systemctl status proxy-to-directory-400.service â proxy-to-directory-400.service Loaded: loaded (/usr/lib/systemd/system/proxy-to-directory-400.service; static) Active: active (running) since Thu 2014-07-17 09:37:36 EEST; 5min ago Main PID: 32744 (systemd-socket-) CGroup: /system.slice/proxy-to-directory-400.service ââ32744 /usr/lib/systemd/systemd-socket-proxyd CLA-0:400 -- # ss -anp | egrep -wi 400|401|402|403|49502|haproxy tcpLISTEN 0 128 169.254.0.4:400 *:* users:((slapd,32743,7)) tcpLISTEN 0 128 :::401 :::* users:((systemd-socket-,32744,3),(systemd,1,26)) Any further help. On Thu, Jul 17, 2014 at 12:53 AM, David Timothy Strauss da...@davidstrauss.net wrote: On Wed, Jul 16, 2014 at 7:29 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: This won't work, since proxyd now cannot connect to port 400. There is now a way to make that work with JoinsNamespaceOf= -- Suvendu Mitra GSM - +358504821066 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-socket-proxyd slapd
On Thu, Jul 17, 2014 at 09:43:48AM +0300, Suvendu Mitra wrote: I have changed proxy-to-directory-400.service as # cat proxy-to-directory-400.service [Unit] Requires=vgp.master-ldap-400.service After=vgp.master-ldap-400.service JoinsNamespaceOf=vgp.master-ldap-400.service [Service] ExecStart=/usr/lib/systemd/systemd-socket-proxyd ${HOSTNAME}:400 PrivateTmp=yes PrivateNetwork=yes I'd try without Private* settings. Also, replace /usr/lib/systemd/systemd-socket-proxyd with '/bin/strace -o /tmp/log /usr/lib/systemd/systemd-socket-proxyd' and look at the log file. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-socket-proxyd slapd
want to start slapd with socket activation via 'systemd-socket-proxyd' , I can see that slapd is listening to port 400 sytemd create socket at 401. But ldapsearch doesn't work with port 401. Any help !! --- 1. $ cat proxy-to-directory-400.socket [Socket] ListenStream=401 [Install] WantedBy=sockets.target -- 2. $ cat proxy-to-directory-400.service [Unit] Requires=vgp.master-ldap-400. service After=vgp.master-ldap-400.service [Service] ExecStart=/usr/lib/systemd/systemd-socket-proxyd ${HOSTNAME}:400 PrivateTmp=yes PrivateNetwork=yes --- 3. [Unit] Description=Local OpenLDAP server After=vgp.master-ldapdb-400-get.service Requires=vgp.master-ldapdb-400-get.service [Service] Type=simple LimitNOFILE=4096 LimitCORE=infinity WorkingDirectory=/etc/ldapfiles/ ExecStart=/usr/local/libexec/slapd -d 0 -f /tmp/fsldap_400.conf -h ldap://${HOSTNAME}:400; -l LOCAL1 -- Suvendu Mitra GSM - +358504821066 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-socket-proxyd slapd
On Wed, Jul 16, 2014 at 7:29 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: This won't work, since proxyd now cannot connect to port 400. There is now a way to make that work with JoinsNamespaceOf= ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel