Recent Posts

Pages: [1] 2 3 ... 10
1
General Talk / Re: Request - Upload obfuscated NZB via API
« Last post by Wally73 on Today at 02:51:46 am »
1. nzedb has nothing to do with torrents

2. it sounds like its promoting to post which is most likely illegal
2
General Talk / Re: Request - Upload obfuscated NZB via API
« Last post by brumsky on 2020-02-18, 07:42:29 am »
Any thoughts on this?

The idea is to try and limit or reduce the chance the torrent is taken down.
3
General Talk / Request - Upload obfuscated NZB via API
« Last post by brumsky on 2020-02-12, 04:00:58 pm »
I know of an indexer that allows you to upload a NZB that has been obfuscated.

This is from their config file for the uploader someone built to use that API.

# API url that is used to notify the indexer of an obfuscated release.
# The following two parameters will be replaced:
#   {0} by the obfuscated name of the file/folder
#   {1} by the original name of the file/folder
#   optionally ${ApiKey} will be replaced by the value entered above
ObfuscatedNotificationUrl=https://api.apiserver.com/api?hash={0}&name={1}&apikey=${ApiKey}

This way the NZB file has a GUID, while the indexer knows what it is.  Would it be possible to implement something like this??  That would be huge!
4
did you check the db on errors??

i'm guessing releases tables are crashed

ps if  you use mysql sock leave DB_HOST and DB_PORT empty
5
Support / Crash recovery, mysql cmd and phpmyadmin work fine, but nZEDb
« Last post by egandt on 2020-01-18, 04:59:24 am »
Crash recovery, mysql cmd and phpmyadmin work fine, but  nZEDb

Code: [Select]
[18-Jan-2020 07:54:00 America/New_York] PHP Fatal error:  Uncaught PDOException: SQLSTATE[HY000] [2002] Connection refused in /websites/nZEDb17a/nzedb/db/DB.php:1343
Stack trace:
#0 /websites/nZEDb17a/nzedb/db/DB.php(1343): PDO->__construct('mysql:host=0;po...', 'DBNAME', 'PASSWORD', Array)
#1 /websites/nZEDb17a/nzedb/db/DB.php(212): nzedb\db\DB->connect(Array)
#2 /websites/nZEDb17a/nzedb/SphinxSearch.php(31): nzedb\db\DB->__construct(Array)
#3 /websites/nZEDb17a/nzedb/Releases.php(66): nzedb\SphinxSearch->__construct()
#4 /websites/nZEDb17a/www/pages/browse.php(10): nzedb\Releases->__construct(Array)
#5 /websites/nZEDb17a/www/index.php(89): require_once('/websites/nZEDb...')
#6 {main}
  thrown in /websites/nZEDb17a/nzedb/db/DB.php on line 1343

So if I can manualy connect using this login/password and myphpadmin works, why is nZEDb unable to connect?  I tried with and without the socket connection enabled same errrors.

Code: [Select]
//=========================
// Config you must change - updated by installer.
//=========================
define('DB_SYSTEM', 'mysql');
define('DB_HOST', '127.0.0.1');
define('DB_PORT', '3306');
define('DB_SOCKET', '/var/run/mysqld/mysqld.sock');
define('DB_USER', 'DBUSER');
define('DB_PASSWORD', 'PASSWWORD');
define('DB_NAME', 'DBNAME');
define('DB_PCONNECT', false);

the exact same information works via mysql -u DBUSER -p DBNAME
which also uses the socket so why is nZEDb throwing connections issues and how to debug this?  as I see no independent way to verify the connection beyond what I'm doing.

Example of mysql working:
Code: [Select]
root@vmware_nzdb:/# mysql -u DBUSER -p DBNAME
Enter password: <PASSWORD>
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 2730
Server version: 10.0.38-MariaDB-0ubuntu0.16.04.1 Ubuntu 16.04

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [nzedb17a]> show tables;
+--------------------------+
| Tables_in_nzedb17a       |
+--------------------------+
| allgroups                |
| anidb_episodes           |
| anidb_info               |
| anidb_titles             |
| audio_data               |
| binaries                 |
| binaries_1               |
| binaries_1000001         |
| binaries_1000002         |
| binaries_1000003         |
| binaries_1000004         |
| binaries_1000021         |
| binaries_1000025         |
....

ERIC
6
Support / Re: PHP fatal error: Imagick cache resources exhausted
« Last post by Bart39 on 2019-11-22, 03:46:21 pm »
i started seeing this too but followed the suggestion in this bug report (increasing the cache)

https://github.com/ImageMagick/ImageMagick/issues/396
7
Support / Re: PHP fatal error: Imagick cache resources exhausted
« Last post by brewmarsh on 2019-10-17, 08:45:34 am »
FYI I ended up rebuilding the server and have not found this problem again.
8
Announcements / 0.8.20.0 2019-10-07
« Last post by Wally73 on 2019-10-07, 11:03:39 pm »
0.8.20.0 2019-10-07
Changed:
   * Updated Lithium Framework to v1.2 and other dependencies.

Fixed:
   * Issue 2637. Problem with cover image links having leading zeroes in the name.
   * Install should now correctly create PROCEDUREs in database setup.
9
Announcements / 0.8.19.0 2019-09-06
« Last post by Wally73 on 2019-09-05, 09:58:19 pm »
0.8.19.0 2019-09-06
Fixed:
   * PHP 7.3 compatibility changes.

0.8.18.3 2019-07-19
Fixed:
   * Issue 2633. SQL Error when updating binaries. Hopefully reduces overhead formatting
    'Message-Id'.


0.8.18.2 2019-07-18
Fixed:
   * Issue 2632. Debug: Postdate retried when updating binaries or backfilling.
     *NOTE* This is the same problem as the reported Missing "Subject", "Date", etc indexes for
     users of certain USPs.


0.8.18.1 2019-07-18
Changed:
   * 'Optimisations' for NNTP::getXOVER().

Fixed:
   * Remove include_once that was made superfluous.


0.8.18.0 2019-07-18
Added:
   * Add newznab:apilimit to API and RSS XML response with limits and current api hits and grabs.

Fixed:
   * Increase size of imdbid fields in movieinfo, releases, and user_movies tables to bring us
     inline with IMDb's latest entries.
   * Update movie-add.php for larger IMDb IDs (PR 2631).
   * Broken include_once in DB.php


0.8.17.1 2019-06-03
Fixed:
   * Typo in variable name.


0.8.17.0 2019-06-03
Changed:
   * Improvements to how TSV files are handled to make LOAD INFILE less problematic.

Fixed:
   * Update some regexes that were using invalid syntax. This will prevent them from being flagged
     as the errors they are with PCRE2 in PHP 7.3+.
   * Reduce the size of tmux table's 'value' column from 19000 to a more reasonable size (1000).
10
Support / Re: PHP fatal error: Imagick cache resources exhausted
« Last post by Wally73 on 2019-06-10, 04:35:07 am »
Never seen those kind of errors

better report an issue on https://github.com/nZEDb/nZEDb/issues
Pages: [1] 2 3 ... 10