Recent Posts

Pages: [1] 2 3 ... 10
1
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
2
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
3
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
4
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.
5
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.
6
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).
7
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
8
Support / PHP fatal error: Imagick cache resources exhausted
« Last post by brewmarsh on 2019-06-04, 06:34:17 am »
I'm getting this error regularly now in postprocessing.

Code: [Select]
PHP Fatal error:  Uncaught ImagickException: cache resources exhausted `' @ error/cache.c/OpenPixelCache/3984 in /mnt/nzedb/nzedb/ReleaseImage.php:101
Stack trace:
#0 /mnt/nzedb/nzedb/ReleaseImage.php(101): Imagick->readimageblob('\xFF\xD8\xFF\xE0\x00\x10JFIF\x00\x01\x01\x01\x00...')
#1 /mnt/nzedb/nzedb/ReleaseImage.php(128): nzedb\ReleaseImage->fetchImage('/var/www/nZEDb/...')
#2 /mnt/nzedb/nzedb/processing/post/ProcessAdditional.php(1623): nzedb\ReleaseImage->saveImage('04135e9babbf1dd...', '/var/www/nZEDb/...', '/var/www/nZEDb/...', 650, 650)
#3 /mnt/nzedb/nzedb/processing/post/ProcessAdditional.php(1438): nzedb\processing\post\ProcessAdditional->_processJPGMessageIDs()
#4 /mnt/nzedb/nzedb/processing/post/ProcessAdditional.php(746): nzedb\processing\post\ProcessAdditional->_processMessageIDDownloads()
#5 /mnt/nzedb/nzedb/processing/post/ProcessAdditional.php(566): nzedb\processing\post\ProcessAdditional->_processReleases()
#6 /mnt/nzedb/misc/update/nix/multiprocessing/.do_not_run/switch.php(248): nzedb\processing\post\Proce in /mnt/nzedb/nzedb/ReleaseImage.php on line 101

Reading on some forums they suggested checking the output of this command:
Code: [Select]
identify -list resource
Resource limits:
  Width: 16KP
  Height: 16KP
  Area: 128MP
  Memory: 256MiB
  Map: 512MiB
  Disk: 1GiB
  File: 768
  Thread: 8
  Throttle: 0
  Time: unlimited

I'd appreciate any tips!
9
Support / Re: predb table re-create and re-patch
« Last post by Wally73 on 2019-04-06, 01:55:12 am »
Code: [Select]
DROP TABLE IF EXISTS predb;
CREATE TABLE predb (
  id         INT(11) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'Primary key',
  title      VARCHAR(255)     NOT NULL DEFAULT '',
  nfo        VARCHAR(255)     NULL,
  size       VARCHAR(50)      NULL,
  category   VARCHAR(255)     NULL,
  created    TIMESTAMP        NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'Unix time of when the
  pre was created, or first noted by the system',
  updated    TIMESTAMP        NOT NULL ON UPDATE CURRENT_TIMESTAMP COMMENT 'Unix time of when the
  entry was last updated',
  source     VARCHAR(50)      NOT NULL DEFAULT '',
  requestid  INT(10) UNSIGNED NOT NULL DEFAULT '0',
  groups_id  INT(10) UNSIGNED NOT NULL DEFAULT '0'  COMMENT 'FK to groups',
  nuked      TINYINT(1)       NOT NULL DEFAULT '0'  COMMENT 'Is this pre nuked? 0 no 2 yes 1 un nuked 3 mod nuked',
  nukereason VARCHAR(255)     NULL  COMMENT 'If this pre is nuked, what is the reason?',
  files      VARCHAR(50)      NULL  COMMENT 'How many files does this pre have ?',
  filename   VARCHAR(255)     NOT NULL DEFAULT '',
  searched   TINYINT(1)       NOT NULL DEFAULT '0',
  PRIMARY KEY (id),
  UNIQUE INDEX ix_predb_title     (title),
  INDEX ix_predb_nfo       (nfo),
  INDEX ix_predb_created   (created),
  INDEX ix_predb_source    (source),
  INDEX ix_predb_requestid (requestid, groups_id),
  INDEX ix_predb_filename  (filename),
  INDEX ix_predb_searched  (searched),
  FULLTEXT INDEX ix_predb_filename_ft (filename)
)
  ENGINE = MYISAM
  DEFAULT CHARSET = utf8
  COLLATE = utf8_unicode_ci
  AUTO_INCREMENT = 1;


DROP TABLE IF EXISTS predb_hashes;
CREATE TABLE predb_hashes (
  predb_id INT(11) UNSIGNED NOT NULL DEFAULT '0' COMMENT 'id, of the predb entry, this hash belongs to',
  hash VARBINARY(20)      NOT NULL DEFAULT '',
  PRIMARY KEY (hash)
)
  ENGINE = MYISAM
  DEFAULT CHARSET = utf8mb4
  COLLATE = utf8mb4_unicode_ci;


DROP TABLE IF EXISTS predb_imports;
CREATE TABLE predb_imports (
  title      VARCHAR(255)
               COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  nfo        VARCHAR(255)
               COLLATE utf8_unicode_ci          DEFAULT NULL,
  size       VARCHAR(50)
               COLLATE utf8_unicode_ci          DEFAULT NULL,
  category   VARCHAR(255)
               COLLATE utf8_unicode_ci          DEFAULT NULL,
  created    DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
  updated    DATETIME NOT NULL DEFAULT 0,
  source     VARCHAR(50)
               COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  requestid  INT(10) UNSIGNED        NOT NULL DEFAULT '0',
  groups_id   INT(10) UNSIGNED        NOT NULL DEFAULT '0' COMMENT 'FK to groups',
  nuked      TINYINT(1)              NOT NULL DEFAULT '0'  COMMENT 'Is this pre nuked? 0 no 2 yes 1 un nuked 3 mod nuked',
  nukereason VARCHAR(255)
               COLLATE utf8_unicode_ci          DEFAULT NULL
  COMMENT 'If this pre is nuked, what is the reason?',
  files      VARCHAR(50)
               COLLATE utf8_unicode_ci          DEFAULT NULL
  COMMENT 'How many files does this pre have ?',
  filename   VARCHAR(255)
               COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  searched   TINYINT(1)              NOT NULL DEFAULT '0',
  groupname  VARCHAR(255)
               COLLATE utf8_unicode_ci          DEFAULT NULL
)
  ENGINE =MYISAM
  DEFAULT CHARSET =utf8
  COLLATE =utf8_unicode_ci;
10
Support / predb table re-create and re-patch
« Last post by burn on 2019-03-24, 12:11:38 am »
I dropped my predb tables as it was crashed. (don't ask) and am hoping I can get instructions on how to re-create it properly before re-filling it.
php data/predb_import_daily_batch.php 0 local true is completely non-functional at present.
Pages: [1] 2 3 ... 10