Hi Ole, unfortunately, I have been not able to reproduce the problem on a fresh CentOS 7.6.1810 test VM (as you suggested). The operating system is he same, also coreutils package version is the same, but the error only appears in the production server.
So, I know that it’s up to me to debug and solve this strange issue. In any case, I would like to share with you an interesting thing: if I set -j equal to 1 or a value less than the “test” file lines (in my particular use-case I need to do that), the error appears. If I set -j equal to 9 the problem disappears. [user@production]> cat test echo 1 echo 2 echo 3 echo 4 echo 5 echo 6 echo 7 echo 8 echo 9 [user@production]> parallel -j1 -k < test 1 2 3 4 5 6 7 8 9 type=ANOM_ABEND msg=audit(1715720158.732:217252): auid=0 uid=0 gid=0 ses=29426 pid=166139 comm="sleep" reason="memory violation" sig=11 I will try to solve this issue by myself, but, if you have any interesting idea, please, share it with me :) Many thanks for the time you spent for my case. Have a great day, Mauro > On 13 May 2024, at 14:09, Mauro Tridici <[email protected]> wrote: > > Good morning Ole, > > many thanks for your kind support. > I’m sorry for my late reply, but I just found this message in my spam box. > > I will try to follow your instruction. > In any case, I can confirm that “sleep memory violation” appears during the > parallel startup. > > If I run sleep command separately, it works as expected and it doesn’t > produce any error. > > I will investigate further. > Have a great day, > Mauro > >> On 9 May 2024, at 08:12, Ole Tange <[email protected]> wrote: >> >> On Mon, May 6, 2024 at 3:22 PM Mauro Tridici <[email protected]> wrote: >> : >>> checking the operating system (CentOS 7.2) audit logs, I detect a lot of >>> "sleep command memory violation". >>> I investigated about this issue for almost a week and I think I found the >>> cause of the error message mentioned above. >>> It seems it is related to the "parallel" command usage and I'm able to >>> replicate the problem as follows. >>> >>> Could you please help me to understand what I'm doing wrong and how to fix >>> this issue? >> >> I tested with https://app.vagrantup.com/Gigasavvy/boxes/centos7-LAMP >> and cannot reproduce the problem. >> >> Please follow >> https://www.gnu.org/software/parallel/man.html#bug-dependent-on-environment >> >>> type=ANOM_ABEND msg=audit(1714688507.057:173872): auid=0 uid=0 gid=0 >>> ses=23831 pid=74652 comm="sleep" reason="memory violation" sig=11 >> >> This smells like `sleep` is doing a memory violation - so not an issue >> with GNU Parallel. But it might be that GNU Parallel triggers this. >> GNU Parallel calls `sleep` during startup. >> >> A wild guess is that the specific binary of `sleep` that you have >> installed for some odd reason crashes when called from GNU Parallel. >> >> All of this is easier to verify if you follow >> https://www.gnu.org/software/parallel/man.html#bug-dependent-on-environment >> >> >> /Ole > >
