I followed the config guide and added a line to my.ini to set the buffer size to 1017M and restarted my whole system. I still continue to be told when starting HMM that the buffer size is too small although all the other settings seemed to have worked ok. I can see from the log that the size is being set correctly so I ma guessing the size should actually be bigger than 1017M. Any suggestion as to what value to try next?
MariaDb can mix configurations from various places so just editing my.ini might not always help.
You can check the actual variables by executing the SHOW VARIABLES command (against the database engine) and review the results of the actual used values.
Another way is to check Helium's logs which dumps the results from SHOW VARIABLES.
If you need further in-detail assistance you can take contact with our support: support.imploded.com
C
Colin Piper
said
over 3 years ago
Answer
1023M seemed to work. I will stick with that.
Mikael Stalvik
said
over 3 years ago
Great, feel free to contact us for more in detail assistance.
Mathias Thelker
said
about 2 years ago
Just to let you know that despite 1017M worked for me using MariaDB 10.3 on a NAS, the line "innodb_log_buffer_size=800M" does not work at all (including changing to 500M).
MariaDB does not start if I include that line in my.cnf.
So I just left it out.
Mikael Stalvik
said
about 2 years ago
Please note that settings depends on the backend hardware, a NAS has generally more limited capabilities compared to a "standard" server setup.
Colin Piper
I followed the config guide and added a line to my.ini to set the buffer size to 1017M and restarted my whole system. I still continue to be told when starting HMM that the buffer size is too small although all the other settings seemed to have worked ok. I can see from the log that the size is being set correctly so I ma guessing the size should actually be bigger than 1017M. Any suggestion as to what value to try next?
1023M seemed to work. I will stick with that.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstMikael Stalvik
MariaDb can mix configurations from various places so just editing my.ini might not always help.
You can check the actual variables by executing the SHOW VARIABLES command (against the database engine) and review the results of the actual used values.
Another way is to check Helium's logs which dumps the results from SHOW VARIABLES.
If you need further in-detail assistance you can take contact with our support: support.imploded.com
Colin Piper
1023M seemed to work. I will stick with that.
Mikael Stalvik
Great, feel free to contact us for more in detail assistance.
Mathias Thelker
Just to let you know that despite 1017M worked for me using MariaDB 10.3 on a NAS, the line "innodb_log_buffer_size=800M" does not work at all (including changing to 500M).
MariaDB does not start if I include that line in my.cnf.
So I just left it out.
Mikael Stalvik
Please note that settings depends on the backend hardware, a NAS has generally more limited capabilities compared to a "standard" server setup.
-
Dots in play queue
-
Tag Editor with fields
-
tag and rename files not (yet) under neon control
-
Helium Streamer and NEON
-
Date format ...
-
Neon blues ..
-
Helium remote for Android
-
Determination of discography
-
Application did not start
-
MOD- / SID-tunes
See all 134 topics