apisix-dashboard: bug: apisix-dashboard v2.5 make build failed on Huawei Kunpeng system
Issue description
Environment
- apisix version (cmd:
apisix version
): v2.4 - OS (cmd:
uname -a
): Linux localhost.localdomain 4.19.90-17.ky10.aarch64 apache/apisix#1 SMP Sun Jun 28 14:27:40 CST 2020 aarch64 aarch64 aarch64 GNU/Linux - OpenResty / Nginx version (cmd:
nginx -V
oropenresty -V
): openresty/1.19.3.1 - etcd version, if have (cmd: run
curl http://127.0.0.1:9090/v1/server_info
to get the info from server-info API): v3.4.13 - apisix-dashboard version, if have: v2.5
- luarocks version, if the issue is about installation (cmd:
luarocks --version
): v3.6.0
Minimal test code / Steps to reproduce the issue
- apisix源码构建后正常启动./bin/apisix start
- 在apisix-dashboard内执行make build时报错了,如下图
What’s the actual result? (including assertion message & call stack if applicable)
What’s the expected result?
这个是因为鲲鹏系统的差异性导致最后构建失败的吗? 请求帮助,谢谢
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19 (12 by maintainers)
@imjoey Thank you for your help. After many times to download different versions of nodejs, I find the suitable version is v10.24.0.
At last,
make build
will work properly. Thank you all.I’ve already debugged with @Molio-tan personally, now I put the debug progress here with @Molio-tan’s permission.
Simply run
yarn install --verbose
under./web
directoryAt the same time, see the output from
/var/log/message
:Use
coredumpctl info 16027
to see detailed coredump infoActually, we could find a similar issue https://github.com/nodejs/help/issues/3202, which shows us that nodejs-v14&v15 is not compatible with Redhat8-aarch64 while nodejs-v12 is OK, and nodejs-v14&15 works well with ubuntu20.04-aarch64. From the snapshot in step 2, we could the reason for the crash is about nodejs itself.
Moreover, from the yum repository provided by Kylin, the default version of nodejs in kylin-v10 is
nodejs-10.11.0
, see the rpm package herehttp://archive.kylinos.cn/yum/v10/pks/aarch64/os/Packages/n/nodejs-10.11.0-1.ky10.aarch64.rpm
.In conclusion, IMHO, the root cause is about the incompatibility between nodejs version and Operating System.
So @Molio-tan will then downgrade the nodejs to 10.11.0 to recheck if the problem still exists and then post your result back here, Thank you very much.
Thank you anyway.I can’t wait for the solution.