(38)Function not implemented: AH00141: Could not initialize random number generator
WarSonic69 opened this issue Β· 33 comments
How to use GitHub
- Please use the π reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
Hi everyone,
I searched and found this issue with the exact same issue but no real answer : nextcloud/server#28666 As the webserver is handled in the docker container as far as I know, the issue is with the container.
- 22.1.0.1 docker version of Nextcloud server perfectly working
- Automatic update to 22.1.1.2 this morning via Watchtower
- Server not started and this issue looping in the container logs :
[Tue Aug 31 20:16:38.273961 2021] [:crit] [pid 1] (38)Function not implemented: AH00141: Could not initialize random number generator
Server configuration
Operating system: Synology DS415+ with DSM 6.2.4
Web server: Handled in the docker image (Apache I guess given the error)
Database: MariaDB
Where did you install Nextcloud from: This repository
Are you using external storage, if yes which one: No
Are you using encryption: No
Are you using an external user-backend, if yes which one: No
Nothing interesting in the Nextcloud logs apart from :
{"reqId":"Z2wxZZKE4MZXbp9uotkC","level":1,"time":"2021-08-31T02:03:35+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\OC\Updater::startCheckCodeIntegrity: Starting code integrity check...","userAgent":"--","version":"22.1.0.1"}
{"reqId":"Z2wxZZKE4MZXbp9uotkC","level":1,"time":"2021-08-31T02:04:04+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\OC\Updater::finishedCheckCodeIntegrity: Finished code integrity check","userAgent":"--","version":"22.1.0.1"}
{"reqId":"Z2wxZZKE4MZXbp9uotkC","level":1,"time":"2021-08-31T02:04:04+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\OC\Updater::updateEnd: Update successful","userAgent":"--","version":"22.1.1.2"}
{"reqId":"Z2wxZZKE4MZXbp9uotkC","level":1,"time":"2021-08-31T02:04:04+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\OC\Updater::maintenanceDisabled: Turned off maintenance mode","userAgent":"--","version":"22.1.1.2"}
{"reqId":"Z2wxZZKE4MZXbp9uotkC","level":1,"time":"2021-08-31T02:04:04+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\OC\Updater::resetLogLevel: Reset log level to Warning(2)","userAgent":"--","version":"22.1.1.2"}
Thanks in advance for your help !
Additional context:
docker-library/wordpress#630
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978045
Your NAS is using a linux kernel < 3.16 and is missing some dependencies required by apache2 now.
Hi @kesselb
Thanks for your quick answer. I looked a little bit around and did not find any easy way to update the Synology kernel. Is it possible to install only the dependencies missing ? If yes, is there a list ? If not, is it possible to downgrade the version of my Nextcloud installation ?
Thanks in advance !
same problem :( - any dummy advice to install the missing dependencies?
Thanks in advance !
I had a similar problem. The only difference was that my docker image ran in a virtual machine (VirtualBox) with Debian Jessie as a guest system. I had to update to Debian Stretch (all my attempts to update the Linux kernel for Jessey ended in vain), after which the error disappeared. It seems to me that the problem arose after the docker image was based on php: 7.4-apache-bullseye (and then php: 8.0-apache-bullseye) instead of php: 7.4-apache-buster. For NAS, things will be much worse, since updating the Linux version will not be easy at all.
Yes, I tried looking for different ways to update the kernel on my NAS but it seems far too risky. My only hope would be the last version of the OS (DSM7.0) but I am not sure of the kernel version on it (found several answers all contradictory) and I don't want to rush the update for that...
My NAS is on DSM7.0 --> same Error!
Thanks for the information ! (Even if it's not what I wanted to hear) Sooo, no possibility for us apparently ?
Same issue on DSM7.0
same issue but on DSM 6.2.4
I can reproduce this issue on a Synology RS3617xs with DSM 6.2.4-25556. On a DS1618+ with DSM 7.0-41890 it is working fine.
My workaround was to edit the Dockerfile to use php:8.0-apache-buster as base image instead of php:8.0-apache-bullseye and build it on my own. Otherwise a switch to the fpm image could a be a workaround for this issue.
BTW, same issue for the bitnami apache image:
https://github.com/bitnami/bitnami-docker-apache/issues/106
Hi @mosesdd
Thanks you for the hint about the fact to build your own image. I just tried and can confirm it went back up immediately.
For reference for those that do not know exactly how to build your own image, I did the following (all in SSH) :
Git clone in a specific directory on the NAS
Change the docker/22/apache/Dockerfile to use the buster image
Go to the docker/22/apache folder
Docker build with this command : "sudo docker build -t nextcloudtest . -f Dockerfile" (the -t part is to have a understandable name, the . -f part is to avoid an issue with the COPY part)
Then change the base image of my container from nextcloud:latest to nextcloudtest:latest
So far, everything seems to work fine again but I am no longer using the official Nextcloud image for now, I will be forced to build it manually everytime.
Best regards
anyone know if there are any pre built images to download with php:8.0-apache-buster as base image by default?
That would be nice to have also for future updates.
Hi, anyone an idea how an already updated DB/data can be rolled back from 21.1.1.2 to 21.1.0.1 ?
I still have a working DS412+ with DSM 6.2.4. Any higher DSM like 7 will never be released for this. Only security updates will be done. I gues these will not contain a new kernel.
Same issue with Docker running on a Synology DS1515+ with DSM 6.2.4.
Since Nextcloud downgrades are not supported and building my own image seems quite the effort please release an image with php:8.0-apache-buster as base image.
@WarSonic69
Can you elaborate on how to build a custom docker image?
Git clone in a specific directory on the NAS
Which git repository are you cloning?
Change the docker/22/apache/Dockerfile to use the buster image
What exactly do you change.
etc.
Greatly appreciated.
I Gitcloned the Nextcloud/docker repo : https://github.com/nextcloud/docker.git
I changed this line in the Dockerfile :
FROM php:8.0-apache-bullseye
and I put :
FROM php:8.0-apache-buster
Hope this is enough information, don't hesitate if you need more.
@WarSonic69 Thanks! I could make a new docker image and got nextcloud up and running.
You're welcome ! This is not ideal but well... It works.
Hey @WarSonic69 another two questions from my side:
You mention a "specific" folder where you cloned the repository. Which one is it? I'm trying to find this information, but I'm not sure where to clone this.
Another thing: I tried to build the build the docker container inside the directory like "volume1/docker/docker/22/apache", but wasn't successful, is that also a sign that I need to have a specific folder? Err. Msg. looks like that:
/volume1/docker/docker/22/apache$ sudo docker build -t nextcloudtest
"docker build" requires exactly 1 argument.
See 'docker build --help'.
Usage: docker build [OPTIONS] PATH | URL | -
Build an image from a Dockerfile
The specific folder I am mentioning is the folder in which you want to store the Git data. Personally, it is something like "volume1/docker/NextcloudGitClone" just to remember it. It does not have a huge importance as you can delete it once the image is built.
Regarding your error, I remember having it when I tried building the image at the beginning. I can only advice you to use the exact same build command as I did (even the dot is important). I don't remember the exact cause but it is linked to the command.
Since the root issue is stille there, any chance of a permanent fix? like a prebuilt dockerfile with the correct base image?
Just wanted to mention that changing the Dockerfile directly is a valid, yet not an ideal solution.
Instead, I would advise to do that change in Dockerfile-debian.template and run ./update.
If you are upgrading across multiple major versions, that has the benefit of "fixing" all the Dockerfiles at once.
+1 currently I am on nextcloud v20.0.4 using the docker apache image. I am trying to upgrade the container to 20.0.14 in order to upgrade to the current major version after that. However, due to this error the container won't start an I have no upgrade path available. Is this error fixed in v21? Can the upgrade to 20.0.14 be omitted?
I am running on synology DSM 7.0.1, so there is no kernel update available.
@leiterschleife Synology needs to fix this. In the meantime, as mentioned further above, you can fix it yourself. Using outdated packages would not be the preferred solution for everyone.
@m4rkv5 Has anyone given Synology a hint about this? What are the versions known to be working again? Would I need to do the manual fix from now on for any future version of nextcloud? If so, this cannot be expected from every user hosting a nextcloud docker image on a diskstation as I expect there are plenty of them.
@leiterschleife Yes you need to patch every version in your upgrade path. You only need to use the commands from above. Have a backup. My database was already V23 but I needed a specific V22 first.
Synology don't issue kernel updates. It's sort of fixed hardware.
Time marches on never-ending and software dependencies are upgraded, and here we are with broken things.
I'd love to know the reason for -bullseye over -buster, even if it is in vain.
It's good to see RSS-Bridge and other repos actively going back to -buster
I had the same problem with centos7οΌThe container automatically exits after starting. Check logs. ErrorοΌFunction not implemented: AH00141: Could not initialize random number generator
my solution was to upgrade the kernel
-
Check my server kernel: Linux 3.10.0-123.el7.x86_64
-
After kernel upgrade: Linux 6.0.5-1.el7.elrepo.x86_64
-
Problem solved
Forgive my non-standard English expression;
I can reproduce this issue on a Synology RS3617xs with DSM 6.2.4-25556. On a DS1618+ with DSM 7.0-41890 it is working fine.
My workaround was to edit the Dockerfile to use
php:8.0-apache-busteras base image instead ofphp:8.0-apache-bullseyeand build it on my own. Otherwise a switch to the fpm image could a be a workaround for this issue.BTW, same issue for the bitnami apache image: https://github.com/bitnami/bitnami-docker-apache/issues/106
Can you please elaborate the procedure of changing the docker file on a synology nas?
Can you please elaborate the procedure of changing the docker file on a synology nas?
Step 1: Change line 1 of Dockerfile-debian.template, here is the git patch:
diff --git a/Dockerfile-debian.template b/Dockerfile-debian.template
index d3fb81e..9b5ea71 100644
--- a/Dockerfile-debian.template
+++ b/Dockerfile-debian.template
@@ -1,4 +1,4 @@
-FROM php:%%PHP_VERSION%%-%%VARIANT%%-bullseye
+FROM php:%%PHP_VERSION%%-%%VARIANT%%-buster
# entrypoint.sh and cron.sh dependencies
RUN set -ex; \
Step 2: Run update.sh.
Step 3: Build desired Docker images.
Step 4: Profit? :D
I just succesfully worked around this with version 27.0.1 downgrading the PHP base image from php:8.2-apache-bookworm to php:8.2-apache-buster. So far so good it still works with v27 and bookworm. FYI.
I just succesfully worked around this with version 27.0.1 downgrading the PHP base image from
php:8.2-apache-bookwormtophp:8.2-apache-buster. So far so good it still works with v27 and bookworm. FYI.
Me too. Big thanks for all of you guys for helping with that!
I did this:
1.- Clone Nextcloud repository into the docker-compose.yml directory
cd /docker-apps/nextcloud
git clone https://github.com/nextcloud/docker.git
2.- Changed the version name of debian (bullseye, bookwork or whatever it is) to buster in the Dockerfile. Look for it in the corresponding version directory under the cloned Nextcloud repository (in this case /docker-apps/nextcloud/docker/27/apache/Dockerfile)
3.- After changing to the Dockerfile path
cd /docker-apps/nextcloud/docker/27/apache/
I run the build command:
docker build -t nextcloudtest . -f Dockerfile
4.- A few years later I modified the docker-compose.yml file to match the new nextcloud image name (nextcloudtest):
vim docker-compose.yml
nextcloud-app:
image: nextcloudtest
5.- And finally started all up.
docker compose up -d && docker compose logs -f
It is just all of the above in a single post. I just compiled it ;-)
Regards,
Mauricio
2.- Changed the version name of debian (bullseye, bookwork or whatever it is) to buster in the
Dockerfile. Look for it in the corresponding version directory under the cloned Nextcloud repository (in this case/docker-apps/nextcloud/docker/27/apache/Dockerfile)
This is not ideal in case you want to update properly!
There's a better way:
- Modify the
update.shas follows (git diffsyntax):
@@ -7,8 +7,7 @@ declare -A alpine_version=(
)
declare -A debian_version=(
- [25]='bullseye'
- [default]='bookworm'
+ [default]='buster'
)
(i.e. set [default] to buster and remove the exception for [25])
-
Save this changes to git stash with
git stash store "$(git stash create)".
This is helpful if you want to update this repo from upstream to get fixes for Dockerfiles later. -
Run
./update.sh. -
Build whatever version(s) you want. Example:
for (( NCV=25; NCV<=27; NCV++ )); do docker buildx build -t nextcloud:$NCV $NCV/apache; done
This will build all recent NextCloud apache images for versions [25; 27] for amd64.
If you have an account on DockerHub, you can do this:
for (( NCV=25; NCV<=27; NCV++ )); do docker buildx build --push -t <your-account>/nextcloud:$NCV $NCV/apache; done
Now, whenever you want to update to the latest NC version, just do steps (3) and (4).
In case you also want to get repo updates from GitHub:
git reset HEAD --hard
git pull
git stash apply # apply changes in `update.sh` from stash
./update.sh
# insert your build command from step 4 here
And yes, if you feel too lazy for that and just need a fairly recent amd64 image for your Syno box or whatever and consider me a trustworthy source for docker images, feel free to just use my milux/nextcloud:[25/26/27].
Built on my Ubuntu machine, no modifications except base image as described above.