NZBMatrix Down Again, Server/PHP(?) Maintenance

And all this 6th grade/jr. high nonsense means what, exactly? Nothing. Small minds chasing small... you get the gist.

Meanwhile, I ran into some fairly major problems on NZBMatrix today which hopefully they will fix (didn't have problems before the h/w changeover).

I use several indexers, but since the downfall of the original newzbin, I find myself using Matrix the most. Newzbin2 is at the bottom of the heap, and most places are simply overrun with really bad quality 'junk' that isn't worth the d/l effort.

Quote:

---

Originally Posted by k2bug

Latest News: NZBsRus reported to be back online tomorrow for those missing it. Well done NZBsRus

---

just waiting for the server backup to be restored and it will be back :D

what relevance "latest news" about nzbrus has to nzbmatrix topic i wonder... :lol:

the VIP section on NZBmatrix sucks nothingh there...

Dang, down again!

From the NZBMatrix service status page: SQL issues are being looked into...

The major problem I ran into several days ago (when the new server came up) had to do with the s/w inability to post an nzb's that referenced larger than around 50GB (or thereabouts).

It was supposed to be being 'worked on' for the last several days, but as of yesterday it still basically 'took a dump' when trying to upload 'large' nzb's (the actual size of the nzb being around 11+MB, but the file referenced were large BD50's with large amounts of par2's).

As of around 6 hours ago, no fix (and no response from the operators for a couple of days), maybe (!?!) that's what's being worked on now. Interestingly, on the old h/w, no problems like this existed, so I would gather some particular piece of the s/w was 'missed' during the new h/w, and in fact I did get a couple PHP folks that brought up that very point (it's been WAY to long since I messed around with PHP to hazard much of a real guess at this point).

Anyway, we shall see.

Quote:

---

Originally Posted by Beck38

The major problem I ran into several days ago (when the new server came up) had to do with the s/w inability to post an nzb's that referenced larger than around 50GB (or thereabouts).

---

With file sizes that big, it seems silly that people post article sizes that are measured in KB rather than MB, but for whatever reason that's still the way the system works.

Maybe when NNTP providers start allowing 10 or 20MB size articles --and uploaders of Blurays exploit that allowance-- these kind of NZB problems will automatically disappear.

up down... up down... up down for the last 24-48 hrs. Lots of 'SQL' errors. A lot of folks have come to the conclusion (when it was 'up') that not enough care was made in the transfer of the system from the old h/w to the new.

Probably so.