Closed Alfagun74 closed 1 year ago
It looks like system:install
command failed somehow wtf.
Whats your device 🤔
a decent server :(
_,met$$$$$gg. root@HADES
,g$$$$$$$$$$$$$$$P. ----------
,g$$P" """Y$$.". OS: Debian GNU/Linux bookworm/sid x86_64
,$$P' `$$$. Host: PRIMERGY RX300 S6 GS01
',$$P ,ggs. `$$b: Kernel: 5.18.0-2-amd64
`d$$' ,$P"' . $$$ Uptime: 4 hours, 33 mins
$$P d$' , $$P Packages: 1808 (dpkg)
$$: $$. - ,d$$' Shell: fish 3.5.0
$$; Y$b._ _,d$P' CPU: Intel Xeon X5680 (24) @ 1.596GHz
Y$$. `.`"Y$$$$P"' GPU: 09:00.0 Matrox Electronics Systems Ltd.
`$$b "-.__ Memory: 4739MiB / 145039MiB
`Y$$
`Y$$.
`$$b.
`Y$$b.
`"Y$b._
`"""
@shyim have you got a version of mysql/maria and shopware that definitely work together, so i can try?
Do you have a docker-compose.yml to reproduce it?
unfortunately i dont use docker-compose but i can try setting one up rl quick
Okay i tested around a little bit.
local mysql in docker compose works absolutely fine. remote mysql in docker compose crashes though.
My mysql server seems to be the problem. Which version should i use?
tried 5.7, same problem. maybe its the shopware package after all. i will roll back a couple versions and see.
maybe some connectivity issues?
No they are on the same local network and it works until around 17%
MySQL 5.7 Shopware 6.3.5.0
Didn't work either. Same Problem. What could be the cause for this 😩😩😩
maybe look into mysql logs 🤔
I need a reproducer I can't do anything
I know :(
I'm sorry. I can't seem to reproduce it either..
My RAID5 seems to be the issue i think.
When i map the Volume of MYSQL to another drive everything works fine.
Is it a no-go to use mysql databases on raid 5?
Can be fixed with mariadb instead of mysql:
# [...]
mysql:
image: mariadb:10.7.4
environment:
MYSQL_ROOT_PASSWORD: shopware
MYSQL_DATABASE: shopware
MYSQL_USER: shopware
MYSQL_PASSWORD: shopware
restart: on-failure
volumes:
- mysql-data:/var/lib/mysql
# [...]
Did anyone found how to solve this? I still cannot reproduce it 🙈
@shyim yes look at my last comment https://github.com/shyim/shopware/issues/42#issuecomment-1192879657 In my eyes this seems to be a compatibility issue with the newer mysql version. But even if it is or not I don't understand why to use mysql anyway. Mysql has a "difficult" license agreement and so in general I can only recommend mariadb.
MariaDB is fully GPL licensed while MySQL takes a dual-license approach. MariaDB supports a lot of different storage engines. In many scenarios, MariaDB offers improved performance.
MariaDB runs much slower than MySQL 8 for Shopware as we use a lot of JSON fields
Ok that makes sense. However, after checking again today, I don't think it's the RAID as described in the comment by Alfagun74 because I don't use RAID (on the hard drive where the container is located).
Basically I think that it may have something to do with an edgecase. Here are some system data from me maybe they help: Debian 11 Bullseye, stable, on an AMD Ryzen 2700, 128GB DDR4 3600mhz, Nvidia GT700, 2TB NVME Samsung EVO 900, virtualization: Docker version 20.10.20, build 9fdeb9c + Portainer.
Does someone have an idea how we can improve this directly in this image. I would otherwise close it, as I can't reproduce it. 🙈
Despite changing hosts (this time to an Intel server with NVMe storage), the same problem persisted. However, after running some benchmarks with example data in Shopware, I did not observe any significant differences in speed with mariadb.
Oh almost forgot, locally it works fine, it's just on my servers that's the problem. I don't know. You could close this and add a reference to this ticket in the readme if someone has similar problems.
Maybe it helps to configure some variables inside the MySQL server like innodb_buffer_pool_size :)
Everything is empty and clean. Still fails in Migration all the time.
Logs:
Verisons used:
shyim/shopware:6.4.13.0
mariadb:10.3.27
ENV:
Volumes mapped: