Cyberduck Mountain Duck CLI

Opened on Feb 17, 2009 at 11:58:33 AM

Closed on Apr 9, 2009 at 12:52:23 PM

Last modified on May 9, 2009 at 6:00:45 PM

#2997 closed defect (worksforme)

Getting timestamp of ...

Reported by: andrzej@firlet.com Owned by: dkocher
Priority: normal Milestone: 3.2
Component: ftp Version: 3.1.2
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description

"Getting timestamp of ..." , and nothing happens. It is always when I’m trying overwrite file on remote host. Then it is impossible to delete this job from Transfers window and i have to restart app to be able to delete them

Change History (4)

comment:1 Changed on Mar 20, 2009 at 8:49:09 PM by dkocher

Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

comment:2 Changed on Apr 9, 2009 at 12:52:23 PM by dkocher

  • Milestone set to 3.1.3
  • Resolution set to worksforme
  • Status changed from new to closed

comment:3 Changed on Apr 15, 2009 at 10:48:17 PM by andrzej@firlet.com

Sorry for so long time. Here You can find logs from console 

2009-04-16 00:29:37,482 [Background] WARN  com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=dev.firlet.com/195.189.32.43,port=21,localport=63423]
2009-04-16 00:29:37,505 [Background] INFO  com.enterprisedt.net.ftp.FTPClient - No data channel to interrupt
2009-04-16 00:30:07,315 [main] WARN  com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=dev.firlet.com/195.189.32.43,port=21,localport=63425]
2009-04-16 00:30:07,315 [main] INFO  com.enterprisedt.net.ftp.FTPClient - No data channel to interrupt
2009-04-16 00:44:06,215 [Background] WARN  com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=dev.firlet.com/195.189.32.43,port=21,localport=63434]
2009-04-16 00:44:06,215 [Background] INFO  com.enterprisedt.net.ftp.FTPClient - No data channel to interrupt
2009-04-16 00:44:47,188 [Background] ERROR ch.cyberduck.core.ftp.FTPSession - IO Error: Connection reset

comment:4 Changed on May 9, 2009 at 6:00:45 PM by stonetownmike@gmail.com

I am experiencing the same problem with Cyberduck 3.2. It stopped when I reverted to Cyberduck 3.1.2. The only way I could exit Cyberduck 3.2 was by force quit. Console messages here: 

09/05/09 10:30:06 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:06,089 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - No UTF8 support 
09/05/09 10:30:15 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:15,556 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - No UTF8 support 
09/05/09 10:30:18 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:18,991 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - No PRET support 
09/05/09 10:30:19 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:19,223 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - No MFMT support 
09/05/09 10:30:19 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:19,249 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - UTIME not supported 
09/05/09 10:30:44 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:30:44,181 [Background] WARN  com.enterprisedt.net.ftp.FTPClient - No UTF8 support 
09/05/09 10:31:38 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:31:38,466 [Background] WARN  com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=stmarysmuseum.ca/216.251.32.92,port=21,localport=60385] 
09/05/09 10:31:38 AM [0x0-0x248248].ch.sudo.cyberduck[3513] 2009-05-09 10:31:38,466 [Background] INFO  com.enterprisedt.net.ftp.FTPClient - No data channel to interrupt 
09/05/09 10:32:06 AM com.apple.launchd[67] ([0x0-0x248248].ch.sudo.cyberduck[3513]) Exited with exit code: 143
Note: See TracTickets for help on using tickets.