NNTmux / newznab-tmux

Laravel based usenet indexer
GNU General Public License v3.0
210 stars 52 forks source link

Some files not being processed #43

Closed bert0901 closed 9 years ago

bert0901 commented 9 years ago

The files are being found but no processing is being done, mainly file contents which has a knock on effect later down the line.

New Version of Tmux 229190-7[01/58] - "229190-2.0" yEnc (1/100) YES 228983-11[001/117] - "228983-3.0" yEnc (1/50) NO 147004-0[001/114] - "147004-2.0" yEnc (1/50) YES

Older Version of Tmux 229190-7[01/58] - "229190-2.0" yEnc (1/100) YES 228983-11[001/117] - "228983-3.0" yEnc (1/50) YES 147004-0[001/114] - "147004-2.0" yEnc (1/50) YES

Same with nZEDb so could be linked.

They are mainly series files that have the same initial numbers but different e.g -11 in above example.

Many Thanks

bert0901 commented 9 years ago

Looked into this more.

Having a lot of releases getting a value "passordstatus=-2".

When I search for the entries they show up, but in the normal browse they are not there.

What is this value?

Cheers

DariusIII commented 9 years ago

Values from -1 to -6 mean releases that are still processed by ProcessAdditional.

bert0901 commented 9 years ago

I thought that too, but not doing them when passwordstatus= -2

Seems just to miss those, not sure why. They don't get a retry for some reason.

Had a look at postprocessadditional.php in the tmux/lib folder and all seems to be okay.

DariusIII commented 9 years ago

Is this still an issue?

bert0901 commented 9 years ago

Yep, All I have been doing is running a SQL to reset passwordstatus to 0 if it has value of -2.

Its a weird one as it follows no pattern, sometimes it is due to no file contents, some files will go to -7 value.

Some of the files have with the -2 value have been processed fully but just have this value of -2 so not showing up on the website.

To be honest I gave up on this issue as was spending lots of time on it and getting nowhere.

I see you have made changes in DEV so will copy those over and see if still happening.

DariusIII commented 9 years ago

I will close this isse then. If the problem persists, reopen this issue.