-
-
Notifications
You must be signed in to change notification settings - Fork 790
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
2.0.25 gives Restarting (132) issue in docker #2959
Comments
same here. |
Create an
Then run: docker compose down
docker compose pull
docker compose up -d |
Your issue does not contain sufficient information for troubleshooting. It does not even contain logs. Please provide logs and provide more information about the hardware you are running this on. Especially the cpu properties are interesting. You can get these via |
@Diman0
For me, there are no logs. With
|
Does it work when you set an empty |
Almost, all containers except oletools start. oletools continues with exit code 132. |
I just see that on 2.0.24, I have the following message in every container log (at the very beginning):
Might that help? @Diman0 |
It is probably due to the updated hardened malloc. It might need more modern hardware now. but oletools has not been updated to use this method: So oletools must be updated to also use this method. @Dennis14e A potential workaround is too pass all the CPU flags of the host processor to the VM. |
@Diman0 |
Same problem here, and same as @Dennis14e: I am using a VM from an hosting provider, which I cannot control. |
I have the same problem on a 'real' server; /proc/cpuinfo ` processor : 1 processor : 2 processor : 3 |
Here is my
It is just using the
|
+1 processor : 0 |
Thanks for the tip, worked as expected. Should be documented in the wiki ? So 2.0.24 is hopefully working, but latest version is not at the moment i am writing this. I run mailu on ARCH x86_64 , nothing very fancy. Never went into this type of trouble with updating mailu until now.
|
root@mail:/mailu# docker-compose up |
We have been talking about this on #mailu-dev: The new version of hardened-malloc requires the AVX2 instruction set... our current test only checks for AVX, which explains why Mailu now fails to start when started on some CPUs. Assuming you are using and controlling a virtualized environment (qemu), you may be able to change the CPU features exposed and enable AVX2 (mainstream CPUs have it since 2011). We will release a new build shortly that will address the problem by disabling hardened-malloc by default. |
Ok, looking forward to new releases |
2961: Hardened malloc was not disabled for oletools when an CPU with missing flags is used r=mergify[bot] a=Diman0 ## What type of PR? bug fix ## What does this PR do? Updates oletools to also disable hardened malloc when used CPU misses flags ### Related issue(s) - closes #2959 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [n/a ] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz> Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
2961: Hardened malloc was not disabled for oletools when an CPU with missing flags is used r=mergify[bot] a=Diman0 ## What type of PR? bug fix ## What does this PR do? Updates oletools to also disable hardened malloc when used CPU misses flags ### Related issue(s) - closes #2959 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [n/a ] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz> Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
2961: Hardened malloc was not disabled for oletools when an CPU with missing flags is used r=mergify[bot] a=Diman0 ## What type of PR? bug fix ## What does this PR do? Updates oletools to also disable hardened malloc when used CPU misses flags ### Related issue(s) - closes #2959 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [n/a ] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz> Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
2961: Hardened malloc was not disabled for oletools when an CPU with missing flags is used r=nextgens a=Diman0 ## What type of PR? bug fix ## What does this PR do? Updates oletools to also disable hardened malloc when used CPU misses flags ### Related issue(s) - closes #2959 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [n/a ] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz> Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
2961: Hardened malloc was not disabled for oletools when an CPU with missing flags is used r=nextgens a=Diman0 ## What type of PR? bug fix ## What does this PR do? Updates oletools to also disable hardened malloc when used CPU misses flags ### Related issue(s) - closes #2959 ## Prerequisites Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list. - [n/a ] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. Co-authored-by: Dimitri Huisman <diman@huisman.xyz> Co-authored-by: Dimitri Huisman <52963853+Diman0@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@users.noreply.github.com> Co-authored-by: Florent Daigniere <nextgens@freenetproject.org>
v2.0.27 is out and should fix this; let us know if it's still broken |
Everything runs smooth again. |
I just run v2.0.27. Appears to work fine. |
Environment & Version
Environment
Version
2.0.25
Description
pulled the latest build (2.0.25) and the mailu docker containers would no longer start. They would go to a status of "Restarting (132)" and continuously just restart
Replication Steps
Observed behaviour
Expected behaviour
Docker containers to start up and run
Logs
The text was updated successfully, but these errors were encountered: