Delete the install directory and try again. Don't delete the config directory though it you will lose your database.

 

If that doesn't work, check the logs for the app.

Delete the install directory and try again. Don't delete the config directory though it you will lose your database.

 

If that doesn't work, check the logs for the app.

 

I just did that and kept the config dir, it reinstalled all the install directory but failed to start in the end with the same message as before. Something about PID not started, for some reason....

 

I really don't want to lose my db.

What should I do?

There are some failed.db and failed.db-journal files in the config dir.

Move your config folder to somewhere else and see if it can start fresh. Then you'll know if it's the db or not that's corrupt.

Move your config folder to somewhere else and see if it can start fresh. Then you'll know if it's the db or not that's corrupt.

 

Same thing after i moved the config folder.

What should I look for in the log file?

Change the repo back to default and see if it starts sickbeard, then still it and change it back to sickrage. Make sure your db is backed up

Change the repo back to default and see if it starts sickbeard, then still it and change it back to sickrage. Make sure your db is backed up

 

Did that.

Sickbeard starts all right.

Sickrage fails with the same error.

 

Update: And I lost my config dir apparently. Stupidly I saved it under another name but under the Sickbeard_alt dir. And with the latest manipulations I cannot find my saved config dir anymore.

Try changing the port next, sorry to hear you lost your db

Are you planning on getting your plugins verified soonish or do they have no issues with 6.1 or do we need to hold off on updating for awhile if we want things to work without issue?

Hold off. I've been working furiously for the last 4 weeks (20 hours a week) on updating them for better dependency handling, and will update them for 6.1 at the same time. Hopefully a week or two.

 

Hold off. I've been working furiously for the last 4 weeks (20 hours a week) on updating them for better dependency handling, and will update them for 6.1 at the same time. Hopefully a week or two.

 

Thanks for all the hard work! Hope this is the last round of forced changes for awhile.

Try changing the port next, sorry to hear you lost your db

 

Changing the port doesn't help, and since I lost my db ....

Could you give me a procedure to clean up the whole thing and reinstall Sickrage from scratch, without any remains from the older install?

I guess there is something corrupted there, right?

If you use the uninstall button from within the plugin, then reboot after, delete your install directory and config directory, it will be clean. Then you can try again.

 

I'm working on a proper sickrage plugin which will release with the v3 updates. It's basically identical to sickbeard though so I'm not sure if it will help. Are you using unmenu or anything custom? What other plugins do you have installed?

I have a clean 6.0.1 install with 3 PhAze plugins. Sabnzbd, Transmission, and Sickrage which is broken now. That's all.

Make sure after uninstall that the /boot/config/plugins/Sickbeard folder deleted too (off the USB stick).

Make sure after uninstall that the /boot/config/plugins/Sickbeard folder deleted too (off the USB stick).

 

I did everything you wrote. Nothing works.

I an using the Sickbeard_alt version, right?

 

i really need some help here, please.

I am stuck.

 

Can't somebody please have a look at logs or some other files?

 

The weird thing is that I came back from vacation yesterday and although my internet connection was down Sickrage was running. But there was a message saying it needed to run some updates. After it started the updates it went for a reboot but never recovered.

HI Guys,

 

I have moved over from Sickbeard to use Sonarr. I have it running and it does what it should but for some reason when i check on it, its in a stopped status in unraid?? I'm not sure what information in relation to logs to present as there are a few.

 

regards

 

Bob

Do you mean it has stopped on the plugin settings page but is actually still running or do you mean it is crashing and stopping?

Hi Phaze,

 

i get it saying it has stopped on the plugin page, and on the gui it tells me it needs to reloaded.

 

r

 

Bob

If you know Linux, kill the process and start it again from the plugin, otherwise reboot the server. Sounds like it was restarted from within the app and the pid wasnt created.

I couldnt see the PID it created so i rebooted and when i open the plugin page its not started?

It will no longer start via the plugin page.

What unraid version are you running?

Phaze

 

Media server

5.0.5

 

Its runs sometime but it seems something that turns it off.

 

Been running with this all day and it still turns of at random times

Hello,

 

I need help here.

Sickrage won't start no matter what I do.

I checked after uninstall for leftovers using Winscp and couldn't find anything.

But after reinstall it still won't start. Says something about PID that couldn't start for some reason.

My guess is that it clashes with something else.

Not the port as I tried to change it already.

Maybe a dependency.

I am using a clean 6.0.1 install with 2 PhAze plugins only: Transmission and Sabnzbd.

Please can I get help from the next level? Like sending log files or running in debug mode?

I must bring it back to life.

 

Thanks

I managed to start Sickrage finally.

I simply toggled off the Force Update checkbox in the Setingts page in Unraid.

Just FYI, there is no next level for my plugins lol. I don't work for limetech.

 

Strange that the force update option fixed it. Did you change it to "yes"?