DETECT: Task: 'off' flag corruption for pid #329
Labels
bug
Something isn't working
Comments
|
@solardiz Unfortunately I can't find anything for: What is interesting it is not failing always for |
|
Can you please try uncommenting |
Here is the one with debug enabled, this time with different container: dmesg: |
|
Thanks @80kk , could you also enable log_level to level 4 under |
How can I do this? The only log_level occurrence I found in this file is in: |
|
@80kk You don't need to patch anything to adjust |
|
Here is the call trace with and Docker container log: |
|
I don't know if that matters but as you probably already noticed this is a VM running on Proxmox. Underlying hardware is Dell PowerEdge R320. |
|
Sorry for late reply. I tried to repro your issue under VmWare: but under the kernel and everything works fine. Is there anything specific to repro it? |
|
Well, as I wrote in my first post: There was no 24.04 released at that time and hypervisor is Proxmox but I don't think that this is the factor. I will probably upgrade to 24.04 during this weekend and update the ticket. |
|
Unfortunately there is no official way for upgrading to 24.04 until 24.04.1 will be released. If you think this issue is resolved in 6.8 kernel then feel free and close this ticket. |
|
Even if the issue is resolved or otherwise avoided in 6.8, we may still care to fix it for older kernels. LKRG supports a wide range of kernel versions. |
|
I spent some time to do the same test on: Under the kernel In the kernel logs I can see that LKRG runs fine: No other logs related to LKRG. However, I have a question @80kk , do you see in the logs something similar to those messages? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just started with LKRG by building it for Ubuntu 22.04 with 5.15.0-101-generic kernel. So far it seems to be working fine however I am getting everyday:
host is running Docker containers for Mailcow while none of the containers were restarted/killed it looks more like it prevent new container from starting?
The text was updated successfully, but these errors were encountered: