snappahead Posted December 28, 2014 Report Share Posted December 28, 2014 I can usually troubleshoot emerge errors after a bit of thinking and googling, but this one has me stumped. Anyone seen this before? >>> Source compiled. * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-18339.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: unlink S: deny P: /sys/fs/cgroup/sem.AdPVho A: /sys/fs/cgroup/sem.AdPVho R: /sys/fs/cgroup/sem.AdPVho C: python2.7 setup.py build -b build-2.7 F: unlink S: deny P: /sys/fs/cgroup/sem.cnQVGD A: /sys/fs/cgroup/sem.cnQVGD R: /sys/fs/cgroup/sem.cnQVGD C: python3.3 setup.py build -b build-3.3 * -------------------------------------------------------------------------------- Link to comment Share on other sites More sharing options...
0 Oleg Vinichenko Posted December 28, 2014 Report Share Posted December 28, 2014 cannot reproduce this one. Please, give more details on this, emerge --info, imaging version. And steps leading to this failure. Link to comment Share on other sites More sharing options...
0 snappahead Posted December 28, 2014 Author Report Share Posted December 28, 2014 Hey Oleg, Thanks for taking a look at it. I started troubleshooting again this morning. This was occurring in a chrooted environment. I booted into the OS and the error went away...I'm definitely not savvy enough with portage to explain why there was a difference, but it seems to have rectified itself. Link to comment Share on other sites More sharing options...
Question
snappahead
I can usually troubleshoot emerge errors after a bit of thinking and googling, but this one has me stumped. Anyone seen this before?
Link to comment
Share on other sites
2 answers to this question
Recommended Posts