starred/Lidarr

Fork 0

mirror of https://github.com/Lidarr/Lidarr.git synced 2026-03-02 22:56:57 -05:00

Lidarr not waiting for media to appear in remote path then cancels import #3764

New issue

Closed

opened 2026-02-20 02:20:49 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 02:20:49 -05:00

Owner

Originally created by @ofernander on GitHub (Jun 27, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

When download client (Deluge) tells Lidarr the media has been downloaded Lidarr looks in the remote directory but does not find the media (because it has not been downloaded locally yet) then cancels the import process, never to restart.

2024-06-28 01:19:58.1|Error|DownloadedTracksImportService|Import failed, path does not exist or is not accessible by Lidarr: /rseedsync/The Clash - Cut The Crap (1985 - Pop) [Flac 16-44]. Ensure the path exists and the user running Lidarr has the correct permissions to access this file/folder

Expected Behavior

Upon not finding the media in the remote directory should try again and again until it appears. Sonnar, Radarr, & Readarr work this way.

I use a local shell script and rsync to bring media from a seedbox and Lidarr should wait for it.

Steps To Reproduce

No response

Environment

- OS: 
- Lidarr: Version 2.3.3.4204
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Browser: Mozilla
- Database: sqlite

What branch are you running?

Master

Trace Logs?

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @ofernander on GitHub (Jun 27, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior When download client (Deluge) tells Lidarr the media has been downloaded Lidarr looks in the remote directory but does not find the media (because it has not been downloaded locally yet) then cancels the import process, never to restart. 2024-06-28 01:19:58.1|Error|DownloadedTracksImportService|Import failed, path does not exist or is not accessible by Lidarr: /rseedsync/The Clash - Cut The Crap (1985 - Pop) [Flac 16-44]. Ensure the path exists and the user running Lidarr has the correct permissions to access this file/folder ### Expected Behavior Upon not finding the media in the remote directory should try again and again until it appears. Sonnar, Radarr, & Readarr work this way. I use a local shell script and rsync to bring media from a seedbox and Lidarr should wait for it. ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: - Lidarr: Version 2.3.3.4204 - Docker Install: Yes - Using Reverse Proxy: Yes - Browser: Mozilla - Database: sqlite ``` ### What branch are you running? Master ### Trace Logs? 2024-06-28 01:19:58.1|Error|DownloadedTracksImportService|Import failed, path does not exist or is not accessible by Lidarr: /rseedsync/The Clash - Cut The Crap (1985 - Pop) [Flac 16-44]. Ensure the path exists and the user running Lidarr has the correct permissions to access this file/folder ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 02:20:49 -05:00

closed this issue
added the
Type: Bug

Type: Duplicate
labels

deekerman commented

2026-02-20 02:20:50 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jun 27, 2024):

Duplicate of https://github.com/Lidarr/Lidarr/issues/2746

Please actually search rather than simply checking the box....why lie and say you did?

Also Invalid Bug Report - OP failed to provide trace logs and lied about following the wiki. Why lie when you made no attempt to even follow the wiki?

@bakerboy448 commented on GitHub (Jun 27, 2024): Duplicate of https://github.com/Lidarr/Lidarr/issues/2746 Please actually search rather than simply checking the box....why lie and say you did? Also Invalid Bug Report - OP failed to provide trace logs and lied about following the wiki. Why lie when you made no attempt to even follow the wiki?

deekerman commented

2026-02-20 02:20:50 -05:00

Author

Owner

@ofernander commented on GitHub (Jun 27, 2024):

Duplicate of #2746

Please actually search rather than simply checking the box....why lie and say you did?

Also Invalid Bug Report - OP failed to provide trace logs and lied about following the wiki. Why lie when you made no attempt to even follow the wiki?

That's a lot of accusations and assumptions... I did search but not every search is perfect when key words are vague, and you said I didn't follow the wiki when in the issue you linked you yourself state it is a "known" issue.

I get that people posting "bug reports" that aren't perfect annoy you but try to come down off your high horse and be a human for a little bit. Or maybe it's time to step away from the FOSS community since it clearly cases you duress.

Anyway thanks for the info, I hope maybe my post has the right keywords to help anyone else with this issue.

@ofernander commented on GitHub (Jun 27, 2024): > Duplicate of #2746 > > Please actually search rather than simply checking the box....why lie and say you did? > > Also Invalid Bug Report - OP failed to provide trace logs and lied about following the wiki. Why lie when you made no attempt to even follow the wiki? That's a lot of accusations and assumptions... I did search but not every search is perfect when key words are vague, and you said I didn't follow the wiki when in the issue you linked you yourself state it is a "known" issue. I get that people posting "bug reports" that aren't perfect annoy you but try to come down off your high horse and be a human for a little bit. Or maybe it's time to step away from the FOSS community since it clearly cases you duress. Anyway thanks for the info, I hope maybe my post has the right keywords to help anyone else with this issue.

deekerman commented

2026-02-20 02:20:50 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jun 27, 2024):

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

you failed to follow this and lied claiming you did.

users that waste time by failing to complete bug reports properly and thinking they did are actually worse than users that open duplicates....

For future issues - please abide by the requirements of the template or expect them to be closed as invalid as noted may occur in the template

@bakerboy448 commented on GitHub (Jun 27, 2024): >> # Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. >> I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue. you failed to follow this and lied claiming you did. users that waste time by failing to complete bug reports properly and thinking they did are actually worse than users that open duplicates.... For future issues - please abide by the requirements of the template or expect them to be closed as invalid as noted may occur in the template

deekerman commented

2026-02-20 02:20:50 -05:00

Author

Owner

@ofernander commented on GitHub (Jun 27, 2024):

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

you failed to follow this and lied claiming you did.

users that waste time by failing to complete bug reports properly and thinking they did are actually worse than users that open duplicates....

For future issues - please abide by the requirements of the template or expect them to be closed as invalid as noted may occur in the template

My post was still informational enough that you clearly knew the issue I was having... but yes you are right I failed to provide a trace log. Either way I had my question answered, I see there is a commit that will fix this issue and my post might help others in the future.

Thanks again! Hope you can find some peace amongst all the idiots that "waste" your time LOL.

@ofernander commented on GitHub (Jun 27, 2024): > > > # Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. > > > > I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue. > > you failed to follow this and lied claiming you did. > > users that waste time by failing to complete bug reports properly and thinking they did are actually worse than users that open duplicates.... > > For future issues - please abide by the requirements of the template or expect them to be closed as invalid as noted may occur in the template My post was still informational enough that you clearly knew the issue I was having... but yes you are right I failed to provide a trace log. Either way I had my question answered, I see there is a commit that will fix this issue and my post might help others in the future. Thanks again! Hope you can find some peace amongst all the idiots that "waste" your time LOL.

deekerman commented

2026-02-20 02:20:50 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Jun 29, 2024):

I can't really reproduce this one, but even if it's not the right approach I think #4815 is what intends to fix.

My post was still informational enough that you clearly knew the issue I was having

Sadly we don't share the same installation to have the same behavior for a one line log to make sense. 😝 While spammy, trace logs might show some helpful information specific you one's configuration.

@mynameisbogdan commented on GitHub (Jun 29, 2024): I can't really reproduce this one, but even if it's not the right approach I think #4815 is what intends to fix. > My post was still informational enough that you clearly knew the issue I was having Sadly we don't share the same installation to have the same behavior for a one line log to make sense. 😝 While spammy, trace logs might show some helpful information specific you one's configuration.