Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

I can not emerge I get ACCESS VIOLATION

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
13 posts • Page 1 of 1
Author
Message
eyexer0
Tux's lil' helper
Tux's lil' helper
Posts: 75
Joined: Sat Dec 13, 2003 4:20 pm
Location: Fort Smith, Arkansas
Contact:
Contact eyexer0
Website

I can not emerge I get ACCESS VIOLATION

  • Quote

Post by eyexer0 » Fri Sep 29, 2006 3:20 pm

I have installed samba and ldap and now I can not emerge anything..

emerge portage

Code: Select all

fs1 home # emerge portage
Calculating dependencies... done!

>>> Emerging (1 of 1) sys-apps/portage-2.1.2_pre1-r4 to /
request done: ld 0x81f2bb8 msgid 1
request done: ld 0x81f2bb8 msgid 2
request done: ld 0x81f2bb8 msgid 3
request done: ld 0x81f2bb8 msgid 4
request done: ld 0x81f2bb8 msgid 5
request done: ld 0x81f2bb8 msgid 6
request done: ld 0x81f2bb8 msgid 7
request done: ld 0x81f2bb8 msgid 8
request done: ld 0x81f2bb8 msgid 9
request done: ld 0x81f2bb8 msgid 10
request done: ld 0x81f2bb8 msgid 11
request done: ld 0x81f2bb8 msgid 12
request done: ld 0x81f2bb8 msgid 13
request done: ld 0x81f2bb8 msgid 14
request done: ld 0x81f2bb8 msgid 15
request done: ld 0x81f2bb8 msgid 16
request done: ld 0x81f2bb8 msgid 17
request done: ld 0x81f2bb8 msgid 18
request done: ld 0x81f2bb8 msgid 19
request done: ld 0x81f2bb8 msgid 20
request done: ld 0x81f2bb8 msgid 21
request done: ld 0x81f2bb8 msgid 22
request done: ld 0x81f2bb8 msgid 23
request done: ld 0x81f2bb8 msgid 24
request done: ld 0x81f2bb8 msgid 25
request done: ld 0x81f2bb8 msgid 26
request done: ld 0x81f2bb8 msgid 27
request done: ld 0x81f2bb8 msgid 28
request done: ld 0x81f2bb8 msgid 29
request done: ld 0x81f2bb8 msgid 30
request done: ld 0x81f2bb8 msgid 31
 * portage-2.1.2_pre1-r4.patch.bz2 MD5 ;-) ...                            [ ok ]
 * portage-2.1.2_pre1-r4.patch.bz2 RMD160 ;-) ...                         [ ok ]
 * portage-2.1.2_pre1-r4.patch.bz2 SHA1 ;-) ...                           [ ok ]
 * portage-2.1.2_pre1-r4.patch.bz2 SHA256 ;-) ...                         [ ok ]
 * portage-2.1.2_pre1-r4.patch.bz2 size ;-) ...                           [ ok ]
 * portage-2.1.2_pre1.tar.bz2 MD5 ;-) ...                                 [ ok ]
 * portage-2.1.2_pre1.tar.bz2 RMD160 ;-) ...                              [ ok ]
 * portage-2.1.2_pre1.tar.bz2 SHA1 ;-) ...                                [ ok ]
 * portage-2.1.2_pre1.tar.bz2 SHA256 ;-) ...                              [ ok ]
 * portage-2.1.2_pre1.tar.bz2 size ;-) ...                                [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking portage-2.1.2_pre1.tar.bz2 ;-) ...                            [ ok ]
 * checking portage-2.1.2_pre1-r4.patch.bz2 ;-) ...                       [ ok ]
request done: ld 0x81f2ed0 msgid 1
request done: ld 0x81f2ed0 msgid 2
request done: ld 0x81f2ed0 msgid 3
request done: ld 0x81f2ed0 msgid 4
request done: ld 0x81f2ed0 msgid 5
request done: ld 0x81f2ed0 msgid 6
request done: ld 0x81f2ed0 msgid 7
request done: ld 0x81f2ed0 msgid 8
request done: ld 0x81f2ed0 msgid 9
request done: ld 0x81f2ed0 msgid 10
request done: ld 0x81f2ed0 msgid 11
request done: ld 0x81f2ed0 msgid 12
request done: ld 0x81f2ed0 msgid 13
request done: ld 0x81f2ed0 msgid 14
request done: ld 0x81f2ed0 msgid 15
request done: ld 0x81f2ed0 msgid 16
request done: ld 0x81f2ed0 msgid 17
request done: ld 0x81f2ed0 msgid 18
request done: ld 0x81f2ed0 msgid 19
request done: ld 0x81f2ed0 msgid 20
request done: ld 0x81f2ed0 msgid 21
request done: ld 0x81f2ed0 msgid 22
request done: ld 0x81f2ed0 msgid 23
request done: ld 0x81f2ed0 msgid 24
request done: ld 0x81f2ed0 msgid 25
request done: ld 0x81f2ed0 msgid 26
request done: ld 0x81f2ed0 msgid 27
request done: ld 0x81f2ed0 msgid 28
request done: ld 0x81f2ed0 msgid 29
request done: ld 0x81f2ed0 msgid 30
request done: ld 0x81f2ed0 msgid 31
ACCESS DENIED  open_wr:   /var/log/nss_ldap/ldap.11059
ACCESS DENIED  open_wr:   /var/log/nss_ldap/ldap.11059
request done: ld 0x815c540 msgid 1
request done: ld 0x815c540 msgid 2
request done: ld 0x815c540 msgid 3
request done: ld 0x815c540 msgid 4
request done: ld 0x815c540 msgid 5
request done: ld 0x815c540 msgid 6
request done: ld 0x815c540 msgid 7
request done: ld 0x815c540 msgid 8
request done: ld 0x815c540 msgid 9
request done: ld 0x815c540 msgid 10
request done: ld 0x815c540 msgid 11
request done: ld 0x815c540 msgid 12
request done: ld 0x815c540 msgid 13
request done: ld 0x815c540 msgid 14
request done: ld 0x815c540 msgid 15
request done: ld 0x815c540 msgid 16
request done: ld 0x815c540 msgid 17
request done: ld 0x815c540 msgid 18
request done: ld 0x815c540 msgid 19
request done: ld 0x815c540 msgid 20
request done: ld 0x815c540 msgid 21
request done: ld 0x815c540 msgid 22
request done: ld 0x815c540 msgid 23
request done: ld 0x815c540 msgid 24
request done: ld 0x815c540 msgid 25
request done: ld 0x815c540 msgid 26
request done: ld 0x815c540 msgid 27
request done: ld 0x815c540 msgid 28
request done: ld 0x815c540 msgid 29
request done: ld 0x815c540 msgid 30
request done: ld 0x815c540 msgid 31
>>> Unpacking source...
>>> Unpacking portage-2.1.2_pre1.tar.bz2 to /var/tmp/portage/portage-2.1.2_pre1-r4/work
ACCESS DENIED  open_wr:   /var/log/nss_ldap/ldap.11063
ACCESS DENIED  open_wr:   /var/log/nss_ldap/ldap.11063
request done: ld 0x81225e8 msgid 1
request done: ld 0x81225e8 msgid 2
request done: ld 0x81225e8 msgid 3
request done: ld 0x81225e8 msgid 4
>>> Unpacking portage-2.1.2_pre1-r4.patch.bz2 to /var/tmp/portage/portage-2.1.2_pre1-r4/work
 * Applying portage-2.1.2_pre1-r4.patch ...                               [ ok ]
 * Setting portage.VERSION to 2.1.2_pre1-r4 ...                           [ ok ]
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-sys-apps_-_portage-2.1.2_pre1-r4-11035.log"

open_wr:   /var/log/nss_ldap/ldap.11059
open_wr:   /var/log/nss_ldap/ldap.11059
open_wr:   /var/log/nss_ldap/ldap.11063
open_wr:   /var/log/nss_ldap/ldap.11063
--------------------------------------------------------------------------------
Top
steveL
Watchman
Watchman
Posts: 5153
Joined: Wed Sep 13, 2006 1:18 pm
Location: The Peanut Gallery

  • Quote

Post by steveL » Fri Sep 29, 2006 5:49 pm

I have no idea what that's about, it looks horrible; you must be tearing your hair out?

Anyone?
Top
masterdriverz
Retired Dev
Retired Dev
Posts: 391
Joined: Tue Mar 28, 2006 7:30 pm
Location: Far out in the uncharted backwaters of the unfashionable end of the Western Spiral arm of the galaxy

  • Quote

Post by masterdriverz » Fri Sep 29, 2006 6:03 pm

Its a sandbox error, try adding "-sandbox" to your FEATURES until you can work out why it happens.
Top
eyexer0
Tux's lil' helper
Tux's lil' helper
Posts: 75
Joined: Sat Dec 13, 2003 4:20 pm
Location: Fort Smith, Arkansas
Contact:
Contact eyexer0
Website

  • Quote

Post by eyexer0 » Sat Sep 30, 2006 5:22 am

where is the FEATURES? at?
Top
masterdriverz
Retired Dev
Retired Dev
Posts: 391
Joined: Tue Mar 28, 2006 7:30 pm
Location: Far out in the uncharted backwaters of the unfashionable end of the Western Spiral arm of the galaxy

  • Quote

Post by masterdriverz » Sat Sep 30, 2006 7:53 am

In make.conf:
make.conf wrote:FEATURES="-sandbox"
Top
cokey
Advocate
Advocate
User avatar
Posts: 3355
Joined: Fri Apr 23, 2004 12:30 am

  • Quote

Post by cokey » Tue Oct 03, 2006 12:33 pm

masterdriverz wrote:In make.conf:
make.conf wrote:FEATURES="-sandbox"
no, please tell him to add that to the emerge instead of turning it off for every emerge. Use it like this instead:

Code: Select all

FEATURES="-sandbox" emerge foo
https://otw20.com/ OTW20 The new place for off the wall chat
Top
kallamej
Administrator
Administrator
User avatar
Posts: 4993
Joined: Fri Jun 27, 2003 10:05 am
Location: Gothenburg, Sweden

  • Quote

Post by kallamej » Tue Oct 10, 2006 8:32 pm

Please do not disable the sandbox unless you really know what you're doing. While far from perfect, it is there to protect you from emerges doing nasty stuff to your file system. Sandbox violations are almost always bugs that need to be reported and fixed properly.
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat
Top
Fluid_Donkey
n00b
n00b
Posts: 31
Joined: Tue Jun 18, 2002 9:50 pm

  • Quote

Post by Fluid_Donkey » Tue Oct 31, 2006 6:24 pm

Has anyone figured out the cause of this? I've tried screwing with it from a few different directions but nothing seems to help. In my case it's currently only a problem on the test server so I have no qualms about turning sandbox off however that really isn't an acceptable fix/solution.

It looks like nss_ldap is complaining about not being able to open log files for writing. That would be my interpretation of open_wr proceeded by Access Denied. However there is no obvious reason this would be happening. Directory permissions were fine but for funsies I did a chmod 777 that didn't help. I could also be complaining about the sandbox logs but there aren't any filesystem issues there either. It's appears to be an application level access/authentication issue but I have no idea where it is origionating from.
Top
kallamej
Administrator
Administrator
User avatar
Posts: 4993
Joined: Fri Jun 27, 2003 10:05 am
Location: Gothenburg, Sweden

  • Quote

Post by kallamej » Tue Oct 31, 2006 8:45 pm

Fluid_Donkey wrote:Has anyone figured out the cause of this? I've tried screwing with it from a few different directions but nothing seems to help. In my case it's currently only a problem on the test server so I have no qualms about turning sandbox off however that really isn't an acceptable fix/solution.

It looks like nss_ldap is complaining about not being able to open log files for writing. That would be my interpretation of open_wr proceeded by Access Denied. However there is no obvious reason this would be happening. Directory permissions were fine but for funsies I did a chmod 777 that didn't help. I could also be complaining about the sandbox logs but there aren't any filesystem issues there either. It's appears to be an application level access/authentication issue but I have no idea where it is origionating from.
The sandbox prevents ebuilds from doing stuff outside of the build directory (typically /var/tmp/portage/package-version)

I can't find anything in Bugzilla about it so you may want to file a new bug.
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat
Top
kallamej
Administrator
Administrator
User avatar
Posts: 4993
Joined: Fri Jun 27, 2003 10:05 am
Location: Gothenburg, Sweden

  • Quote

Post by kallamej » Thu Nov 09, 2006 10:48 pm

Split off unrelated [topic=514998]external kernel modules[/topic] issue.

Edit: And [post=3725957]another one[/post] split off.
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat
Top
srdjan.rosic
n00b
n00b
Posts: 5
Joined: Sat Sep 09, 2006 5:11 pm
Location: Belgrade, SP

  • Quote

Post by srdjan.rosic » Sun Dec 17, 2006 9:01 pm

well this might not help eyexer0, but It's a decent question and I think it deserves and answer.

at my machine pam is using nss which is using ldap to check something (I think :?) anyways putting
/etc/ldap.conf

Code: Select all

...
debug 0
...
helped.
Top
korda
n00b
n00b
Posts: 11
Joined: Sun Nov 14, 2004 6:40 pm
Location: Australia

  • Quote

Post by korda » Sat Dec 30, 2006 5:53 am

srdjan.rosic wrote:well this might not help eyexer0, but It's a decent question and I think it deserves and answer.

at my machine pam is using nss which is using ldap to check something (I think :?) anyways putting
/etc/ldap.conf

Code: Select all

...
debug 0
...
helped.
Yep, I had the same sort of problem as eyexer0 and that debug 0 line helped me emerge things. I had debug 256 in /etc/ldap.conf and that was causing my emerge issues, cheers for the fix srdjan.rosic.
Top
jaccort
n00b
n00b
Posts: 54
Joined: Tue Dec 02, 2003 10:03 pm
Contact:
Contact jaccort
Website

  • Quote

Post by jaccort » Sun Apr 15, 2007 12:40 pm

I had a very similar problem - couldn't emerge anything, not even sandbox itself.

Fix: Update sandbox and portage, with FEATURES="-sandbox".

Now I can turn sandbox back on and everything works.
Top
Post Reply

13 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic