#49217 cgroup memory usage in bytes not always present
Closed: wontfix 6 years ago Opened 7 years ago by firstyear.

Issue Description

Sometimes we see this message:

>> [11/Apr/2017:16:52:38.089185390 -0700] - ERR - _spal_get_uint64_t_file -
> >> Unable to open file "/sys/fs/cgroup/memory/memory.limit_in_bytes". errno=13

It looks like the memory limit_in_bytes may not be present on newer fedora.

This should be checked and fixed.


May affect usage_in_bytes also.

Metadata Update from @firstyear:
- Custom field type adjusted to defect

7 years ago

Metadata Update from @firstyear:
- Issue assigned to firstyear

6 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.7.0

6 years ago

I think this is actually from the SELinux policy issues we saw in BZ. @nhosoi can I ask you to check your audit log when you test next? 'ausearch -ts recent' should do it.

Does this help?

$ sudo ausearch -ts recent  | egrep 389
type=USER_CMD msg=audit(1493248986.517:2193): pid=18654 uid=1001 auid=1001 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/export/src/ds/ldapserver/ldapserver/docker/389ds_poc" cmd=646F636B6572206275696C64202D742033383964735F706F633A6C6174657374202E terminal=pts/1 res=success'
type=USER_CMD msg=audit(1493249066.866:2198): pid=18687 uid=1001 auid=1001 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/export/src/ds/ldapserver/ldapserver/docker/389ds_poc" cmd="dockerd" terminal=pts/1 res=success'
type=USER_CMD msg=audit(1493249099.125:2231): pid=18895 uid=1001 auid=1001 ses=5 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/export/src/ds/ldapserver/ldapserver/docker/389ds_poc" cmd=646F636B6572206275696C64202D742033383964735F706F633A6C6174657374202E terminal=pts/1 res=success'

$ sudo cat /sys/fs/cgroup/memory/memory.limit_in_bytes
9223372036854771712

Here's the test result...

make[4]: Entering directory `/usr/local/src/389-ds-base/rpmbuild/BUILD/389-ds-base-1.3.6.3'
PASS: test_slapd
PASS: test_libsds
PASS: test_nuncstans
FAIL: test_nuncstans_stress_small
============================================================================
Testsuite summary for 389-ds-base 1.3.6.3
============================================================================
# TOTAL: 4
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

Hmmm, that's a different set of issues I think. I think whatever spirit that possessed my laptop and causes random issues has migrated to your machine instead >.<

Is this in a docker container, or outside of it?

It looks related to BZ 1444864,is there AVC in your case ?

Hmmm, that's a different set of issues I think. I think whatever spirit that possessed my laptop and causes random issues has migrated to your machine instead >.<
Is this in a docker container, or outside of it?
In a docker container. I haven't tried outside this time, but I remember it worked just fine last time...

It looks related to BZ 1444864,is there AVC in your case ?
I upgraded my selinux policy just in case, but it did not change the behavior...
selinux-policy.noarch 3.13.1-225.13.fc25
selinux-policy-targeted.noarch 3.13.1-225.13.fc25

But I got the same result as in this comment...
https://pagure.io/389-ds-base/issue/49217#comment-438565

I'd like to get the AVC on the docker, but once the test failed, the container is already gone. :)

FAIL: test_slapd
PASS: test_libsds
PASS: test_nuncstans
PASS: test_nuncstans_stress_small

[==========] Running 3 test(s).
[ RUN      ] test_plugin_hello
[       OK ] test_plugin_hello
[ RUN      ] test_plugin_pwdstorage_pbkdf2_auth
[  ERROR   ] --- pbkdf2_sha256_pw_cmp("password", password_a) == 0
[   LINE   ] --- test/plugins/pwdstorage/pbkdf2.c:48: error: Failure!
[  FAILED  ] test_plugin_pwdstorage_pbkdf2_auth
[ RUN      ] test_plugin_pwdstorage_pbkdf2_rounds
[       OK ] test_plugin_pwdstorage_pbkdf2_rounds

It seems there is some flaking in the docker build that I need to look into :)

#49268 resolves the test issue, and the other issue here was SELinux, so closing invalid. Thanks for testing @nhosoi !!!

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2276

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata