Opened 6 years ago

Closed 3 years ago

#10938 closed defect (moved_to_github)

sslh can't start due to pid file access error

Reported by: jacob.myers@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: sslh Cc:


sslh package defaults the PID file to /var/run/, but it attempts to do this as the user nobody and thus fails with an error since there is no write permission for the user in that directory. This is the built in default pid file location, no configuration options are available for it in the init script/config file provided in the package, though the -P option is available to specify it through sslh.

This prevents being able to use sslh, since the error prevents it from starting up at all. There are several possible solutions that I can think of, I don't know what is the most correct one to go with:

  1. Modify /etc/init.d/sslh (2 possible options)
    1. Add a command to touch /var/run/ and then chown nobody /var/run/ or chmod 777 /var/run/ before running sslh OR
    2. Just change the pid file location, add -P /tmp/ or something like that to the argument list to pass to sslh on startup
  1. Modify /etc/config/sslh
    1. Add a PID file configuration directive here that points to somewhere such as /tmp/
    2. Update /etc/init.d/sslh to know how to add the -P parameter using this cofiguration option
  2. Modify sslh source to work with the pid file before the user change/fork thus it will have access to the filesystem properly to take care of the problem itself

I am unsure if this is an underlying problem in sslh and thus the source should be patched/adjusted appropriately or if simply handling it via the init.d/sslh script is a better option.

Attachments (0)

Change History (2)

comment:1 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:2 Changed 3 years ago by jogo

  • Resolution set to moved_to_github
  • Status changed from new to closed

sslh is now maintained here:

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.