Blocking error message with Jdownloader

**Nomoon** · 05-09-12 at 09:49 AM

Glad this thread can help

I didn't have any more problem with JD since the update to Nightly build!

**wlad025** · 05-10-12 at 11:15 PM

Yesterday the latest update to official (stable) JD version has been released by JD team - but leaving the RS issue remain unsolved again, i.e. the update improved nothing.
So then I immediately switched to Nightly update, and everything is fine now! : )

Many thanks again guys - Nomoon, Noledox & robbo0000 - for helping to solve the problem that creators of the official JD could not manage to solve! : )

**robbo0000** · 05-11-12 at 01:30 AM

your welcome wlad025

**Nomoon** · 05-11-12 at 12:50 PM

I just created the thread... all the credit goes to those who found the solutions!

**wlad025** · 05-12-12 at 02:00 PM

Quote: Originally Posted by Nomoon

I just created the thread... all the credit goes to those who found the solutions!

That's nice to be modest, however if you haven't started it at all I doubt the solution to our common issue would appear that quickly. So you are free to take the 1/3 part in credit share ; ) In my opinion, that alltogether was one quality brainstorming example, later mixed with trial&error methods regarding my own JD Nightly Edit docking station, hehe
Thanks all three of you once again!

hentesveis · 06-20-12 at 12:23 AM

well, I feel that it's not really a solution by going to NIGHTLY mode. (what is this?)

I have experienced the same issue, (Linux), and I see that if my computer has a lots of I/O, such as unpacking the rar's, uploading/downloading something in my LAN, the jdownloader chokes before my computer and I gets file error writes and permission denied. It works sometime when I enable it and force it to download, but usually I have to reset the file, e.g. downloading it again. Max Connectons and Downloads are at 4-5, it helps a bit when I set it down to 2-3.

The same apply when it have been up for few days, so I restarts the jdownloader after a 5-7 days, it seems (feels?) that it's easier to get file errors after a few days, especially with a lot of I/O on the harddisk.

The mechanical HDD don't likes several I/O at the same time, since the head have to move between two places at the same time, so I am looking at SSD, are these better at heavy I/O-traffic?

It's not a really problem for me, as I'm learning by these incidents. :)

**Noledox** · 06-20-12 at 12:59 AM

Quote: Originally Posted by hentesveis

well, I feel that it's not really a solution by going to NIGHTLY mode. (what is this?)

I have experienced the same issue, (Linux), and I see that if my computer has a lots of I/O, such as unpacking the rar's, uploading/downloading something in my LAN, the jdownloader chokes before my computer and I gets file error writes and permission denied. It works sometime when I enable it and force it to download, but usually I have to reset the file, e.g. downloading it again. Max Connectons and Downloads are at 4-5, it helps a bit when I set it down to 2-3.

The same apply when it have been up for few days, so I restarts the jdownloader after a 5-7 days, it seems (feels?) that it's easier to get file errors after a few days, especially with a lot of I/O on the harddisk.

The mechanical HDD don't likes several I/O at the same time, since the head have to move between two places at the same time, so I am looking at SSD, are these better at heavy I/O-traffic?

It's not a really problem for me, as I'm learning by these incidents. :)

NIGHTLY is the latest beta build. There are likely to be newer fixes (and bugs) in the nightly branch than in the stable build. I personally haven't seen a single I/O error since switching to the nightly branch.

hentesveis · 06-23-12 at 03:16 AM

Thanks for the explanation, I'll jump on it!

I have found a new bug/feature:
The jdownloader don't likes multiusers, it silently dies if one haven't write permission to the jdownloader-directory. Get the permission
("chmod -R 755 jdownloader" and "chown -R your_name.your_group jdownloader")
correct and it'll start nicely.
Just a little warning for these who don't use Windows.

caradepau06 · 01-08-13 at 12:51 PM

One thing I noticed about Jdown with cheesy file services like rapidgator (which will occasionally give those I/O errors or can't write to HD), is when I'm downloading from various services at the same time. AND, when there is a lot of disk activity (like when jdown unrar's file sets while downloading).

I never had any of those errors with RS or UL, while downloading from many different services and unraring file sets. I think it's a jdown / cheesy file service thing.

05-09-12 at 09:49 AM	#29
Nomoon Expert Join Date: May 2011 Location: Far from everything Posts: 964	Glad this thread can help I didn't have any more problem with JD since the update to Nightly build!

05-10-12 at 11:15 PM	#30
wlad025 Expert Join Date: Sep 2009 Posts: 823	Yesterday the latest update to official (stable) JD version has been released by JD team - but leaving the RS issue remain unsolved again, i.e. the update improved nothing. So then I immediately switched to Nightly update, and everything is fine now! : ) Many thanks again guys - Nomoon, Noledox & robbo0000 - for helping to solve the problem that creators of the official JD could not manage to solve! : )

05-11-12 at 01:30 AM	#31
robbo0000 ¯`·.¸¸.·´¯`·.¸><((((º> Join Date: May 2009 Location: Sydney Posts: 3,367	your welcome wlad025

05-11-12 at 12:50 PM	#32
Nomoon Expert Join Date: May 2011 Location: Far from everything Posts: 964	I just created the thread... all the credit goes to those who found the solutions!

05-12-12 at 02:00 PM	#33
wlad025 Expert Join Date: Sep 2009 Posts: 823	Quote: Originally Posted by Nomoon I just created the thread... all the credit goes to those who found the solutions! That's nice to be modest, however if you haven't started it at all I doubt the solution to our common issue would appear that quickly. So you are free to take the 1/3 part in credit share ; ) In my opinion, that alltogether was one quality brainstorming example, later mixed with trial&error methods regarding my own JD Nightly Edit docking station, hehe Thanks all three of you once again!

06-20-12 at 12:23 AM	#34
hentesveis Newcomer Join Date: Jun 2011 Posts: 72	well, I feel that it's not really a solution by going to NIGHTLY mode. (what is this?) I have experienced the same issue, (Linux), and I see that if my computer has a lots of I/O, such as unpacking the rar's, uploading/downloading something in my LAN, the jdownloader chokes before my computer and I gets file error writes and permission denied. It works sometime when I enable it and force it to download, but usually I have to reset the file, e.g. downloading it again. Max Connectons and Downloads are at 4-5, it helps a bit when I set it down to 2-3. The same apply when it have been up for few days, so I restarts the jdownloader after a 5-7 days, it seems (feels?) that it's easier to get file errors after a few days, especially with a lot of I/O on the harddisk. The mechanical HDD don't likes several I/O at the same time, since the head have to move between two places at the same time, so I am looking at SSD, are these better at heavy I/O-traffic? It's not a really problem for me, as I'm learning by these incidents. :)

06-20-12 at 12:59 AM	#35
Noledox Bad command or file name Join Date: Jul 2010 Location: Terra Incognita Posts: 2,709	Quote: Originally Posted by hentesveis well, I feel that it's not really a solution by going to NIGHTLY mode. (what is this?) I have experienced the same issue, (Linux), and I see that if my computer has a lots of I/O, such as unpacking the rar's, uploading/downloading something in my LAN, the jdownloader chokes before my computer and I gets file error writes and permission denied. It works sometime when I enable it and force it to download, but usually I have to reset the file, e.g. downloading it again. Max Connectons and Downloads are at 4-5, it helps a bit when I set it down to 2-3. The same apply when it have been up for few days, so I restarts the jdownloader after a 5-7 days, it seems (feels?) that it's easier to get file errors after a few days, especially with a lot of I/O on the harddisk. The mechanical HDD don't likes several I/O at the same time, since the head have to move between two places at the same time, so I am looking at SSD, are these better at heavy I/O-traffic? It's not a really problem for me, as I'm learning by these incidents. :) NIGHTLY is the latest beta build. There are likely to be newer fixes (and bugs) in the nightly branch than in the stable build. I personally haven't seen a single I/O error since switching to the nightly branch.

06-23-12 at 03:16 AM	#36
hentesveis Newcomer Join Date: Jun 2011 Posts: 72	Thanks for the explanation, I'll jump on it! I have found a new bug/feature: The jdownloader don't likes multiusers, it silently dies if one haven't write permission to the jdownloader-directory. Get the permission ("chmod -R 755 jdownloader" and "chown -R your_name.your_group jdownloader") correct and it'll start nicely. Just a little warning for these who don't use Windows.

01-08-13 at 12:51 PM	#37
caradepau06 Expert Join Date: Jun 2012 Posts: 944	One thing I noticed about Jdown with cheesy file services like rapidgator (which will occasionally give those I/O errors or can't write to HD), is when I'm downloading from various services at the same time. AND, when there is a lot of disk activity (like when jdown unrar's file sets while downloading). I never had any of those errors with RS or UL, while downloading from many different services and unraring file sets. I think it's a jdown / cheesy file service thing.