Closed tacruc closed 5 years ago
This is huge file ! event for a TIFF.
Do you have other issue with file as big as this one ? what is your setup (are you using the files_fts_tesseract app ?)
So here is the server detail, so I'm using files_fts_tesseract. Coulnd't test until now if it fails for an other tiff this size.
Operating system: Linux 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64
Webserver: Apache/2.4.27 (Debian) (apache2handler)
Database: mysql 10.1.26
PHP version:
7.0.30-0+deb9u1 Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, session, standard, apache2handler, mysqlnd, PDO, xml, apcu, apc, bz2, calendar, ctype, curl, dom, enchant, mbstring, fileinfo, ftp, gd, gettext, gmp, gnupg, iconv, igbinary, imagick, imap, interbase, intl, json, ldap, exif, mcrypt, mongodb, mysqli, odbc, pdo_dblib, PDO_Firebird, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, readline, recode, redis, shmop, SimpleXML, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xmlreader, xmlrpc, xmlwriter, xsl, zip, Zend OPcache
Nextcloud version: 14.0.0 - 14.0.0.19
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: unknown
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Operating system:
+1 here. Although the file, which causes this issue is "only" approx 100MB in size, it's contents seem to give tesseract issues. In my case its a - admittedly - huge texture file of a wooden surface. I tried to run this file through tesseract on the terminal and it took tesseract a whopping 19 mins. to produce a 3k file of… well probably blanks.
This initially caused the DB connection to get closed and bubbled up a DBA exception, but when I adjusted the max_timeout for mysql from 600 to 1800, indexing stopped by "force quit".
Also, I have limited the file size for indexing to 64mb, so this file shouldn't have been considered for indexing anyway, but that's only a side-note.
My NC is at 13.0.6 and FTS is current.
I restarted the index and I had set the max filesize to 20MB, but now FTS has tesseract indexing the same file again:
[root@nextcloud Tex]# ps -ef | grep tesseract nginx 23733 21692 0 22:00 pts/2 00:00:00 sh -c "tesseract" "/mnt/nextcloud/data/valentina.kohl/files/BRUNNER_NEUHEITEN/vonCRAFT/VALET/Tex/wood-075_teak-2_d_eiche-hell_XL.png" stdout -psm 3 -l deu+eng 2> /dev/null nginx 23734 23733 99 22:00 pts/2 00:11:39 tesseract /mnt/nextcloud/data/valentina.kohl/files/BRUNNER_NEUHEITEN/vonCRAFT/VALET/Tex/wood-075_teak-2_d_eiche-hell_XL.png stdout -psm 3 -l deu+eng
@budachst thanks for opening a new issue, however, I cannot reproduce your issue
@tacruc I would say that ORCing a 600Mb file is not a good idea to start with, I think even a huge (100+ MB) pdf file would result with Tika crashing. This is the main reason I implemented a limit on the file size.
I am trying right now to work with your 600Mb file but more to see if I can ignore the issue and go on with the index
@daita I agree that ORCing a 600Mb file is not reasonable. So one last stupid question, where can I configure the limit on the file size? I coulnd't find the option.
Sorry never mind just found it, but it is set to 50mb. So why does the file even get indexed? Cloud it be related to #387 ?
I think you'd set that in the preferences -> fulltextsearch -> maximum file size, which is set to 20 in my case.
the Update to version 1.0.0 fixed the problem.
Hi I got this Force Quit Message
Allways on this large prefix.tif file. The password is the file name. I clound't finde any futher related error messages in the logs.