[GH-ISSUE #32] Errors while processing data #32

Closed
opened 2026-02-27 15:54:34 +03:00 by kerem · 10 comments
Owner

Originally created by @andr6 on GitHub (May 11, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/32

Hi,

I am seeing allot of the following errors on the pipeline for all the files being used via SMB Crawler .

2017-05-11 14:59:05.470: [error] [p0] error submiting parsed text to Api, unexpected response code //windowsxptools/g/docs/file.html 500 {"message":"Invalid non-string/buffer chunk\n TypeError: Invalid non-string/buffer chunk\n at validChunk (_stream_writable.js:186:14)\n at GridWriteStream.Writable.write (_stream_writable.js:213:12)\n at ondata (_stream_readable.js:542:20)\n at emitOne (events.js:77:13)\n at emit (events.js:169:7)\n at Readable.read (_stream_readable.js:368:10)\n at flow (stream_readable.js:759:26)\n at resume (_stream_readable.js:739:3)\n at nextTickCallbackWith2Args (node.js:511:9)\n at process._tickCallback (node.js:425:17)"}

This is happening to all the files.

Any ideas ?

Thanks

Originally created by @andr6 on GitHub (May 11, 2017). Original GitHub issue: https://github.com/RD17/ambar/issues/32 Hi, I am seeing allot of the following errors on the pipeline for all the files being used via SMB Crawler . 2017-05-11 14:59:05.470: [error] [p0] error submiting parsed text to Api, unexpected response code //windowsxptools/g/docs/file.html 500 {"message":"Invalid non-string/buffer chunk\n TypeError: Invalid non-string/buffer chunk\n at validChunk (_stream_writable.js:186:14)\n at GridWriteStream.Writable.write (_stream_writable.js:213:12)\n at ondata (_stream_readable.js:542:20)\n at emitOne (events.js:77:13)\n at emit (events.js:169:7)\n at Readable.read (_stream_readable.js:368:10)\n at flow (_stream_readable.js:759:26)\n at resume_ (_stream_readable.js:739:3)\n at nextTickCallbackWith2Args (node.js:511:9)\n at process._tickCallback (node.js:425:17)"} This is happening to all the files. Any ideas ? Thanks
kerem 2026-02-27 15:54:34 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@isido993 commented on GitHub (May 11, 2017):

Hello!

The error is not critical and won't affect search performance and experience anyhow.
However it's a bug, and we'll fix it. Please send us the file (file.html - the one that generates the error) to help us investigate the issue.

Thanks

<!-- gh-comment-id:300818426 --> @isido993 commented on GitHub (May 11, 2017): Hello! The error is not critical and won't affect search performance and experience anyhow. However it's a bug, and we'll fix it. Please send us the file (`file.html` - the one that generates the error) to help us investigate the issue. Thanks
Author
Owner

@andr6 commented on GitHub (May 11, 2017):

Hi @fpd4444

Can't do that :) But this happening to all files now.

<!-- gh-comment-id:300821903 --> @andr6 commented on GitHub (May 11, 2017): Hi @fpd4444 Can't do that :) But this happening to all files now.
Author
Owner

@isido993 commented on GitHub (May 12, 2017):

@andr6

We made some updates, please run sudo ./ambar.py update and then try processing this files again.

<!-- gh-comment-id:301021680 --> @isido993 commented on GitHub (May 12, 2017): @andr6 We made some updates, please run `sudo ./ambar.py update` and then try processing this files again.
Author
Owner

@sochix commented on GitHub (May 19, 2017):

@andr6 did it help?

<!-- gh-comment-id:302694425 --> @sochix commented on GitHub (May 19, 2017): @andr6 did it help?
Author
Owner

@andr6 commented on GitHub (May 20, 2017):

It did. No more errors on html. I am seeing the same errors being applied to images file types(jpg,, png, etc)

I haven't upgrade yet to the latest version since my understanding is that it will need to start from 0.

<!-- gh-comment-id:302896974 --> @andr6 commented on GitHub (May 20, 2017): It did. No more errors on html. I am seeing the same errors being applied to images file types(jpg,, png, etc) I haven't upgrade yet to the latest version since my understanding is that it will need to start from 0.
Author
Owner

@isido993 commented on GitHub (May 22, 2017):

@andr6
We fixed the error you mentioned (processing images) in the latest version. Please update (you're right, it requires resetting Ambar index, but it worth it since the search is much more advance in this new version)

<!-- gh-comment-id:303047464 --> @isido993 commented on GitHub (May 22, 2017): @andr6 We fixed the error you mentioned (processing images) in the latest version. Please update (you're right, it requires resetting Ambar index, but it worth it since the search is much more advance in this new version)
Author
Owner

@andr6 commented on GitHub (May 22, 2017):

@fpd4444 If i upgrade does the data needs to be reprocessed again ?

<!-- gh-comment-id:303051047 --> @andr6 commented on GitHub (May 22, 2017): @fpd4444 If i upgrade does the data needs to be reprocessed again ?
Author
Owner

@sochix commented on GitHub (May 22, 2017):

@andr6 yep

<!-- gh-comment-id:303051182 --> @sochix commented on GitHub (May 22, 2017): @andr6 yep
Author
Owner

@sochix commented on GitHub (May 28, 2017):

@andr6 should I close this issue?

<!-- gh-comment-id:304493555 --> @sochix commented on GitHub (May 28, 2017): @andr6 should I close this issue?
Author
Owner

@andr6 commented on GitHub (Jun 1, 2017):

Please do

<!-- gh-comment-id:305509229 --> @andr6 commented on GitHub (Jun 1, 2017): Please do
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ambar#32
No description provided.