Opened 5 weeks ago

Last modified 6 days ago

#12534 new Bug report

Logging to files does not work

Reported by: Raffael Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc:
Component version: 1.0.1 Operating system type:
Operating system version:

Description

When I select "log to file" then I see that the file is empty. Sometimes when I stop the server then suddenly the file is filled with all the log information. But not always.

So this feature does not work as expected.

Attachments (1)

Screenshot 2021-10-22 102349.png (10.8 KB ) - added by Michael Magill 6 days ago.
Settings screenshot

Download all attachments as: .zip

Change History (7)

comment:1 by Michael Magill, 7 days ago

Same issue here. No matter what I try, I can't seem to make it log to a file after I upgraded from 0.9.60 beta. I have tried all the way up to 1.1.0-beta1. Running on Windows server 2019

comment:2 by Fabio Alemagna, 6 days ago

Could you please show what kind of configuration you are setting in the server?

Thanks.

by Michael Magill, 6 days ago

Settings screenshot

comment:3 by Michael Magill, 6 days ago

I attached a screenshot of the current settings. I have tried multiple different locations, including C:\Logs. The Filezilla user the service is running as has Full control permissions to the folders I have tried.

I have also tried leaving the service running as System and logging it to different places, including C:\Logs and C:\Program Files\FileZilla Server\Logs, which is where I used to log for 0.9.60 beta.

comment:4 by Fabio Alemagna, 6 days ago

As the label in the settings window should suggests, a file path is required, but you're using a directory path instead.

Give a name to your log file, FileZilla Server will use that one and rotate it as needed.

comment:5 by Michael Magill, 6 days ago

Adding a filename started logged to the file immediately for me, thanks! I think that wording is very unclear. When I see "File path" I read that as what path should be used for the files, not what path and filename should be used.

Can you describe how rotation works? I assumed it would be like previous version where it would rotate daily and auto-name the files with a date e.g. fzs-2021-04-05.log. Specific questions:
Does it rotate the file daily, or only when it hits the maximum size?
What naming convention does it use when rotating?
If it rotates daily, are there variables like %d or something we can use the in the filename to add the date to the name?
Is there any way to ensure you have a specific number of days of logs available, regardless of size?

comment:6 by Michael Magill, 6 days ago

Also please don't mark this ticket resolved, as I see now that my issue is not the same as the OP and I have hijacked his ticket.

For what its worth, his ticket just sounds like it isn't flushing the log to disk as often as he expects.

Note: See TracTickets for help on using tickets.