| Summary: | net-proxy/nutcracker: init script can't start nutcracker | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marcin Mirosław <bug> |
| Component: | Current packages | Assignee: | Patrick Lauer <patrick> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
# /etc/init.d/nutcracker start * Testing configuration ... [ ok ] * Starting Nutcracker [ ok ] # ps aux|grep nutcrack root 15189 0.0 0.0 11360 844 pts/1 S+ 17:17 0:00 grep --colour=auto nutcrack start-stop-daemon should contain "--wait 100", this allows to catch such problematic situation: * Testing configuration ... [ ok ] * Starting Nutcracker ... * start-stop-daemon: /usr/sbin/nutcracker died [ !! ] * ERROR: nutcracker failed to start Main problem is that nutcracker is starting as user nobody: USER="${USER:-nobody}" but user nobody doesn't has permissions to create pid file: PIDFILE="${PIDFILE:-/var/run/nutcracker.pid}" Something like: start_pre { check_path ... } should fix it. Reproducible: Always