Hello,
I have encountered a couple of issues with stunnel 4.45 on RHEL 5.5.
I tried configuring stunnel to log messages in /var/log/messages and later found that messages were logged both in that file AND /var/log/messages.
In stunnel.conf, I had specified: debug=local6.info
In syslog.conf: local6.* /var/log/stunnel.log
I could achieve what I wanted only with the combination of the following two options: syslog=no output=/usr/local/app/stunnel/var/stunnel.log
Is this expected?
The second issue I have noticed is that stunnel seems to have a bit of trouble handling the hup signal. If you start stunnel specifying a relative path to the config, sending hup will cause stunnel to log and error but it won't exit.
2012.03.01 16:31:29 LOG5[19000:0]: Reading configuration from file etc/server.conf 2012.03.01 16:31:29 LOG3[19000:0]: etc/server.conf: No such file or directory (2) 2012.03.01 16:31:29 LOG3[19000:0]: Cannot read configuration 2012.03.01 16:31:29 LOG3[19000:0]: Failed to reload the configuration file
If you specify an absolute path, no error will be reported but stunnel will exit anyway.
I tried configuring stunnel to log messages in /var/log/messages and later found that messages were logged both in that file AND /var/log/messages.
Someone explained that happened because of *.info in syslog.conf on RHEL:
*.info;mail.none;authpriv.none;cron.none /var/log/messages
Adding ";local6.none" at the end of the line worked fine.
Philippe A. wrote:
I tried configuring stunnel to log messages in /var/log/messages and later found that messages were logged both in that file AND /var/log/ messages.
/var/log/messages *and* /var/log/messages? Are you sure?
I could achieve what I wanted only with the combination of the following two options: syslog=no output=/usr/local/app/stunnel/var/stunnel.log
Is this expected?
Yes, it is.
The second issue I have noticed is that stunnel seems to have a bit of trouble handling the hup signal. If you start stunnel specifying a relative path to the config, sending hup will cause stunnel to log and error but it won't exit.
I guess you try to reload configuration within chroot, but you forgot to copy stunnel.conf to your chroot jail. My recommendation is to disable chroot.
Mike
2012/3/4 Michal Trojnara Michal.Trojnara@mirt.net
Philippe A. wrote:
The second issue I have noticed is that stunnel seems to have a bit of
trouble handling the hup signal. If you start stunnel specifying a relative path to the config, sending hup will cause stunnel to log and error but it won't exit.
I guess you try to reload configuration within chroot, but you forgot to copy stunnel.conf to your chroot jail. My recommendation is to disable chroot.
I am not using chroot.
-
Michal Trojnara -
Philippe A.