DirectAdmin not starting on server reboot after migration to new hardware/network

mcsko

Verified User
Joined
Sep 26, 2019
Messages
6
Hi,

I've just migrated my server with DA installation to new hardware and new IP.

After updating the hostname, IP's etc everything is working as it should.

Except that the directadmin service doesn't start automatically after a reboot.

I have to use the CLI and manually issue a start command, e.g. service directadmin start and then it works. Obviously this isn't ideal.

Oddly I've noticed that issuing the command service directadmin restart actually makes the DA service stop and doesn't start the service either. Even though it shows as OK.

[root@ scripts]# service directadmin restart
Stopping DirectAdmin: [FAILED]
Starting DirectAdmin: [ OK ]


Can anyone assist please. I have no idea what is causing this.

Thanks :)
 

mcsko

Verified User
Joined
Sep 26, 2019
Messages
6
Did you remember to change the IP in the licenses in your DirectAdmin acount at https://directadmin.com ? And if OS changed, also update OS in the license? And then maybe you also would need to update the license on your server: https://help.directadmin.com/item.php?id=30

If that is not the reason, then I don't know. Maybe contact DirectAdmin support?
HI! Thanks for your reply. Yes. I've actually had another/new license issued for the most recent IP. OS is the same too. I've checked the logs and seeing references to 'bad sock' when initiating a restart. Think you're right about needing DA support. Cheers.
 
Top