I notice another problem too but its before this version. Sometimes lshttpd makes too many processes for itself. For example a one core license restarts or something and then has 2 root processes and 2 apache process and its very hard to kill the processes, they do not die immediately. Not sure if this is really a problem or not but I figured id point it out
well if you have apache off in the directadmin service monitor it should not start back.
I tried this though every which way, using the apache wrapper and everything with the monitor, it still done it. Only solution was to downgrade to the version before the latest. I would have normally written this off as freak occurence but its happened on 2 servers when I was posting in this thread and I went to setup a vps today and it was a brand new fresh vps - done the same thing. Would just quit out of nowhere and not start back
Yeah - this is happening on two of my DirectAdmin VPSes. Apache is off in the DirectAdmin service monitor but for some reason it starts right when lshttpd crashes, even though it's off in chkconfig too. Oh well - for now, I've downgraded back to 3.3.12 until a fix becomes available.