-
Notifications
You must be signed in to change notification settings - Fork 17
[6.0.0a] lucence jobs store path instead of fileid #5
Comments
Comment by karlitschek from Wednesday Dec 18, 2013 at 08:34 GMT @butonic Can you have a look please? |
Comment by butonic from Wednesday Dec 18, 2013 at 13:12 GMT I am trying to store the path to new files as a parameter for the backroundjob. When it cannot be inserted it will be indexed the next time you click in the search field. I'll prepare a PR that uses storage & fileids instead of the path to get rid of the problem. In the meanwhile please ignore the error {"app":"hook","message":"error while running hook (OCA\\Search_Lucene\\Hooks::indexFile): An exception occurred while executing 'INSERT INTO \"oc_jobs\"(\"class\", \"argument\", \"last_run\") VALUES(?, ?, 0)':\n\nSQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(256)","level":3,"time":"December 18, 2013 08:19:48"} The other lines are not related to this issue. @DeepDiver1975 might have an idea about the severity of |
Comment by marcello-lodi from Tuesday Jan 07, 2014 at 11:29 GMT I have the same problem. {"app":"hook","message":"error while running hook (OCA\Search_Lucene\Hooks::indexFile): An exception occurred while executing 'INSERT INTO "oc_jobs"("class", "argument", "last_run") VALUES(?, ?, 0)':\n\nSQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(255)","level":3,"time":"2014-01-06T12:47:09+00:00"} ownCloud version: 6.0.0a |
Comment by disconn3ct from Friday Jan 10, 2014 at 21:07 GMT I believe this is the same (or at least related). New Arch linux vhost, clean install. Getting these errors in the log while using the sync client to migrate data in: |
Comment by butonic from Friday Jan 17, 2014 at 17:39 GMT changed name to better reflect the issue |
Comment by usterk from Tuesday Jan 21, 2014 at 13:35 GMT I have the same errors: {"app":"hook","message":"error while running hook (OCA\\Search_Lucene\\Hooks::indexFile): An exception occurred while executing 'INSERT INTO \"oc_jobs\"(\"class\", \"argument\", \"last_run\") VALUES(?, ?, 0)':\n\nSQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(256)","level":3,"time":"2014-01-21T13:24:53+00:00"}
{"app":"hook","message":"error while running hook (OCA\\Search_Lucene\\Hooks::deleteFile): An exception occurred while executing 'INSERT INTO \"oc_jobs\"(\"class\", \"argument\", \"last_run\") VALUES(?, ?, 0)':\n\nSQLSTATE[22001]: String data, right truncated: 7 ERROR: value too long for type character varying(256)","level":3,"time":"2014-01-21T13:24:53+00:00"} Debian 7 |
@jcfischer @marcello-lodi @disconn3ct @usterk Beware, this is bleeding edge code! Could you try replacing the contents of your search_lucene folder with this zip: https://github.com/owncloud/search_lucene/archive/search_lucene_refactoring.zip and report any issues in #1 Let me know if that solves the Class not found error and still works as expected. |
Is there an update on a fix for this issue and a process to reset the lucene indexes? We are currently encountering this issue when we have deep paths for some of our files. The files are synced to the server, but they fail to index with the error specified in this issue. This causes them to be unavailable in the web client and also causes a subsequent delete of the file on our computers the next time a sync operation occurs in the sync client. |
From what I understand, the column "argument" is too short in the oc_jobs table, if this is the only issue, why not just extend it? Something like 1024 char from 256 should work: ALTER TABLE oc_jobs ALTER COLUMN argument TYPE character varying(1024); |
@AceSlash the correct fix has been implemented in the https://github.com/owncloud/search_lucene/tree/search_lucene_refactoring branch. Unfortunately, my time gets soaked up in other projects. I'll try to polish it on friday. |
Hello, Info on my setup: |
@roelWuyts The alter from my earlier comment worked for me on a production environment (owncloud 6.0.4), so you should not have any issue if you do the same thing. |
Thanks, will do |
@butonic I upgraded owncloud from version 7.0.2 to 7.0.3 and this error came up in my owncloud.log. I never had this error before. |
@cippaciong please try with the master branch of search_lucene: https://github.com/owncloud/search_lucene/archive/master.zip |
@butonic I'm having a hard time trying to reproduce it before I try the master branch. Any hint? |
@cippaciong It will only appear if you create a new file with a very long path (>256 chars). The old search lucene will try to add an indexing job and fail with this error. The master version of search_lucene no longer does that. |
In the meantime, extending the column "argument" like I described in my previous post will fix this issue. |
@butonic I was able to reproduce the error creating a long path and I can confirm that it doesn't show up anymore using the master branch. This time I had another error but I don't know if it's related to search_lucene, it looks more like a file permission error (I checked and the contents of that directory is owned by www-data while the php5 directory itself is owned by root): @AceSlash thanks, I will try that later as a workaround |
@butonic Never mind, that error was caused by a wrong line in my |
Issue by jcfischer from Wednesday Dec 18, 2013 at 07:34 GMT
Originally opened as owncloud/core#6479
Expected behaviour
Syncing a directory without any errors
Actual behaviour
SQL Errors when inserting into oc_jobs
Steps to reproduce
Server configuration
Operating system: Ubuntu 13.04
Web server: Apache 2.4
Database: Postgres 9.2
PHP version: 5.5
ownCloud version: 6.0.0a
Updated from an older ownCloud or fresh install: fresh install
List of activated app: LDAP,
The content of config/config.php: (Without the database password and passwordsalt)
Client configuration
Browser: OS X Sync Client 1.4.2
Operating system: OS X 10.8.5
Logs
ownCloud log (data/owncloud.log)
The text was updated successfully, but these errors were encountered: