-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STDOUT not working #59
Comments
+1 to the above. I am facing the exact same issue. |
I guess this is because "xferlog_file" is only used if "xferlog_std_format=YES". Otherwise the path is driven by "vsftpd_log_file" which is not defined in this container. |
Looks like vsftpd logs to |
Is this repository still 'active'?? |
It is. Labeling this issue as |
yeah, I followed the documentation on DockerHub https://hub.docker.com/r/fauria/vsftpd
|
Hi, I've tried for the first time using this image, and I noticed that the STDOUT is not working as I expected, since I don't see any connect or transfer messages.
I'm starting the container using docker-compose, and I set the Environment Variable as documented.
However, after testing for sometime, I only saw one single log message on the console.
So I opened a terminal inside the running container, and I noticed there are 2 vsftpd.log files under /var/log, as follows:
/var/log:
Apparently, the location /var/log/vsftpd/vsftpd.log has been corretly redirected to /dev/stdout, but the most messages are being logged into a different location, /var/log/vsftpd.log.
I checked the configuration file being used, and it does point to the location that is redirected to stdout, but for some reason, the situation I just described is taking place.
/etc/vsftpd/vsftpd.conf:
Am I doing something wrong, or is there maybe a problem here?
I appreciate any support.
The text was updated successfully, but these errors were encountered: