Bug 2240293
Summary: | Redis fails to start on aarch64 with 16kb pages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | pounce |
Component: | redis | Assignee: | Nathan Scott <nathans> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 38 | CC: | fabian.deutsch, fedora, fpercoco, mgoodwin, nathans |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | aarch64 | ||
OS: | Linux | ||
URL: | http://github.com/redis/redis/issues/12586 | ||
Whiteboard: | |||
Fixed In Version: | redis-7.2.1-2.fc39 redis-7.0.13-2.fc38 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-10-03 13:59:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
pounce
2023-09-22 22:33:02 UTC
Can you try a redis rebuild using this patch: diff --git a/redis.spec b/redis.spec index e4f6501..a054a0f 100644 --- a/redis.spec +++ b/redis.spec @@ -150,6 +150,15 @@ sed -i -e 's|^logfile .*$|logfile /var/log/redis/redis.log|g' redis.conf sed -i -e 's|^logfile .*$|logfile /var/log/redis/sentinel.log|g' sentinel.conf sed -i -e 's|^dir .*$|dir /var/lib/redis|g' redis.conf +# See https://bugzilla.redhat.com/2240293 +# See https://src.fedoraproject.org/rpms/jemalloc/blob/rawhide/f/jemalloc.spec#_34 +%ifarch %ix86 %arm x86_64 s390x x86_64 +sed -e 's/--with-lg-quantum/--with-lg-page=12 --with-lg-quantum/' -i deps/Makefile +%endif +%ifarch ppc64 ppc64le aarch64 +sed -e 's/--with-lg-quantum/--with-lg-page=16 --with-lg-quantum/' -i deps/Makefile +%endif + # Module API version safety check api=`sed -n -e 's/#define REDISMODULE_APIVER_[0-9][0-9]* //p' src/redismodule.h` if test "$api" != "%{redis_modules_abi}"; then You can download and try scratch build from F38 (redis-7.0.13-2) https://koji.fedoraproject.org/koji/taskinfo?taskID=106674259 F39 (redis-7.2.1-2) https://koji.fedoraproject.org/koji/taskinfo?taskID=106674152 (In reply to Remi Collet from comment #2) > You can download and try scratch build from > > F38 (redis-7.0.13-2) > https://koji.fedoraproject.org/koji/taskinfo?taskID=106674259 > F39 (redis-7.2.1-2) > https://koji.fedoraproject.org/koji/taskinfo?taskID=106674152 Downloaded and installed redis-7.0.13-2.fc38.aarch64 from the above builds. Was able to start the redis service (redis-server) and connect using redis-cli. Thanks! FEDORA-2023-cbc68067a5 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cbc68067a5 FEDORA-2023-bdb1515542 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-bdb1515542 FEDORA-2023-cbc68067a5 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-cbc68067a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cbc68067a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-bdb1515542 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-bdb1515542` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-bdb1515542 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-cbc68067a5 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-bdb1515542 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |