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

Unikraft redis doesn't start with kraft run, works correctly when started with Qemu #8

Open
andrejvelichkovski opened this issue Dec 5, 2022 · 0 comments

Comments

@andrejvelichkovski
Copy link

Hello, I noticed that when starting redis with the run option (instead of run_qemu) in the MUSL scripts it gives this error:

0:M 05 Dec 2022 19:40:42.023 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
0:M 05 Dec 2022 19:40:42.026 # Redis version=5.0.6, bits=64, commit=c5ee3442, modified=1, pid=0, just started
0:M 05 Dec 2022 19:40:42.031 # Configuration loaded
0:M 05 Dec 2022 19:40:42.097 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
0:M 05 Dec 2022 19:40:42.102 # Server can't set maximum open files to 10032 because of OS error: No such file or directory.
0:M 05 Dec 2022 19:40:42.107 # Current maximum open files is 1024. maxclients has been reduced to 992 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
0:M 05 Dec 2022 19:40:42.116 # Fatal: Can't initialize Background Jobs.

It works all good when started directly with Qemu, so I guess this is not a big issue, but I wanted to report it still in case it helps with something else.

I have used this script for setup/build/run/run_qemu: https://github.com/unikraft-upb/scripts/blob/main/musl/do-redis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant