Issue with Model Uploads with Revit Plugin - Server Error

Speckle Help Developers
,
1

Dear Support,

I’m encountering a server error when uploading about 100 models via the Revit plugin. Our server, version 2.16.0, is deployed with yarn dev. The PostgreSQL database is set up using the Docker configuration provided in the source code.

server logs:

[server] ERROR: Upload error. {"req":{"id":"bef2b7c0-f035-47ef-adf3-723733a5fb4b","method":"POST","path":"/objects/d7645a3083","headers":{"x-request-id":"bef2b7c0-f035-47ef-adf3-723733a5fb4b","content-type":"multipart/form-data; boundary=\"a9a7f9b9-09d9-4643-8132-88db1d8a829b\"","host":"10.5.56.19:3000","content-length":"38124","accept-encoding":"gzip"}},"authContext":{"auth":true,"userId":"f9786e8e7d","role":"server:admin","scopes":["streams:read","streams:write","profile:read","profile:email","users:read","users:invite"]},"userId":"f9786e8e7d","streamId":"d7645a3083"}
9|sp_server  | [server]     err: {
9|sp_server  | [server]       "type": "DatabaseError",
9|sp_server  | [server]       "message": "insert into \"object_children_closure\" (\"child\", \"minDepth\", \"parent\", \"streamId\") values ($1, $2, $3, $4), ($5, $6, $7, $8), ($9, $10, $11, $12), ($13, $14, $15, $16), ($17, $18, $19, $20), ($21, $22, $23, $24), ($25, $26, $27, $28), ($29, $30, $31, $32), ($33, $34, $35, $36), ($37, $38, $39, $40), ($41, $42, $43, $44), ($45, $46, $47, $48), ($49, $50, $51, $52), ($53, $54, $55, $56), ($57, $58, $59, $60), ($61, $62, $63, $64), ($65, $66, $67, $68), ($69, $70, $71, $72), ($73, $74, $75, $76), ($77, $78, $79, $80), ($81, $82, $83, $84), ($85, $86, $87, $88), ($89, $90, $91, $92), ($93, $94, $95, $96), ($97, $98, $99, $100), ($101, $102, $103, $104), ($105, $106, $107, $108), ($109, $110, $111, $112), ($113, $114, $115, $116), ($117, $118, $119, $120), ($121, $122, $123, $124), ($125, $126, $127, $128), ($129, $130, $131, $132), ($133, $134, $135, $136), ($137, $138, $139, $140), ($141, $142, $143, $144), ($145, $146, $147, $148), ($149, $150, $151, $152), ($153, $154, $155, $156), ($157, $158, $159, $160), ($161, $162, $163, $164), ($165, $166, $167, $168), ($169, $170, $171, $172), ($173, $174, $175, $176) on conflict do nothing - unexpected data beyond EOF in block 84700 of relation base/16384/188088",
9|sp_server  | [server]       "stack":
9|sp_server  | [server]           error: insert into "object_children_closure" ("child", "minDepth", "parent", "streamId") values ($1, $2, $3, $4), ($5, $6, $7, $8), ($9, $10, $11, $12), ($13, $14, $15, $16), ($17, $18, $19, $20), ($21, $22, $23, $24), ($25, $26, $27, $28), ($29, $30, $31, $32), ($33, $34, $35, $36), ($37, $38, $39, $40), ($41, $42, $43, $44), ($45, $46, $47, $48), ($49, $50, $51, $52), ($53, $54, $55, $56), ($57, $58, $59, $60), ($61, $62, $63, $64), ($65, $66, $67, $68), ($69, $70, $71, $72), ($73, $74, $75, $76), ($77, $78, $79, $80), ($81, $82, $83, $84), ($85, $86, $87, $88), ($89, $90, $91, $92), ($93, $94, $95, $96), ($97, $98, $99, $100), ($101, $102, $103, $104), ($105, $106, $107, $108), ($109, $110, $111, $112), ($113, $114, $115, $116), ($117, $118, $119, $120), ($121, $122, $123, $124), ($125, $126, $127, $128), ($129, $130, $131, $132), ($133, $134, $135, $136), ($137, $138, $139, $140), ($141, $142, $143, $144), ($145, $146, $147, $148), ($149, $150, $151, $152), ($153, $154, $155, $156), ($157, $158, $159, $160), ($161, $162, $163, $164), ($165, $166, $167, $168), ($169, $170, $171, $172), ($173, $174, $175, $176) on conflict do nothing - unexpected data beyond EOF in block 84700 of relation base/16384/188088
9|sp_server  | [server]               at Parser.parseErrorMessage (/home/release_2.17.3/node_modules/pg-protocol/dist/parser.js:287:98)
9|sp_server  | [server]               at Parser.handlePacket (/home/release_2.17.3/node_modules/pg-protocol/dist/parser.js:126:29)
9|sp_server  | [server]               at Parser.parse (/home/release_2.17.3/node_modules/pg-protocol/dist/parser.js:39:38)
9|sp_server  | [server]               at Socket.<anonymous> (/home/release_2.17.3/node_modules/pg-protocol/dist/index.js:11:42)
9|sp_server  | [server]               at Socket.emit (node:events:514:28)
9|sp_server  | [server]               at Socket.emit (node:domain:489:12)
9|sp_server  | [server]               at addChunk (node:internal/streams/readable:324:12)
9|sp_server  | [server]               at readableAddChunk (node:internal/streams/readable:297:9)
9|sp_server  | [server]               at Readable.push (node:internal/streams/readable:234:10)
9|sp_server  | [server]               at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
9|sp_server  | [server]       "length": 220,
9|sp_server  | [server]       "name": "error",
9|sp_server  | [server]       "severity": "ERROR",
9|sp_server  | [server]       "code": "XX000",
9|sp_server  | [server]       "hint": "This has been seen to occur with buggy kernels; consider updating your system.",
9|sp_server  | [server]       "file": "bufmgr.c",
9|sp_server  | [server]       "line": "1997",
9|sp_server  | [server]       "routine": "ExtendBufferedRelShared"
9|sp_server  | [server]     }

Thanks

1 Like
2

Hi @lihuifree

Thanks for reporting this issue; and welcome to the Speckle community. Please do feel free to introduce yourself over in our introductions thread.

This is not an error I have encountered before, so this may require further investigation to identify the root cause.

The hint within the error message This has been seen to occur with buggy kernels; consider updating your system., may suggest that this issue has been resolved in a later version of postgres - but I’m not sure if this refers to the postgres server or the postgres client.

Our docker compose files currently deploy postgres server version 14.5

Could you try updating the postgres server version to 14.10? An example of this proposed change can be found here.

We would recommend backing up your data and following our guide before proceeding with making any changes.

Iain

1 Like
3

Hi Iain,

Thanks for your advice. I’ll update the postgres and server kernel version, then test by uploading more model. Will let you know how it goes.

li

1 Like