Im running true nas on a thinkcentre m77 (lemmy.world)

submitted 1 year ago by Oliper202020@lemmy.world to c/truenas@programming.dev

13 comments fedilink hide all child comments

Im running true nas with i think 12 gigabytes of ram, i will upgrade soon, an i just upgraded the cpu to an amd fx 6350 but it seems when i try to run any apps i can maximum run 1-2 apps and thats without nfs or anything else, and i have more free ram, and the cpu doesn't seem to be overloaded at all

So what can i do to get it running better, I currently run it on a hdd but i dont think that would make it just not work

top 12 comments

sorted by: hot top controversial new old

[-] Sleeping@programming.dev 1 points 1 year ago

What type of issues are you running into specifically, because while you may face some slow-downs if your system can't handle the load, you should still be able to spin up multiple apps. If you're just noticing a slow-down of one of your apps, you could try upping the limit in the resource limits section in the app.

[-] Oliper202020@lemmy.world 1 points 1 year ago

It just doesn't start more then 1-2 apps i have waited for over an hour and had it still not start

[-] Sleeping@programming.dev 1 points 1 year ago* (last edited 1 year ago)

What do the app logs say?

[-] Oliper202020@lemmy.world 1 points 1 year ago

sorry for slow reply but i only got home just now

[-] Sleeping@programming.dev 1 points 1 year ago

No worries, my response times aren't great either, haha.

[-] Oliper202020@lemmy.world 1 points 1 year ago

2023-07-05T19:41:33.229299334Z [38;5;6mmariadb [38;5;5m19:41:33.11 [0m 2023-07-05T19:41:33.233191009Z [38;5;6mmariadb [38;5;5m19:41:33.23 [0m[1mWelcome to the Bitnami mariadb container[0m 2023-07-05T19:41:33.236841741Z [38;5;6mmariadb [38;5;5m19:41:33.23 [0mSubscribe to project updates by watching [1mhttps://github.com/bitnami/containers[0m 2023-07-05T19:41:33.240604041Z [38;5;6mmariadb [38;5;5m19:41:33.23 [0mSubmit issues and feature requests at [1mhttps://github.com/bitnami/containers/issues[0m 2023-07-05T19:41:33.244090500Z [38;5;6mmariadb [38;5;5m19:41:33.24 [0m 2023-07-05T19:41:33.247746637Z [38;5;6mmariadb [38;5;5m19:41:33.24 [0m[38;5;2mINFO [0m ==> ** Starting MariaDB setup ** 2023-07-05T19:41:33.322764486Z [38;5;6mmariadb [38;5;5m19:41:33.32 [0m[38;5;2mINFO [0m ==> Validating settings in MYSQL_*/MARIADB_* env vars 2023-07-05T19:41:33.479546090Z [38;5;6mmariadb [38;5;5m19:41:33.47 [0m[38;5;2mINFO [0m ==> Initializing mariadb database 2023-07-05T19:41:33.515956897Z [38;5;6mmariadb [38;5;5m19:41:33.51 [0m[38;5;2mINFO [0m ==> Updating 'my.cnf' with custom configuration 2023-07-05T19:41:33.628580896Z [38;5;6mmariadb [38;5;5m19:41:33.62 [0m[38;5;2mINFO [0m ==> Setting user option 2023-07-05T19:41:34.418620781Z [38;5;6mmariadb [38;5;5m19:41:34.41 [0m[38;5;2mINFO [0m ==> Setting slow_query_log option 2023-07-05T19:41:34.654633345Z [38;5;6mmariadb [38;5;5m19:41:34.65 [0m[38;5;2mINFO [0m ==> Setting long_query_time option 2023-07-05T19:41:35.172076687Z [38;5;6mmariadb [38;5;5m19:41:35.17 [0m[38;5;2mINFO [0m ==> Using persisted data 2023-07-05T19:41:35.634146293Z [38;5;6mmariadb [38;5;5m19:41:35.63 [0m[38;5;2mINFO [0m ==> Running mysql_upgrade 2023-07-05T19:41:35.639562515Z [38;5;6mmariadb [38;5;5m19:41:35.63 [0m[38;5;2mINFO [0m ==> Starting mariadb in background 2023-07-05T19:41:36.356710832Z 2023-07-05 19:41:36 0 [Note] Starting MariaDB 10.11.4-MariaDB source revision 4e2b93dffef2414a11ca5edc8d215f57ee5010e5 as process 64 2023-07-05T19:41:36.589249912Z 2023-07-05 19:41:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2023-07-05T19:41:36.597583237Z 2023-07-05 19:41:36 0 [Note] InnoDB: Number of transaction pools: 1 2023-07-05T19:41:36.597834782Z 2023-07-05 19:41:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-07-05T19:41:36.597934021Z 2023-07-05 19:41:36 0 [Note] mysqld: O_TMPFILE is not supported on /opt/bitnami/mariadb/tmp (disabling future attempts) 2023-07-05T19:41:36.678741742Z 2023-07-05 19:41:36 0 [Note] InnoDB: Using Linux native AIO 2023-07-05T19:41:36.680114044Z 2023-07-05 19:41:36 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2023-07-05T19:41:36.687357950Z 2023-07-05 19:41:36 0 [Note] InnoDB: Completed initialization of buffer pool 2023-07-05T19:41:36.746930639Z 2023-07-05 19:41:36 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) 2023-07-05T19:41:36.805296172Z 2023-07-05 19:41:36 0 [Note] InnoDB: 128 rollback segments are active. 2023-07-05T19:41:36.838503079Z 2023-07-05 19:41:36 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2023-07-05T19:41:36.838606659Z 2023-07-05 19:41:36 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2023-07-05T19:41:36.841511669Z 2023-07-05 19:41:36 0 [Note] InnoDB: log sequence number 46880; transaction id 16 2023-07-05T19:41:36.842163270Z 2023-07-05 19:41:36 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-07-05T19:41:36.846398093Z 2023-07-05 19:41:36 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool 2023-07-05T19:41:36.932992849Z 2023-07-05 19:41:36 0 [Note] InnoDB: Buffer pool(s) load completed at 230705 19:41:36 2023-07-05T19:41:36.949688141Z 2023-07-05 19:41:36 0 [Note] Server socket created on IP: '127.0.0.1'. 2023-07-05T19:41:37.017659620Z 2023-07-05 19:41:37 0 [Warning] 'proxies_priv' entry '@% root@nginx-proxy-manager-mariadb-776f4cc7d4-l6v44' ignored in --skip-name-resolve mode. 2023-07-05T19:41:37.112141224Z 2023-07-05 19:41:37 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections. 2023-07-05T19:41:37.112208709Z Version: '10.11.4-MariaDB' socket: '/opt/bitnami/mariadb/tmp/mysql.sock' port: 3306 Source distribution 2023-07-05T19:41:39.139792290Z find: '/docker-entrypoint-startdb.d/': No such file or directory 2023-07-05T19:41:39.151435486Z [38;5;6mmariadb [38;5;5m19:41:39.15 [0m[38;5;2mINFO [0m ==> Stopping mariadb 2023-07-05T19:41:39.158494426Z 2023-07-05 19:41:39 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown 2023-07-05T19:41:39.159973241Z 2023-07-05 19:41:39 0 [Note] InnoDB: FTS optimize thread exiting. 2023-07-05T19:41:39.342026607Z 2023-07-05 19:41:39 0 [Note] InnoDB: Starting shutdown... 2023-07-05T19:41:39.342069450Z 2023-07-05 19:41:39 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool 2023-07-05T19:41:39.342928420Z 2023-07-05 19:41:39 0 [Note] InnoDB: Buffer pool(s) dump completed at 230705 19:41:39 2023-07-05T19:41:39.606173500Z 2023-07-05 19:41:39 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2023-07-05T19:41:39.606290031Z 2023-07-05 19:41:39 0 [Note] InnoDB: Shutdown completed; log sequence number 46880; transaction id 17 2023-07-05T19:41:40.499996532Z 2023-07-05 19:41:40 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete 2023-07-05T19:41:40.500130925Z 2023-07-05T19:41:41.584886105Z [38;5;6mmariadb [38;5;5m19:41:41.58 [0m[38;5;2mINFO [0m ==> ** MariaDB setup finished! ** 2023-07-05T19:41:41.584935613Z 2023-07-05T19:41:41.848864377Z [38;5;6mmariadb [38;5;5m19:41:41.84 [0m[38;5;2mINFO [0m ==> ** Starting MariaDB ** 2023-07-05T19:41:41.908943380Z 2023-07-05 19:41:41 0 [Note] Starting MariaDB 10.11.4-MariaDB source revision 4e2b93dffef2414a11ca5edc8d215f57ee5010e5 as process 1 2023-07-05T19:41:41.978850759Z 2023-07-05 19:41:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2023-07-05T19:41:41.983209839Z 2023-07-05 19:41:41 0 [Note] InnoDB: Number of transaction pools: 1 2023-07-05T19:41:41.983287526Z 2023-07-05 19:41:41 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2023-07-05T19:41:41.983353436Z 2023-07-05 19:41:41 0 [Note] mysqld: O_TMPFILE is not supported on /opt/bitnami/mariadb/tmp (disabling future attempts) 2023-07-05T19:41:42.013526774Z 2023-07-05 19:41:42 0 [Note] InnoDB: Using Linux native AIO 2023-07-05T19:41:42.013899642Z 2023-07-05 19:41:42 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2023-07-05T19:41:42.061884525Z 2023-07-05 19:41:42 0 [Note] InnoDB: Completed initialization of buffer pool 2023-07-05T19:41:42.070127144Z 2023-07-05 19:41:42 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) 2023-07-05T19:41:42.096125578Z 2023-07-05 19:41:42 0 [Note] InnoDB: 128 rollback segments are active. 2023-07-05T19:41:42.096733642Z 2023-07-05 19:41:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2023-07-05T19:41:42.096854870Z 2023-07-05 19:41:42 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2023-07-05T19:41:42.098346040Z 2023-07-05 19:41:42 0 [Note] InnoDB: log sequence number 46880; transaction id 16 2023-07-05T19:41:42.098443835Z 2023-07-05 19:41:42 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool 2023-07-05T19:41:42.098533836Z 2023-07-05 19:41:42 0 [Note] Plugin 'FEEDBACK' is disabled. 2023-07-05T19:41:42.101095181Z 2023-07-05 19:41:42 0 [Note] InnoDB: Buffer pool(s) load completed at 230705 19:41:42 2023-07-05T19:41:42.132781359Z 2023-07-05 19:41:42 0 [Note] Server socket created on IP: '0.0.0.0'. 2023-07-05T19:41:42.134787348Z 2023-07-05 19:41:42 0 [Warning] 'proxies_priv' entry '@% root@nginx-proxy-manager-mariadb-776f4cc7d4-l6v44' ignored in --skip-name-resolve mode. 2023-07-05T19:41:42.138145091Z 2023-07-05 19:41:42 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections. 2023-07-05T19:41:42.138205530Z Version: '10.11.4-MariaDB' socket: '/opt/bitnami/mariadb/tmp/mysql.sock' port: 3306 Source distribution

[-] Sleeping@programming.dev 1 points 1 year ago

From the logs you've provided, it appears the MariaDB server indicated a normal shutdown process without providing a specific reason for the shutdown initiation. So I'm assuming within your app it's running multiple containers, would you be able to provide the log of the container that is running into an error that's causing your app to call the shutdowns.

[-] Oliper202020@lemmy.world 1 points 1 year ago

I will do my best to find them😅

[-] Sleeping@programming.dev 1 points 1 year ago

No worries, also to note there may be multiple pods as well as containers, so be sure to check those as well. Although, you can get a pretty good hint at which container is failing based on the application events log that you can first see when you click on the app.

I wanted to provide some screenshots in my last reply, but I was getting an error while trying to upload them, hopefully some of these might help to guide you.

For Application Events:

Example of Multiple Pods:

[-] Oliper202020@lemmy.world 1 points 1 year ago

But could really slow hard drive for applications be the cause, because im currently using an external hard drive, so its not great

[-] Sleeping@programming.dev 1 points 1 year ago

No, slow transfer speeds should not outright stop an app from functioning.

[-] Oliper202020@lemmy.world 1 points 1 year ago

That's what I was thinking but it could be, I don't know all that much about true nas, it could be made so things need to load before a time out and then it tries again, will have to look more at the logs later

load more comments

this post was submitted on 06 Jul 2023

7 points (100.0% liked)

TrueNAS

577 readers

1 users here now

Welcome to the unofficial TrueNAS community!

Here for all things TrueNAS whether you need help with your core, scale, or enterprise edition setups or if you just want to discuss random stuff pertaining to TrueNAS!

Useful Links:

TrueNAS:

Truecharts:

Main MOD: @Sleeping@programming.dev

founded 1 year ago

MODERATORS

Ategon@programming.dev

Sleeping@programming.dev