Thread: Strange Error on Seedbox :/

I got a semi-dedi-france from Xirvik, had this strange error of files getting downloaded but rutorrent never considers it completed and hence doesnt seeds back !!

have got a screenshot:





the ram was at 80% and ~28 Gb free hard disk, 52 torrents running.
the "Storage Error : File Chunk error .." was also present.
So, its 2 probs at the same time. The storage error is related to ram and any suggestions on settings will b helpful (atm settings are at default as recd frm Xirvik)

My main problem is with this new problem of not recognising the downloaded data and not seeding back. Another point is that this error takes place only on smaller size files !!
Has anyone else faced this problem ? What could be the reason for this ? and any suggestions to rectify this problem ?

You could try increase the max_memory_usage until it stops.
Reduce the number of Up/Down Slots.

#327 (rtorrent 0.6.1 error)
#1518 (Storage error: [File chunk write error: Cannot allocate memory.])

Originally Posted by Immortilus

You could try increase the max_memory_usage until it stops.
Reduce the number of Up/Down Slots.

#327 (rtorrent 0.6.1 error)
#1518 (Storage error: [File chunk write error: Cannot allocate memory.])

Changing those in ruTorrent will only fix it temporarily, if at all, as the settings will just revert right back. Plus messing with the those settings is not a good idea on a shared seedbox cause it effects everyone else on the server. Xirvik has those pre-set for a reason.

@ danny

Unless u have SSH access to the server then u need to contact Xirvik support, so they can handle this for u. There's nothing u can do to permanently fix your errors except lower the amount of torrents u have active.

danny u're using up your available ram when u get those errors. Like Mike said, lower the active running torrents and the error will go away by itself

i think the easiest way to prevent this is to limit the amount of high speed torrents. Keep only 1 or 2 running at very high dl/ul speed. Then slowly stop the non-active torrents until the error goes away

I have had similar issues with xirvik before i switched to a different provider. The best thing to do is to contact their support, they are usually fast in replying, if they cant resolve the issue, i suggest you switch providers or reduce number of torrents simultaneously downloading as mentioned above.

Originally Posted by MikeD

Changing those in ruTorrent will only fix it temporarily, if at all, as the settings will just revert right back. Plus messing with the those settings is not a good idea on a shared seedbox cause it effects everyone else on the server. Xirvik has those pre-set for a reason.

@ danny

Unless u have SSH access to the server then u need to contact Xirvik support, so they can handle this for u. There's nothing u can do to permanently fix your errors except lower the amount of torrents u have active.

thanks for all the wonderful advice guys. I tried the settings advice, it was temporary and reverted to default automatically. I have run the same box with 240 torrents without problems !! and running only 50 torrents stumbles me. The ram was also not at peak ~80% but since yesterday night, its been running at 100%, other users on my range are having similar errors, there was some commotion regarding it at the rutorrent shoutbox. Let me try Xirvik-Support.
Although, I am unsure,whether, they can be of much help with this.
uTorrent server based on Linux was released yesterday. This is gr8 news, hopefully, Xirvik replaces rutorrent with the more familiar utorrent !!

Originally Posted by danny

other users on my range are having similar errors, there was some commotion regarding it at the rutorrent shoutbox. Let me try Xirvik-Support.
Although, I am unsure,whether, they can be of much help with this.
uTorrent server based on Linux was released yesterday. This is gr8 news, hopefully, Xirvik replaces rutorrent with the more familiar utorrent !!

maybe the good guys at xirvik tested the alpha utorrent causing the issue
but well this is an OT joke lol

this error is strange sometimes and i think the more fast speed torrents running the faster this error comes. It's not like the torrent would stop/malfunction but it's just annoying...