Permanently disable Direct Admin

[cpuwhiz22]

I was wondering if anyone is aware of a way to permanently disable Direct Admin other than a fresh OS install? The reason being that sites that have been cancelled are still being served because stopping apache, etc. and/or Direct Admin is useless because it is designed to restart itself and/or the services.

I was wondering if maybe removing the license file would prevent the service from starting? I have not tried yet, but if anyone knows better that would save me some time.

Any input is greatly appreciated.

Thanks!

 

[scsi]

If you stop the service from directadmin it will not restart or just edit /usr/local/directadmin/data/admin/services.status and change directadmin=ON to directadmin=OFF and then stop it via ssh

 

[nobaloney]

While this will stop DirectAdmin I'm not sure it will stop the per-minute cronjob run as part of DirectAdmin.

And frankly I'm not at all sure I understand what cpuwhiz22 is writing about. If you suspend users from DirectAdmin the sites won't start up again. If you need to suspend just one site within a user you can make a change to the user-level httpd.conf file, or simply rename the public_html directory and chattr it immutable.

Jeff

 

[Klaipedaville]

If you stop the service from directadmin it will not restart or just edit /usr/local/directadmin/data/admin/services.status and change directadmin=ON to directadmin=OFF and then stop it via ssh

It is either incorrect or I have DA malfunctioning somewhere.

1.) I tried stopping it from DA itself by going to "Service Monitor" and simply pressing "Stop" in there. However, after sometime services start by themselves.

2.) I tried stopping it as you suggest by going to usr/local/directadmin/data/admin/services.status and changing statuses to no. However, after sometime services start by themselves anyway.

Does anybody know if it is possible at all to stop it and to keep it stopped for good? Would appreciate any further suggestions / comments. Many thanks!

P.S. I control almost eveything myself from elsewhere and having a lot of services stopped and keeping them stopped for good even after re-booting the entire server is what I am after.

 

[nobaloney]

Change the name of the DirectAdmin service from directadmin to directadmin_off; that way it'll still be there if you ever want it again you can just rename it.

Or find the cronjob that keeps running the task queue, and remove it or comment it out.

Jeff

 

[Klaipedaville]

Hello Nobaloney,

Thank you so much for your suggestion! I will give it a try. However, will turning DA completely off will disable DA's regular access on its 2222 port as well?

Will carefilly go through all the cronjobs. Does DA mark its own cronjobs somehow for ease of reference for example?

 

[nobaloney]

Thank you so much for your suggestion! I will give it a try. However, will turning DA completely off will disable DA's regular access on its 2222 port as well?

Yes. DirectAdmin runs its own webserver. If you want DirectAdmin to run, but not do it's various cronjobs you'll need to disable crons, but that will disable a lot of functionality.

Will carefilly go through all the cronjobs. Does DA mark its own cronjobs somehow for ease of reference for example?

I don't recall the details. I believe there's only one, running the task.queue and everything else runs through that but I'm not sure.

If you really want to fix a problem with DirectAdmin not allowing you to disable certain services, then ask me to close this thread, and start another focusing on the main problem you're trying to solve, instead of asking how to do things which may or may not solve your problem.

For example, For all of us in my memory, DirectAdmin has no problem shutting off certain daemons and not restarting them. If that's what you need fixed, then let's focus on fixing that.

Jeff

 

[Klaipedaville]

Yes. DirectAdmin runs its own webserver. If you want DirectAdmin to run, but not do it's various cronjobs you'll need to disable crons, but that will disable a lot of functionality.

Thanks. Knowing that it runs its own webserver helps.

I don't recall the details. I believe there's only one, running the task.queue and everything else runs through that but I'm not sure.

I will double-check on it but I guess I saw only one as well.

...then ask me to close this thread, and start another focusing on the main problem you're trying to solve...

Feel free to do it as you please.

-----------------------------------

I really appreciate your suggestions and I am good to go on my own now, just needed a few tips and pointers on how it all operates. Disabling bash / boot scripts (exit 0 in the very beginning, setting no in services.statuses so that the dataskg won't check to see if they they are already running should do the trip for me and disable the services I want for good including boot time.