-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
(38)Function not implemented: AH00141: Could not initialize random number generator #1574
Comments
Additional context: 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 BTW, same issue for the bitnami apache image: |
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) : 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? |
Hi, anyone an idea how an already updated DB/data can be rolled back from 21.1.1.2 to 21.1.0.1 ? |
Same issue with Docker running on a Synology DS1515+ with DSM 6.2.4. |
@WarSonic69
Which git repository are you cloning?
What exactly do you change. Greatly appreciated. |
I Gitcloned the Nextcloud/docker repo : https:/nextcloud/docker.git I changed this line in the Dockerfile : 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:
|
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 |
+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. 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
Forgive my non-standard English expression; |
Can you please elaborate the procedure of changing the docker file on a synology nas? |
Step 1: Change line 1 of
Step 2: Run 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 |
Me too. Big thanks for all of you guys for helping with that! 1.- Clone Nextcloud repository into the docker-compose.yml directory
2.- Changed the version name of debian (bullseye, bookwork or whatever it is) to buster in the 3.- After changing to the Dockerfile path
I run the build command:
4.- A few years later I modified the
5.- And finally started all up.
It is just all of the above in a single post. I just compiled it ;-) Regards, |
This is not ideal in case you want to update properly!
(i.e. set
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:
And yes, if you feel too lazy for that and just need a fairly recent |
How to use GitHub
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.
[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 !
The text was updated successfully, but these errors were encountered: