07.03.2015, 12:14
chmod u+x the file, mhm. I am thinking of two things here.
One, either your file system is enabled with the noexec option. Run a grep on noexec in the file system (mount | grep noexec) and check if noexec is there. If yes, then let me know.
Other than that, probably a shared object, plugin or executable that SA-MP is trying to open for which it doesn't have the required permissions. This is kind-of unlikely, but just to be safe, run a ldd or strace on samp03svr.
Other than the aforementioned, I have no clue..
EDIT: It must be the noexec option enabled. Is your distribution newly installed? And was it a pure install or a install with some other needed settings and programs?
One, either your file system is enabled with the noexec option. Run a grep on noexec in the file system (mount | grep noexec) and check if noexec is there. If yes, then let me know.
Other than that, probably a shared object, plugin or executable that SA-MP is trying to open for which it doesn't have the required permissions. This is kind-of unlikely, but just to be safe, run a ldd or strace on samp03svr.
Other than the aforementioned, I have no clue..
EDIT: It must be the noexec option enabled. Is your distribution newly installed? And was it a pure install or a install with some other needed settings and programs?