Skip to content
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

Open
rpesciotta opened this issue Nov 9, 2020 · 6 comments
Open

STDOUT not working #59

rpesciotta opened this issue Nov 9, 2020 · 6 comments
Labels

Comments

@rpesciotta
Copy link

rpesciotta commented Nov 9, 2020

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:

[root@6b28dbacc585 log]# find . -ls | grep vsftp
1104614   16 -rw-------   1 root     root        14757 Nov  9 19:18 ./vsftpd.log
970431    4 drwxr-xr-x   2 root     root         4096 Nov  9 19:00 ./vsftpd
970441    0 lrwxrwxrwx   1 root     root           11 Nov  9 19:00 ./vsftpd/vsftpd.log -> /dev/stdout

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:

[root@6b28dbacc585 log]# grep log /etc/vsftpd/vsftpd.conf
# Uncomment this to allow local users to log in.
## Enable logging
xferlog_enable=YES
xferlog_file=/var/log/vsftpd/vsftpd.log
xferlog_std_format=NO

Am I doing something wrong, or is there maybe a problem here?
I appreciate any support.

@sm809
Copy link

sm809 commented Jan 25, 2021

+1 to the above. I am facing the exact same issue.

@vecjh
Copy link

vecjh commented Mar 22, 2021

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.

@eelcowen
Copy link

Looks like vsftpd logs to /var/log/vsftpd.log and not /var/log/vsftpd/vsftpd.log so the the run-vsftpd.sh script is incorrect.

@TmyWu
Copy link

TmyWu commented Oct 27, 2022

Is this repository still 'active'??
I also cannot see logs in STDOUT.

@fauria fauria added the look label Jan 27, 2023
@fauria
Copy link
Owner

fauria commented Jan 27, 2023

It is. Labeling this issue as look.

@DanceMore
Copy link

DanceMore commented Mar 20, 2023

yeah, I followed the documentation on DockerHub https://hub.docker.com/r/fauria/vsftpd

LOG_STDOUT doesn't seem to do anything. logs still land ""on disk"" inside the container. thanks for checking into it tho :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants