update releases stuck in loop?

[phirestalker]

I have left the scripts running for about 30 mins, and the logs still show the same thing over and over.

Process Releases -> Create releases from complete collections.
0 Collections ready to be converted to releases.

0 Releases added and 0 duplicate collections deleted in 0 second(s)

Process Releases -> Create the NZB, delete collections/binaries/parts.
1,539 NZBs created/Collections deleted in 4 seconds.
Total time: 4 second(s)


Process Releases -> Create releases from complete collections.
0 Collections ready to be converted to releases.

0 Releases added and 0 duplicate collections deleted in 0 second(s)

Process Releases -> Create the NZB, delete collections/binaries/parts.
1,539 NZBs created/Collections deleted in 4 seconds.
Total time: 4 second(s)

I can't find any errors, it just keeps processing the same set of NZBs from what it looks like.

What could be wrong?

I am running the scripts sequential

[phirestalker]

ok I had to enable several debug options in settings.php but I found the error

General error: 1449 The user specified as a definer ('nzedb'@'localhost') does not exist]

I moved my database from localhost and updated config.php, so I'm not sure where it is getting this from.

[kaibosh]

When the DB was migrated (in your other thread) the stored procedures were likely not copied as it requires a special --routines option on mysqldump.

Check their existence with this query:

Code: [Select]

show procedure status;
Either the DB could be migrated again with this option active, alternatively an option is to recreate the stored procedures from the end of this file:
https://github.com/nZEDb/nZEDb/blob/0.x/resources/db/schema/mysql-ddl.sql

Edit: There should be two stored procedures named: delete_release and loop_cbpm.

[phirestalker]

Yep that's definitely it. In this case the problem is that the procedures were copied. The user is no longer localhost on the new server, I had deleted it to keep out redundant or unecessary entries.

After I posted I thought I would cheat and just recreate the user. Even though the user is now logging in remotely, just the existence of the localhost entry allows the stored procedures to work.

Quick question, since the procedures are already there, can I just edit the localhost part to reflect the correct host the user is connecting from?