When will we get an Update that Supports the 8GB of RAM?
EV21
July 28, 2020, 10:08pm
2
Raspberry Pi OS 64-bit is still beta.Raspberry Pi OS (64 bit) beta test version
Or watch regularly this site until the 64-bit version is released.Official Raspberry Pi OS Downloads
Do you already have tried the beta and installing NCP via install-script?
curl -sSL https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh | bash
If this is not working you have to wait or look for an alternative.
When I try to install it on the beta 64-bit version it fails completely.
Do you happen to know how fast the OwnYourBits developers are with such problems? I am certainly not the only one who wants to install nextcloud on the RaspberryPi 4 Model B 8GB RAM.
EV21
July 29, 2020, 9:25am
4
True
opened 10:56PM - 08 Jun 20 UTC
closed 01:00AM - 03 Aug 20 UTC
bug
<!--
Thanks for reporting issues back to NextCloudPi!
Here you can file bug… s and feature requests. **Do NOT ask questions**, this is not a support forum.
If there is an important security issue that has gone unnoticed, please send a private email to nacho _at_ ownyourbits.com
### DO NOT ASK QUESTIONS, USE THE FORUMS
NCP and its extras are explained in the wiki, also make sure to read the articles in ownyourbits explaining NextCloudPi extras before asking. https://ownyourbits.com/category/nextcloudpi/
For asking questions, please use the forums. https://help.nextcloud.com/c/support/appliances-docker-snappy-vm
### PROBLEMS
Please, look at the FAQ before posting a new issue. Also, make sure it has not been asked before. https://github.com/nextcloud/nextcloudpi/wiki/FAQ
Keep in mind that many problems come from faulty power sources and corrupted SD cards, so make sure this is not the case for you before reporting.
If you are running into problems, make sure to include the output of `sudo ncp-report`
-->
On a fresh install of Raspberry Pi OS (version from 2020-05-27) on a new Raspberry Pi 4 with 8 GB RAM, either using Docker or a traditional installation, the Nextcloud server can't fully start. When opening the website at localhost and pressing "Activate", it gets stuck at "NextCloudPi not yet initialized, trying again in a few seconds...".
This is because MariaDB fails to start: `docker logs nextcloudpi` yields the line `Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!`
Furthermore, starting `mysqld` from the Docker container yields this in `/var/log/mysql/error.log`:
```
2020-06-08 22:46:39 0 [Note] InnoDB: Initializing buffer pool, total size = 3.125G, instances = 1, chunk size = 128M
2020-06-08 22:46:39 0 [ERROR] InnoDB: mmap(136118272 bytes) failed; errno 12
2020-06-08 22:46:40 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2020-06-08 22:46:40 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-06-08 22:46:40 0 [Note] InnoDB: Starting shutdown...
double free or corruption (out)
200608 22:46:41 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Server version: 10.3.22-MariaDB-0+deb10u1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466218 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /data/database
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 61664 61664 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core
```
I could temporarily resolve this be editing `/etc/mysql/mariadb.conf.d/91-npc.cnf` and decreasing the `innodb_buffer_pool_size` from 3341182566 to (e.g.) 341182566 After this, the mysql database starts with `mysqld`. The server is then functional, although very slow - not sure if that's related to this issue.
I've tested this on a completely new Raspberry Pi with a completely fresh Raspberry Pi OS install, so I'm fairly certain that this isn't caused by some configuration error on my side, although I suppose a hardware issue is always possible.
Also, I'm new to this so I'm not sure whether my workaround is sensible - it was just the first thing I tried that worked (it made sense due to the mysql error log). Please let me know if there is a better way to temporarily resolve this.
**System information**
Raspberry Pi 4 with 8 GB RAM
