Root issues... su denied

[EmericanX]

OK I just figured I'd throw this out there hoping someone could clue me in to what I'm missing. I'm running an in secured boot.img and on full aosp 4.0.3 for the Gnex. I built user debug but when I didn't have root I flashed one the su.zips... I still cannot access root. I've filtered logcatand this is the output whenever anything tries to access su...

E/su (17526): sudb - Opening database
E/su (17526): sudb - Database opened
E/su (17526): sudb - Database closed
V/alogcat (17464): resumed
I/ActivityThread(17551): Pub com.google.android.calendar.CalendarRecentSuggestionsProvider: com.android.calendar.CalendarRecentSuggestionsProvider
I/ActivityManager( 179): No longer want com.noshufou.android.su (pid 16895): hidden #16
E/su (17526): select failed with 2: No such file or directory
W/su (17526): request rejected (10073->0 /system/bin/sh)

I can adb remount so I know my boot.img is good. I can also adb shell where it says @root # at least something along those lines. Can someone maybe point me in the right direction?

[git-core]

You have to build su from sources (either master or gc branch) or wait until 3.0.3.2 or greater will be available as a binary package.

ChainsDD, why does Superuser delete socket in this case?

[EmericanX]

are you referring to the su that is included in source? That su was included in the /system/xbin, but when that didn't allow root I replaced it with the su from a su.zip flash that was in the forum for a 4.0.3 build. When that didn't work I removed the old and placed it in /system/bin... no matter what I do I get the same logcat with failed access to root.

[git-core]

What source?? I referred to the git repository you've posted this issue against.
It doesn't matter where a build process puts the binary. You should copy it to /system/bin as you have done already. In fact, you may copy it to anywhere if you just test. I prefer /dev, for example.

If you pick up something from a forum, report to that forum, please.

[EmericanX]

I'm sorry. It seems like I may have asked in the wrong place. I'm not saying its an issue with the code... I'm pretty sure it user error somewhere! I'll continue trying to sort it out somewhere, some way! lol. again I apologize.... I'm still new to this! this can be closed..

[git-core]

In fact, you've asked in the right place. And what you've reported may be known issue with the code which has been fixed already. Again, to ensure this you shall compile master branch and try.