Can't get into console - asterisk.ctl does not exist

i have some server that i installed Asterisk , asterisknow and elastix on them
Asterisknow and elastix work correctly
but for asterisk ( 1.8 ) , asterisk service start automatic after booting server.
so i teried "asterisk -rvvvv"
and here is the result:
[root@Asterisk-Home ~]# asterisk -r
Asterisk SVN-branch-1.8-r375325, Copyright © 1999 - 2012 Digium, Inc. and others.
Created by Mark Spencer
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

i checked the path : /var/run/asterisk/ and there is asterisk.ctl
i test it by root and my runuser of asterisk " runuser=shahram"
and there is no difrent
also SELLINUX is disabled.

all of above test was with ssh terminal,now i test “asterisk -rvvvv” without ssh ( directly connect to system by keyboard ) and it enter to the asterisk succesfully.
so after booting system asterisk will start but i cant work with it by ssh.
[b]first qustion : why it dosnt work with ssh ? [/b] now i exit asterisk by " core stop now " and try again asterisk -rvvvv by ssh and directly but it dosnt work
and now in /var/runs/asterisk/ there isn`t any thing

now i test “safe-asterisk” and it started the asterisk service and i can login by ssh to asterisk and it work normal

but why “safe-asterisk” work and “asterisk -rvvvv” dosn`t work?
i want to use this server in a enterprise location and i want to be sure about it.

so my questions were :
1 - why at startup asterisk work directly and dosn`t work with ssh?
2- why after stop the asterisk manualy and start it again, just whit “safe-asterisk” it will start?
thank for your attention

no any idia?

Generally you get this error if Asterisk fails to start (but the presence of …ctl indicates that this is not the case), or because of permission problems (you seem to have addressed the permission problems, except in that you are running non-root, which does seem prone to creating them).

All I can suggest is turning up the debugging, on both sides.