IRC channel logs

2022-03-10.log

back to list of logs

***rekado_ is now known as rekado
***zimoun` is now known as zimoun_
<zimoun_>hi!
<civodul>o/
<zimoun_>civodul, I get ’guix gc: erreur : build daemon out of memory’; as discussed recently. So I strace it and I get: «openat(AT_FDCWD, "/gnu/store/mp8yfgzxs3ww5kj8rpnkn133pmm16jd6-guix-locale-guix/fr_FR.UTF-8/LC_MESSAGES/guix.mo", O_RDONLY) = -1 ENOENT (Aucun fichier ou dossier de ce type)»
<rekado>zimoun_: FYI I received your patches for R packages, but I haven’t been able to take a look yet.
<rekado>(just had dental surgery)
<zimoun_>rekado: oh, you are cumulating annoying health stuff… I hope everything is fine.
<civodul>zimoun_: could you share the whole trace?
<civodul>and the /proc/PID/maps output, as discussed last time? :-)
<zimoun_>the hard disk is full, maybe that’s the reason.
<zimoun_>how do I get /proc/PID/maps ?
<zimoun_>At the very beginning, it read «openat(AT_FDCWD, "/gnu/store/wmsy2fmx6x2j0nmy3h5mlhjpsb6p8isc-guile-wrapper/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Aucun fichier ou dossier de ce type)»
<zimoun_>oh, I get 2 PID for guix-daemon ?
<civodul>zimoun_: open /proc/PID/maps, where PID is the PID of the guix-daemon process
<civodul>the "SessionPID" bit in "guix processes"
<zimoun_>ah crap! I killed the faulty process.
<zimoun_>root 1500 0.0 0.0 12676 876 ? Ss janv.31 0:00 guix-daemon --build-users-group=guixbuild --max-jobs=8
<zimoun_>root 1073651 48.3 0.0 30496 2736 ? Ss févr.03 24477:08 guix-daemon 1073633 --max-jobs=8
<zimoun_>this second one was the culprit, I guess. Now it is gone and it works.
<zimoun_>So I can still share the complete strace but not /proc/PID/maps
<civodul>thinking about it, i think the strace output won't tell us much about where memory usage goes :-/
<civodul>well, next time?
<civodul>had it been running for a long time?
<zimoun_>3rd feb. I guess.
<zimoun_>I suspect the process had been blocked by full disk space. Next time. :-)
<rekado>re full disk: maybe we can use /dev/full to simulate the condition?
<rekado>zimoun: health stuff is annoying, but not too surprising given the fact that this body is way past its warranty.
<zimoun_>heh
<civodul>zimoun_: BTW, were you successful with video editing?
<zimoun_>civodul: no time this week-end (I was in Marseille helping a friend with their vegatables farm :-)) and this week is ending too fast... and no time next week-end. Arf, hard the life of an artist. ;-) roptat is quite busy too…
<zimoun_>Well, I will try to drop an email for sectioning the 3 rushes…
<civodul>heheh :-)
<civodul>i'm still curious to listen to what was said back then
<zimoun_>you can listen when sectionning ? ;-)
<zimoun_>civodul: have you been in the business of frama-c, code specs, contracts, code specs and the like?
<rekado>is there a way to override /bin/sh in “guix shell -C”?
<rekado>basically I want to use an existing root file system and since /bin/sh already exists I can’t just do --expose=/the/root/fs=/
<rekado>I guess I could just remove /the/root/fs/bin/sh :)
<civodul>zimoun_: i think frama-c is wonderful, but only as long as you think C is necessary
<civodul>rekado: does --expose=/the/root/fs=/ work, or does it clash with the built-in /bin/sh mapping?
<zimoun_>civodul: I see, otherwise it is OCaml or Haskell. ;-)
<rekado>civodul: it clashes with /bin/sh.
<rekado>I worked around it by running “rm -rf /bin; ln -s -t / /usr/bin” in the container
<rekado>this is a CentOS root fs where /bin is just a link to /usr/bin, so this works
<civodul>ok