[Docker] Fresh master installation, no nzbs generated

[connorxxl]

Hello,

my new installation doesn't generate any nzbs.

I've created an nZEDb docker container (based on the great work of razorgirl). It's running on my Synology Docker. Latest master release.

Web setup went through without any hiccups. Directory /var/www/nZEDb/resources/nzb is accessible for everyone (chmod -R 777), and also properly set up in nZEDb as nzb folder.

I've activated 28 groups.

Getting binaries works well.

Whenever I run update_releases.php ("php update_release.php 1 true"), the following happens:

Code: [Select]

Starting release update process (2016-01-23 13:21:14)

Process Releases -> Attempting to find complete collections.
777 collections were found to be complete. Time: 1 second(s)

Process Releases -> Calculating collection sizes (in bytes).
777 collections set to filecheck = 3(size calculated)
0 second(s)

Process Releases -> Delete collections smaller/larger than minimum size/file count from group/site setting.
Deleted 2987 collections:
771 smaller than, 0 bigger than, 2216 with less files than site/group settings in: 9 second(s)

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

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

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


Process Releases -> Request ID local lookup -- limit 5000
No RequestID's to process.
0 releases updated in 0 second(s)

Process Releases -> Request ID web lookup -- limit 1000
No RequestID's to process.
0 releases updated in 0 second(s)

Process Releases -> Categorize releases.
0 second(s)

No music releases to process.
No console releases to process.
No games releases to process.
No xxx releases to process.
No book releases to process for category id 8010
Process Releases -> Delete finished collections.

Deleting collections/binaries/parts older than 72 hours.
Finished deleting 0 old collections/binaries/parts in 0 seconds.

Deleting collections that were missed after NZB creation.
Finished deleting 0 collections missed after NZB creation in 0 seconds.
Removed 0 parts/binaries/collection rows in 0 second(s)

Process Releases -> Delete releases smaller/larger than minimum size/file count from group/site setting.
Deleted 0 releases:
0 smaller than, 0 bigger than, 0 with less files than site/groups setting in: 0 second(s)

Process Releases -> Delete old releases and passworded releases.
Removed releases: 0 past retention, 0 passworded, 0 crossposted, 0 from disabled categories, 0 smaller than category settings, 0 from disabled music genres, 0 from misc->other0 from misc->hashed, 0 under 95% completion.
Completed adding 0 releases in 14.74 second(s). 2,862 collections waiting to be created (still incomplete or in queue for creation)

The folder /var/www/nZEDb/resources/nzb doesn't have a structure or any subdirectories in it after set-up and update_releases.php. Not sure if that's correct.

I'm also not sure if there's an issue with using docker...

Anyone has experienced the same? Where can I start looking for isses?

Thanks alot for your help.

Cheers, Chris

[gwmullin]

Hey Chris.

I actually found your docker script a few weeks ago and ran down your problem. Since mysql 5.5, STRICT has been the default mode of mysql. This doesn't play well with default null fields, which nzedb relies on when inserting collections into the release table.

Following docker instructions, set up an additional file in the mysql image under the directory /etc/mysql/conf.d/ with the following contents:
[mysqld]
sql-mode=""

Alternatively you can log into the mysql database directly and run 'SET GLOBAL sql_mode=""; ' - but this will be reset on the next startup, so better off to put it in your config.

I also did a bunch of modifying of the entry script, feel free to grab anything you like: https://github.com/gwmullin/docker_stuff/tree/master/nzedb

~Greg

[Wally73]

to make sure this is a docker issue NOT a nZEDb issue

[gwmullin]

nzedb could be modified to be more compatible with STRICT mode (EG expressly passing in all values instead of relying on defaults), however I don't think it's necessary really. Setting the sql_mode is good enough for my purposes.

[Wally73]

no docker has to be modified to work better with nZEDb since this is a modification