boatdesign

Well-Known Member
Sep 13, 2003
158
0
166
Something odd here -- timezone on server is set to GMT -5 (EST)

My timezone is GMT -5 (EST)

Yet pure-ftpd for some reason is offset an hour, saying now at 9:51 that the file was uploaded to the server at 10:51

Server time shows as 21:51 according to uptime, etc.

Any ideas?
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
Something odd here -- timezone on server is set to GMT -5 (EST)

My timezone is GMT -5 (EST)

Yet pure-ftpd for some reason is offset an hour, saying now at 9:51 that the file was uploaded to the server at 10:51

Server time shows as 21:51 according to uptime, etc.

Any ideas?
Is it only pure-ftp or other items as well? If it is for everything, ensure your time settings reflect the correct country/locale. The US is currently in EDT whereas Canada is currently in EST, which would explain a 1 hour discrepancy in that direction.
 

boatdesign

Well-Known Member
Sep 13, 2003
158
0
166
Need to do more testing.

Local machine I'm on right now is Vista 32-bit set to Eastern Standard Time but with the "adjust clock for daylight savings" checked.
Local time shows as 5:01 PM

Server time in WHM shows as:
Thu Mar 20 17:01:01 EDT 2008

When I upload a file with FileZilla 3.0.8.1 the time in the remote pane for the file just uploaded at 5:03 local time shows as 6:03 P.M.
I then downloaded the file again from the server and the new time in the local pane of filezilla shows 5:03 P.M. in the local window, 6:03 P.M. in the remote window.
 

boatdesign

Well-Known Member
Sep 13, 2003
158
0
166
As far as I can tell, the only thing affected is FTP on my two cpanel 11 servers.

WHM shows time correctly as
Fri Apr 4 00:14:21 EDT 2008
America/Detroit

Vista (local machine) shows time as
Friday, April 04, 2008
12:14:29 AM
(GMT-05:00) Eastern Time (US & Canada)

However, when I ftp a file to the server the remote time as reported by FileZilla as:
time.jpg 4/4/2008 1:17:00 AM which is one hour in the future

At the SSH prompt however it shows as:
42475 Apr 4 00:17 time.jpg which is correct

uptime shows system time as 00:18:40 which is correct.

Now I'd suspect it's a filezilla issue, but if I connect to a non-cpanel FutureQuest virtual hosting account the time of the transferred file is right on the money.

So something about my pure-ftpd cpanel install is telling FileZilla that it's one hour off.

(I can correct this by manually setting each site in filezilla to have a -1 hour time offset, but this only solves the problem for me, not anyone else using filezilla to connect to my pure ftpd web server.

Any ideas?
 

boatdesign

Well-Known Member
Sep 13, 2003
158
0
166
I guess this says it all:

Status: Calculating timezone offset of server...
Command: MDTM .htaccess
Response: 213 20080225082109
Status: Timezone offsets: Server: -18000 seconds. Local: -14400 seconds. Difference: 3600 seconds.
Status: Directory listing successful
But why? When the server time in WHM does match my Vista local time??? What am I missing here?
 

LiNUxG0d

Well-Known Member
Jun 25, 2003
206
1
168
Gatineau, Quebec, Canada
Hey there boatdesign,

I know this sounds really weird... but... what does the FTP banner state?

Code:
[[email protected] ~]# ftp localhost
Connected to localhost (127.0.0.1).
220---------- Welcome to Pure-FTPd [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 11:06. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
Name (localhost:root): ?
Mine shows 11:06... if it shows 11:06 then the pure-ftpd service is saying 11:06 and I'd suspect maybe your transfer application is showing the wrong time. Do you have a screen shot of what you're seeing?

Thanks,
 

boatdesign

Well-Known Member
Sep 13, 2003
158
0
166
Connected to localhost.
220---------- Welcome to Pure-FTPd [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 21:26. Server port: 21.

uptime
21:26:07

The filezilla forum seems to say that there is something about the way pureftp that is not "standards compliant" causing the issue after the filezilla 3 update that is "standards compliant"

http://forum.filezilla-project.org/...sid=1f17c0d1b94dd1b7caa2698f06066edf&start=15

As required in RFC 3659 (http://filezilla-project.org/specs/rfc3659.txt), FileZilla assumed MDTM returns timestamps in UTC. Based on the timestamp return in the LIST reply and the corresponding MDTM reply, it calculates the timezone offset of the server.

Obviously this fails on broken or misconfigured servers.

I can assure you that it works fine on all standards-compliant servers.