#1
|
|||
|
|||
does not always create logs
JD2 does not always create logs when trying to manually update.
You need to restart the application twice. The problem occurs for a long time. It only creates a partial log, even though I have Debug Mode enabled permanently. Please look here: 04.08.17 09.01.57 <--> 04.08.17 09.01.58 jdlog://4207214015941/ |
#2
|
||||
|
||||
Send parameters to existing jD instance and exit: [--focus]
JDownloader is still running
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
Why do need to do a double restart jd, after the manual update to re-create the logs.
|
#4
|
||||
|
||||
What do you mean by *manual update* ?
__________________
JD-Dev & Server-Admin |
#5
|
|||
|
|||
Just click, check for new updates.
**External links are only visible to Support Staff****External links are only visible to Support Staff** |
#6
|
||||
|
||||
And what exactly happens? What is the problem?
__________________
JD-Dev & Server-Admin |
#7
|
||||
|
||||
you should only need a single restart
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] |
#8
|
|||
|
|||
This is a rare bug that occurs after updates
JDownloader is still running It is running, but has already been restarted to re-create the log file, it needs to restart again, that is, double restart. |
#9
|
||||
|
||||
You do NOT start JDownloader manually again.
Of course this will happen when you start JDownloader manually while it is still updating. You hit the update button, JDownloader shows update is ready, you click okay and let JDownloader proceed.
__________________
JD-Dev & Server-Admin |
|
|