Portal Home > Knowledgebase > Articles Database > pure-ftpd + filezilla = 1 hour time offset problem
pure-ftpd + filezilla = 1 hour time offset problem
| Posted by panopticon, 04-07-2008, 08:55 PM |
| Timezone on server is set to GMT -5 EDT
My timezone is GMT -5 EDT
Yet filezilla 3.x ftp client connected to my server's pure-ftpd server offsets time on transferred files by an hour, saying now at 8:52 that the file was uploaded to the server at 9:52.
WHM and uptime, etc. at the SSH prompt show server time correct, matching my own time.
But connecting via filezilla 3 I get:
Status: Calculating timezone offset of server...
Command: MDTM .htaccess
Response: 213 20080208013750
Status: Timezone offsets: Server: -18000 seconds. Local: -14400 seconds. Difference: 3600 seconds.
Status: Directory listing successful
If I connect locally to pure-ftp via the server shell ftp, I get
Connected to localhost.
220---------- Welcome to Pure-FTPd [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 20:52. Server port: 21.
which matches
$ uptime
20:52:28
The filezilla forums however indicate the problem is due to some "non-standards compliant setup" of my ftp server.
http://forum.filezilla-project.org/viewtop...df&start=15
Is there something I can tweak with pure-ftpd, or is this a Filezilla 3 bug?
|
| Posted by foobic, 04-07-2008, 09:06 PM |
| What does date -u show?
|
| Posted by panopticon, 04-07-2008, 09:53 PM |
| date -u
Tue Apr 8 01:53:05 UTC 2008
at
date
Mon Apr 7 21:53:46 EDT 2008
9:53 p.m. my time (EDT)
|
| Posted by foobic, 04-08-2008, 12:42 AM |
| Well, on the face of it you and the server are GMT -4 and pure-ftpd is incorrectly on GMT -5. Is it using an old copy of etc/localtime maybe?
You can check by using MDTM yourself through shell ftp. Just touch a file, date -u to show current utc time and compare to:
|
| Posted by panopticon, 04-08-2008, 01:35 AM |
| That's a good question - server is RHEL5 updated via yum (WHM/cpanel server install of pure-ftpd)
ls -al /etc/localtime
-rw-r--r-- 1 root root 2202 Apr 4 00:13 /etc/localtime
date
Tue Apr 8 01:29:54 EDT 2008
touch time.txt
ftp> quote MDTM time.txt
213 20080408053058
quit
ls -al time.txt
-rw-r--r-- 1 root root 0 Apr 8 01:30 time.txt
Last edited by panopticon; 04-08-2008 at 01:38 AM.
|
| Posted by RBBOT, 04-08-2008, 02:34 AM |
| May be one machine has daylight savings time enabled and one disabled?
|
| Posted by foobic, 04-08-2008, 02:38 AM |
| date -u would have made it easier to compare, but that's correct isn't it? MDTM reports 2008/04/08 05:30:58 which fits with your GMT -4.
If dir also reports the correct local time then it's hard to see where Filezilla's getting the 5 hour offset.
|
| Posted by panopticon, 04-08-2008, 03:14 AM |
| OK, so this appears to be a Filezilla 3.0.8.1 bug and not something that I can fix server-side. Thank you very much for your help.
ftp> quote MDTM time.txt
213 20080408071209
ftp> quit
# date -u
Tue Apr 8 07:12:39 UTC 2008
|
| Posted by panopticon, 04-08-2008, 06:26 PM |
| Of course the weird thing is that the same Filezilla client on the same client machine connected to FutureQuest's twoftpd server does not have the one-hour-time-offset it does when connecting to the pure-ftpd server above. So there's something about pure-ftpd and Filezilla that isn't working well together, but I can't figure out what. Truly odd.
|
| Posted by foobic, 04-08-2008, 06:38 PM |
| From the thread you linked:
You didn't by any chance use this previously to adjust the server time??
|
Add to Favourites 
Print this Article
Also Read
