Bug 2275464 - ExtendedLog For Proftpd Version 1.3.6e-7 On RHEL 8 Not Showing Correct UTC Offset
Summary: ExtendedLog For Proftpd Version 1.3.6e-7 On RHEL 8 Not Showing Correct UTC Of...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: proftpd
Version: epel8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-17 09:44 UTC by leighchapman
Modified: 2024-04-22 14:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description leighchapman 2024-04-17 09:44:42 UTC
Description of problem:

In using proftpd-1.3.6e-7.el8.x86_64 on RHEL 8, the ExtendedLog feature is not showing the UTC offset correctly in the log file. 

Version-Release number of selected component (if applicable): proftpd-1.3.6e-7.el8.x86_64


How reproducible:

In config /etc/proftpd.conf in the Global Section, the following lines were included additionally to those supplied per default with the proftpd rpm


  ExtendedLog                   /var/log/proftpd/access.log ALL default
  TransferLog                   /var/log/proftpd/transfers.log
  TimesGMT                        off
  SetEnv                          TZ :/etc/localtime

The TIMEZONE of the RHEL 8 Server is: Europe/Berlin (CEST, +0200)

Steps to Reproduce:
1.Start proftpd
2.Connect to localhost with ftp command and enter user + passwd
3.Check log /var/log/proftpd/access.log

Actual results:

In the log /var/log/proftpd/access.log, the following is seen ......


127.0.0.1 UNKNOWN - [17/Apr/2024:10:27:53 +0000] "USER bob" 331 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:10:27:57 +0000] "PASS (hidden)" 230 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:10:27:57 +0000] "SYST" 215 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:10:27:58 +0000] "PASV" 227 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:10:27:58 +0000] "LIST" 226 68
127.0.0.1 UNKNOWN bob [17/Apr/2024:10:28:00 +0000] "QUIT" 221 -

Expected results:

The +0000 should show +0200 for UTC offset for described TIMEZONE Europe/Berlin (CEST, +0200).



Additional info:

In testing with the same config on RHEL 9 with proftpd-1.3.8b-2.el9.x86_64 the +0200 is shown.

In the log /var/log/proftpd/access.log, the following is seen ......


127.0.0.1 UNKNOWN - [17/Apr/2024:09:44:10 +0200] "USER bob" 331 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:09:44:13 +0200] "PASS (hidden)" 230 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:09:44:13 +0200] "SYST" 215 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:09:44:14 +0200] "PASV" 227 -
127.0.0.1 UNKNOWN bob [17/Apr/2024:09:44:14 +0200] "LIST" 226 71
127.0.0.1 UNKNOWN bob [17/Apr/2024:09:44:16 +0200] "QUIT" 221 -


Also note with RHEL 7 proftpd-1.3.5e-12.el7.x86_64, the +0200 is also shown in the 
access.log so RHEL 7 + RHEL 9 are behaving differently to RHEL 8.

Comment 1 Paul Howarth 2024-04-21 11:02:58 UTC
I don't see any recent changes in the proftpd source that would account for this working on the EL-9 version, so this is likely to need more in-depth debugging.

I see though that in /usr/share/doc/proftpd/howto/Timestamps.html it suggests that using a timezone name in the TZ environment variable rather than a filename could be helpful. Could you try that?

Comment 2 leighchapman 2024-04-22 14:13:45 UTC
I have tried setting the following in /etc/proftpd.conf as mentioned but unfortunately the result is the same:-

  
#SetEnv                          TZ :/etc/localtime
SetEnv                          TZ Europe/Berlin


The access log shows the correct time for the above timezone but the +0000 is still there at the end of the timestamp ......

127.0.0.1 UNKNOWN - [22/Apr/2024:15:57:13 +0000] "USER bob" 331 -


Note You need to log in before you can comment on or make changes to this bug.