Report client bugs
alexsandroos
Posts: 4 Joined: Mon Mar 06, 2017 2:46 pm
Post
by alexsandroos » Fri Mar 10, 2017 2:11 pm
Sometimes when I start my coreFTP Pro version 1885 in my server, the CoreFTP freeze and he works only when kill the task and open again.
Logs are incomplete.
I verified all the possibilities of be the server memory or something similar and I didn't have results.
Is it possible the client's servers are freezing my coreFtp when I connect with they ?
cp
Posts: 124 Joined: Sun Sep 11, 2011 5:18 am
Post
by cp » Wed Mar 15, 2017 4:56 am
sometimes you will not be able to connect to servers (due to connectivity issues) and you'll just need to wait for I to timeout (usually 30-60 seconds).
alexsandroos
Posts: 4 Joined: Mon Mar 06, 2017 2:46 pm
Post
by alexsandroos » Wed Mar 15, 2017 12:29 pm
I got it, but is it normal coreftp does not make a complete log ?
Because if I have connectivity issues so that should be in the log.
cp
Posts: 124 Joined: Sun Sep 11, 2011 5:18 am
Post
by cp » Thu Mar 16, 2017 2:06 pm
the log may not be complete until the process has finished.
Are you using the command line? If so use corecmd.exe until the process is complete.
alexsandroos
Posts: 4 Joined: Mon Mar 06, 2017 2:46 pm
Post
by alexsandroos » Tue Mar 21, 2017 3:49 pm
It doesn't work because process never get back to normal after issue. He only get back if I kill process.
cp
Posts: 124 Joined: Sun Sep 11, 2011 5:18 am
Post
by cp » Wed Mar 22, 2017 3:52 am
This isn't really a recommended option, but try adding:
-monitor 120
to the command line. This will kill the process if nothing happens after 120 seconds. Then check and see if there is any output in the log file.
alexsandroos
Posts: 4 Joined: Mon Mar 06, 2017 2:46 pm
Post
by alexsandroos » Mon Apr 03, 2017 12:49 pm
I tried this and there is no output in log file and the same happens when I change to "corecmd".