跳到主要内容
ArcBlock Community

Pages Loading Error

Wasil
支持
pages-kitbugqualifiedresolvedrewarded

Yooo! Recently, I noticed one of my apps is not loading properly, while the other works normally. Each of the blocklets are updated, so not sure what the issue might be?🤔 I thought it was maybe my connection, cause it‘s garbage right now🤣 but my Trinity app loads fine still, so thinking it might be a bug? Lastly, I also tried to restart the entire app, but still nothing, which is why I figured to make this post. I then was able to individually access each blocklet, but not the pages kit or media kit, which makes me think the issue stems from one or the other. The app with the issue is - https://oblivion.did.life

zNKd7wLVSytMnAjm5DrAypmrd5nwyAmzo6GN.20250104213306.log.zip

Pages Kit "stderr" logs as shown in the video above.

Thanks for your help and time in advance!

20 条回复

Yongzhuo Liang20个月前(edited)

想了解一下， https://oblivion.did.life 是你们自托管的机器吗？

我们通过查看日志发现，似乎出现了 js 堆内存溢出的问题，如果是自托管的机器，你们可以尝试下面的解决方法

javascriptCopy
echo "export NODE_OPTIONS='--max-old-space-size=4096'" >> ~/.bashrc
source ~/.bashrc

还需要重启 blocklet server & blocklet

日志如下：

javascriptCopy
2025-01-05T01:20:20: BadRequestError: request aborted
2025-01-05T01:20:20:     at IncomingMessage.onAborted (/var/lib/blocklet/blocklets/node_modules/raw-body/index.js:245:1)
2025-01-05T01:20:20:     at IncomingMessage.emit (node:events:518:28)
2025-01-05T01:20:20:     at IncomingMessage._destroy (node:_http_incoming:221:10)
2025-01-05T01:20:20:     at _destroy (node:internal/streams/destroy:122:10)
2025-01-05T01:20:20:     at IncomingMessage.destroy (node:internal/streams/destroy:84:5)
2025-01-05T01:20:20:     at abortIncoming (node:_http_server:805:9)
2025-01-05T01:20:20:     at socketOnClose (node:_http_server:799:3)
2025-01-05T01:20:20:     at Socket.emit (node:events:530:35)
2025-01-05T01:20:20:     at TCP.<anonymous> (node:net:343:12)
2025-01-05T01:21:53: 
2025-01-05T01:21:53: <--- Last few GCs --->
2025-01-05T01:21:53: 
2025-01-05T01:21:53: [69:0x7ddc000]  8431968 ms: Mark-Compact (reduce) 1022.5 (1046.4) -> 1022.5 (1039.4) MB, pooled: 0 MB, 1903.49 / 0.00 ms  (+ 6.4 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 1950 ms) (average mu = 0.243, curre[69:0x7ddc000]  8433038 ms: Mark-Compact 1023.4 (1039.4) -> 1023.4 (1043.4) MB, pooled: 0 MB, 1068.80 / 0.00 ms  (average mu = 0.155, current mu = 0.000) allocation failure; scavenge might not succeed
2025-01-05T01:21:53: 
2025-01-05T01:21:53: 
2025-01-05T01:21:53: <--- JS stacktrace --->
2025-01-05T01:21:53: 
2025-01-05T01:21:53: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
2025-01-05T01:21:53: ----- Native stack trace -----
2025-01-05T01:21:53: 
2025-01-05T01:21:53:  1: 0xe19de0 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
2025-01-05T01:21:53:  2: 0x1240390 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
2025-01-05T01:21:53:  3: 0x1240667 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
2025-01-05T01:21:53:  4: 0x146e1a5  [node]
2025-01-05T01:21:53:  5: 0x146e1d3  [node]
2025-01-05T01:21:53:  6: 0x148728a  [node]
2025-01-05T01:21:53:  7: 0x148a458  [node]
2025-01-05T01:21:53:  8: 0x1cc5791  [node]
2025-01-05T01:26:53: Aborted (core dumped)
2025-01-05T01:27:00: Sun, 05 Jan 2025 01:27:00 GMT express-session deprecated undefined resave option; provide resave option at blocklet-compact.js:11:21
2025-01-05T01:27:00: Sun, 05 Jan 2025 01:27:00 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at blocklet-compact.js:11:21
2025-01-05T01:27:00: Warning: connect.session() MemoryStore is not
2025-01-05T01:27:00: designed for a production environment, as it will leak
2025-01-05T01:27:00: memory, and will not scale past a single process.
2025-01-05T01:27:00: (node:68) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
2025-01-05T01:27:00: (Use `node --trace-deprecation ...` to show where the warning was created)
2025-01-05T01:27:00: (node:68) DeprecationWarning: user middleware is deprecated, please use session middleware for better security
2025-01-05T01:27:00: (node:68) [DEP0044] DeprecationWarning: The `util.isArray` API is deprecated. Please use `Array.isArray()` instead.
2025-01-05T02:24:22: BadRequestError: request aborted
2025-01-05T02:24:22:     at IncomingMessage.onAborted (/var/lib/blocklet/blocklets/node_modules/raw-body/index.js:245:1)
2025-01-05T02:24:22:     at IncomingMessage.emit (node:events:518:28)
2025-01-05T02:24:22:     at IncomingMessage._destroy (node:_http_incoming:221:10)
2025-01-05T02:24:22:     at _destroy (node:internal/streams/destroy:122:10)
2025-01-05T02:24:22:     at IncomingMessage.destroy (node:internal/streams/destroy:84:5)
2025-01-05T02:24:22:     at abortIncoming (node:_http_server:805:9)
2025-01-05T02:24:22:     at socketOnClose (node:_http_server:799:3)
2025-01-05T02:24:22:     at Socket.emit (node:events:530:35)
2025-01-05T02:24:22:     at TCP.<anonymous> (node:net:343:12)
2025-01-05T02:26:01: 
2025-01-05T02:26:01: <--- Last few GCs --->
2025-01-05T02:26:01:
Yongzhuo Liang20个月前

好的，那我们排查一下服务器情况

Wasil20个月前

Okay bet! I don’t know how to exactly, so if you could guide me on how to do so. Here is a screen shot of my blocklet dashboard, and the DID of server!

did:abt

IMG_2496.png

If you need me to get any other information or logs, just let me know!

Yongzhuo Liang20个月前

我想了解下最近在 Pages Kit 有更新过自定义组件的代码吗？

还有我发现好像现在 Media Kit 能正常访问了？

Wasil20个月前

The pages kit blocklet is updated, and I have not updated any custom components in the Pages kit.

Wasil20个月前

yes the media blocklet is working now! and I was able to access the blocklet

Wasil20个月前

it’s now just the pages kit giving me an issue

Yongzhuo Liang20个月前

能帮我尝试一下以下操作？

先把 Pages Kit 单独停止了，等个几分钟，再把 Pages Kit 启动

Wasil20个月前

you got it!🫡

Yongzhuo Liang20个月前

目前我看 Pages Kit 是停止的状态，请问是手动停止了没有启动吗？还是另外遇到了什么报错

Wasil20个月前

I manually stopped it, and then tried to manually start it, but it gave me a few issues, and then it finally started. But it still does not allow me to access the blocklet.

IMG_2506.jpeg

👀1
Yongzhuo Liang20个月前

好的，我还需要最新的日志，这个问题看着太奇怪了

👀1
Wasil20个月前

Pages Kit Logs stderr

Let me know if you need other Logs!

Yongzhuo Liang20个月前

如果上面的步骤依然无法恢复，请通知我 😭

👀1
Wasil20个月前(edited)

I went through the process as indicated, but still no luck! The pages kit still won’t load properly💀😅

Yongzhuo Liang20个月前

在你刚刚做完这些操作，我们尝试访问你的站点，发现能正常访问，但是过了一会就无法访问了

目前我们无法复现这种情况，但是我们会尝试做一下修复

👀1
Yongzhuo Liang20个月前

我们在刚刚发布了 Pages Kit 0.3.19 版本，尝试修复这个问题

你可以更新一下，看看是否能恢复正常

Yongzhuo Liang20个月前

我们在昨天发布了 Pages Kit 0.3.19 版本，尝试修复这个问题

你可以更新一下，看看是否能恢复正常

👍1
Yongzhuo Liang20个月前

z1e2eafaHZxSiDgpNQEFqcuVSZd9tYT21C6 不好意思，让你久等了

通过最新的日志排查，发现应该是跟 PassBlock 这个 Blocklet 有关，里面存放了比较多的资源文件 当 Pages Kit 启动的时候，会把这些文件上传到 Media Kit 中，但是在上传的时候，似乎遇到一些错误，Pages Kit 没有正常处理，导致问题的发生

目前我们正在同步处理这个问题，你可以通过以下步骤，查看网站是否能恢复

  1. 停止 PassBlock Blocklet
  2. 重启 Pages Kit Blocklet
👍1✅1
Wasil20个月前

Now that I'm going through and deleting all the images, I think this would be a good time to also suggest the option to quickly select many uploads in the Media Kit, and delete them all lol

回复