Thanks everyone I think we got it working....for some reason when I built the apache22 port it did not create the data directory....duh, so to be sure that was all, I did a deisntall and rebuilt the port.....everything seems to be working now.
I have a similar issue, when I reboot or run rcvar on any other function I get the message that Apache22 was not found, which is to be expected since there is no apache22 script in /etc/rc.d, eventhough it is a vanilla install from ports. And yet, it starts and runs without any issues as far as I can tell.
I also have a jailed webserver on top of this machine that does the exact same thing.
I find it is a bit odd that I have three functioning apache22 flags set (below)... how can this be? and can I fix it?
FreeBSD ports don't install anything under /etc, since that belongs to the base system. Ports install everything under /usr/local, and you should find the start scripts installed by ports in /usr/local/etc/rc.d/. This is a very important and thoroughly basic FreeBSD law: base system and add-on software are separated (a very small number of exceptions exist, namely ports that overrule elements of the base system, like Sendmail or BIND from ports, and some ports that like to play in /var).
Note that FreeBSD also has service(8), so you can run [cmd=]service apache22 rcvar[/cmd] instead of [cmd=]/usr/local/etc/rc.d/apache22 rcvar[/cmd]
service(8) covers both /etc/rc.d and /usr/local/etc/rc.d, so it will run everything under both with the usual flags (start, stop, restart, rcvar, status).
I am barely self-taught and tend to nut things out as I think of things I want to do. I haven't really had any reason before to look into rc scripts before but it explains another issue I have been having though.
I don't know how the underscore went missing, but that was definitely the cause of the error in dmesg, I forgot to mention it, but I was getting the apache22 not found error at startup also. Oddly enough mod_ssl has been working.