[Supervisor-users] docker + supervisord + nslcd = no-go

[Jason Swindle]

Howdy,

I have been trying all day to make nslcd work correctly inside of Docker
with SupervisorD. Sadly, I have had no luck at all.

Exit code
```
echo $? `/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid /usr/sbin/nslcd`
0
```

conf file
```
[program:nslcd]
command=/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid /usr/sbin/nslcd
autostart=true
autorestart=true
user=nslcd
```

Log File
```
2014-05-19 19:39:17,816 INFO gave up: nslcd entered FATAL state, too many
start retries too quickly
2014-05-19 19:49:00,741 INFO spawned: 'nslcd' with pid 553
2014-05-19 19:49:00,821 INFO exited: nslcd (exit status 0; not expected)
2014-05-19 19:49:01,824 INFO spawned: 'nslcd' with pid 555
2014-05-19 19:49:01,907 INFO exited: nslcd (exit status 0; not expected)
2014-05-19 19:49:04,714 INFO spawned: 'nslcd' with pid 557
2014-05-19 19:49:04,795 INFO exited: nslcd (exit status 0; not expected)
```

supervisorD version 3.0

Thanks,
Jason

[Chris McDonough]

What is nslcd? Is there a variant of it that doesn't daemonize itself?

Post by Jason Swindle
Howdy,
I have been trying all day to make nslcd work correctly inside of Docker
with SupervisorD. Sadly, I have had no luck at all.
Exit code
```
echo $? `/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid
/usr/sbin/nslcd`
0
```
conf file
```
[program:nslcd]
command=/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid
/usr/sbin/nslcd
autostart=true
autorestart=true
user=nslcd
```
Log File
```
2014-05-19 19:39:17,816 INFO gave up: nslcd entered FATAL state, too many
start retries too quickly
2014-05-19 19:49:00,741 INFO spawned: 'nslcd' with pid 553
2014-05-19 19:49:00,821 INFO exited: nslcd (exit status 0; not
expected)
2014-05-19 19:49:01,824 INFO spawned: 'nslcd' with pid 555
2014-05-19 19:49:01,907 INFO exited: nslcd (exit status 0; not
expected)
2014-05-19 19:49:04,714 INFO spawned: 'nslcd' with pid 557
2014-05-19 19:49:04,795 INFO exited: nslcd (exit status 0; not
expected)
```
supervisorD version 3.0
Thanks,
Jason
------------------------------------------------------------------------
_______________________________________________
Supervisor-users mailing list
https://lists.supervisord.org/mailman/listinfo/supervisor-users

[Chris McDonough]

The reason I ask is because supervisor runs programs. It doesn't care what those programs are as long as they don't daemonize.

Post by Chris McDonough
What is nslcd? Is there a variant of it that doesn't daemonize itself?

Post by Jason Swindle
Howdy,
I have been trying all day to make nslcd work correctly inside of Docker
with SupervisorD. Sadly, I have had no luck at all.
Exit code
```
echo $? `/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid
/usr/sbin/nslcd`
0
```
conf file
```
[program:nslcd]
command=/usr/local/bin/pidproxy /var/run/nslcd/nslcd.pid
/usr/sbin/nslcd
autostart=true
autorestart=true
user=nslcd
```
Log File
```
2014-05-19 19:39:17,816 INFO gave up: nslcd entered FATAL state, too many
start retries too quickly
2014-05-19 19:49:00,741 INFO spawned: 'nslcd' with pid 553
2014-05-19 19:49:00,821 INFO exited: nslcd (exit status 0; not
expected)
2014-05-19 19:49:01,824 INFO spawned: 'nslcd' with pid 555
2014-05-19 19:49:01,907 INFO exited: nslcd (exit status 0; not
expected)
2014-05-19 19:49:04,714 INFO spawned: 'nslcd' with pid 557
2014-05-19 19:49:04,795 INFO exited: nslcd (exit status 0; not
expected)
```
supervisorD version 3.0
Thanks,
Jason
------------------------------------------------------------------------
_______________________________________________
Supervisor-users mailing list
https://lists.supervisord.org/mailman/listinfo/supervisor-users

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
------------------------------------------------------------------------
_______________________________________________
Supervisor-users mailing list
https://lists.supervisord.org/mailman/listinfo/supervisor-users