[systemd-devel] systemd-socket-proxyd & slapd

[Suvendu Mitra]

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 <
david at davidstrauss.net> wrote:

> On Thu, Jul 17, 2014 at 4:51 AM, Zbigniew Jędrzejewski-Szmek
> <zbyszek at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140723/1415ac99/attachment.html>