Mass edit root folder not working?

Help & Support
1

This may be my mistake.

I am testing out a vps w/ ubuntu 13.10. I cheated and copied my config files from my home system. Mostly worked, but I changed the root folder.

I tried to do a mass edit to change the root folder, and that had no effect I could see. But I can go in and change the folder of each tv series.

Any idea why the mass edit doesn’t work?

I"m going to fix it by symlinking. :smiley:

2

It takes a bit for the mass edit to go through and update all the series, the UI should update as its processing though.

3

Ok. I didn’t get any feedback. And when I tried to do just one series as a test, it didn’t do it either.

But this is a tiny atom server, so I’ll let it run for a while, and come back and check it. Symlinking is working fine for now.

EDIT: It’s been several hours, and this never did process. Poor little atom processor is being slammed b/c it’s downloaded a bunch of stuff, and Plex is indexing a lot. I’m going let it settle down, then try this again during a slow period just to be sure it wasn’t just a case of overloaded processor.

4

So tested this again today, after plex finished indexing media.

Watched in htop. Odd behavior. Drone seems to max 1 core, then trade off and max the other core, and then trade off again, continually swapping. Whichever core isn’t maxed is running 2-4%.

Just wondering if this is intentional, or not?

As to the actual process of changing the root folder for all 104 series . . . well, I let it run for a couple hours, and ti’s still pinging the cores, but none of my series show as having a changed root folder. :confused:

So, seems like a bug to me.

5

Could my issue be related to https://trello.com/c/xZ2sVFhI ?

I went from ubuntu 12.04 to 13.10.

Like I said above, I have a workaround that’s doing great, so it’s no big deal. Just info for you to help debug.

6

Saving was extremely slow due to it trying to update the UI, which didn’t work anyways. I have pushed a fix for that, now able to save 140+ shows in under a second. 2.0.0.1255 will have the fix.

7

Just an update, I’m still seeing the same behavior on 1255 on my Ubuntu 13.10 machine.