Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: building any board occurre an internel hashtable error #7708

Closed
1 of 2 tasks
ZYQsteve opened this issue Jan 16, 2025 · 10 comments
Closed
1 of 2 tasks

[Bug]: building any board occurre an internel hashtable error #7708

ZYQsteve opened this issue Jan 16, 2025 · 10 comments
Labels
Bug Something isn't working as it should Not framework bug Bug in 3rd party component

Comments

@ZYQsteve
Copy link

What happened?

[Bug]: building any board occurre an internel hashtable error on step nemed copy files to [/boot (mount /boot)]
Copying files to [ /boot (MOUNT /boot) ] [🔨] Internal hashtable error: illegal key supplied! [🔨] rsync error: errors with program diagnostics (code 13) at hashtable.c(88) [generator=3.2.7] [💥] Error 13 occurred in main shell [ at /home/steve/test/lib/functions/logging/runners.sh:211 run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211 run_host_command_logged() --> lib/functions/logging/runners.sh:193 create_image_from_sdcard_rootfs() --> lib/functions/image/rootfs-to-image.sh:80 do_with_logging() --> lib/functions/logging/section-logging.sh:81 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:93 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] [🌿] Unmounting recursively [ SDCARD - be patient ] [🌿] Unmounting recursively [ MOUNT - be patient ] [🚸] Freeing loop [ trap_handler_cleanup_rootfs_and_image /dev/loop16 ]

How to reproduce?

run compile.sh to compile any board

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ZYQsteve ZYQsteve added the Bug Something isn't working as it should label Jan 16, 2025
Copy link
Contributor

github-actions bot commented Jan 16, 2025

Jira ticket: AR-2587

@igorpecovnik
Copy link
Member

run compile.sh to compile any board

Please provide exact commands to reproduce.

@dellagd
Copy link

dellagd commented Jan 16, 2025

Same issue.

Ran command: ./compile.sh build BOARD=rock-5c BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy

Possibly related: NixOS/nixpkgs#373845, RsyncProject/rsync#702

@ZYQsteve
Copy link
Author

./compile.sh build BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy HTTPS_PROXY="$https_proxy" HTTP_PROXY="$http_proxy"

@igorpecovnik igorpecovnik added the Not framework bug Bug in 3rd party component label Jan 16, 2025
@ZYQsteve
Copy link
Author

solved by upgrade rsync to v3.4.1

@ct991218620
Copy link

我也遇到了同样的问题,但是用同样的方式之前还可以编译成功的,是不是服务出现了什么问题。

@dellagd
Copy link

dellagd commented Jan 16, 2025

@ZYQsteve Where exactly did you upgrade rsync? My compile command is running with Docker as a backend so it's not my host rsync that I have to update I believe.

@dellagd
Copy link

dellagd commented Jan 16, 2025

For anyone else hitting this running through docker, I was able to patch around this by doing an install from source of rsync around this point, after rsync had been installed from APT:

${c} DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends ${BASIC_DEPS[@]} ${host_dependencies[@]}

To get this working without a patch, I think an updated package needs to be pushed to the Jammy ubuntu APT repository. No idea what the process for that looks like, or if the rsync maintainers will be doing that.

EDIT: Appears they will be rolling out a fix to Jammy! https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2095004

@ZYQsteve
Copy link
Author

我也遇到了同样的问题,但是用同样的方式之前还可以编译成功的,是不是服务出现了什么问题。

我没使用dockers编译,直接使用真机编译,更新是通过下载rsync源码编译更新的

@ZYQsteve
Copy link
Author

@ZYQsteve Where exactly did you upgrade rsync? My compile command is running with Docker as a backend so it's not my host rsync that I have to update I believe.

I upgrade the rsync by their official source code on GitHub, without using Docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working as it should Not framework bug Bug in 3rd party component
Development

No branches or pull requests

4 participants