-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jackett cannot start after being updated #3671
Comments
Have a look at this issue in mono repository, support was broken for ARM arch : mono/mono#12537 (comment) |
thank you for your feedback. do have any idear where i can add this command? |
Edit the file |
Hi. Thank you. Now Jackett starts. But when i test to the indexer it fails:
|
I have the same issue in the logs when trying to add an indexer |
Sorry for bearing bad news, but from the upstream discussion @Kilay referenced above (mono/mono#12537 (comment)), it seems the issue has not been fixed so far. I don't have a clean solution. My best bet would be to downgrade |
Looks like this is still a problem:
|
@jbaun... checking on some older issues... is this still an ongoing concern or can this ticket be closed? |
Hi. Just close it 😀 |
@jbaun, did a newer version of Jackett or Mono resolve the issue you were having? |
Hi. I’m not sure. But I don’t have that NAS anymore so cannot test it. |
Okay, thanks for the feedback. Closing the issue per your request. |
For new Package Requests, see the guidelines
Setup
Package Name: Jackett / Mono
Package Version: 0.11.43-8 / 5.18.0.240-12
NAS Model: DS212+
NAS Architecture: 88f628x
DSM version: 6.2.1-23824 update 6
Expected behavior
Tell us what should happen:
Jackett shuld start
Actual behavior
Tell us what happens instead
Jackett does not start after update to v 0.11.43-8 (Mono v 5.18.0.240-12)
Steps to reproduce
1. update Mono and then Jackett.
2. try to start Jackett
3.
Package log
Check Package Center or
/usr/local/{package}/var/
Other logs
E.g.
/var/log/messages
or/var/log/synopkg.log
The text was updated successfully, but these errors were encountered: