#1
|
|||
|
|||
JD2 Failing on every update - Manual work around works but...
From about 3 weeks ago, JD2 is failing on every update with an error insufficient permissions to write to...
If I use the manual work round this works fine, but I have to reinstall FFMPEG plugin every time subsequently. One thing I noticed is that in following the manula work around, when you go to delete the \tmp directory, it fails as it is in use. The subdirectory\updates is what it fails on, and to get this to allow deletion, I have to kill the actual JVM process ? This was working sweet as until about 3 weeks ago, and no changes I can think of on my side. Any assistance welcomed.:outch::outch: |
#2
|
||||
|
||||
Sounds like either permission issues on your site or firewall/av.
What system are you using? Where is your JDownloader installed? Can you please provide logs/screenshots of the error?
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
AVAST Pro 18.6.2349 (latest)
Only Windows FW %%appdata%%\local\J Downloader 2\ Screens attached - note especially that if I kill manually all Java processes (Update_Sceduler + Java VM), the update works just fine. It would appear that the JVM is holding a key file open preventing update during download ? |
#4
|
||||
|
||||
We would like to do a Teamviewer session with you. The screenshot shows that the jar file is still opened by some process and that blocks the update.
Please contact us via support@jdownloader.org I'm sure we can solve this.
__________________
JD-Dev & Server-Admin |
#5
|
|||
|
|||
Hi Jiaz
My work round works so would be near 100% certain of the process holding the file open. See screenshot for the Java processes I have to kill before running a successful update. Even now, if I run the update, JD2 closes, but process still running. Meantime the Java SE process has started. I need to now manually kill the Java SE process and immediately JD2 completes the update. |
#6
|
||||
|
||||
There is a reason that this java process doesn't close itself and that's what we need to find out. And the easiest/fastest way would be to debug/check this on your setup as you're encountering the issue. We cannot fix/debug an issue that we don't know of/can't reproduce nor have any clues what is going on.
I can only tell from the past that update issues has been caused by Firewall/AV/permission issues in nearly all cases.
__________________
JD-Dev & Server-Admin |
#7
|
|||
|
|||
Appears to be working again now ? Please close and thanks for the help
|
#8
|
||||
|
||||
Please report back in case you encounter it again, because there has been no chances to this.
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|