Ok, long story short, we've got directadmin running on eth0 with approx 35 dedicated ip addresses.
We're having to move ISPs, which means we're getting a whole new IP range.
I've enabled the new ISP connection on eth1 and that seems to work fine. However, when I add IP addresses in DirectAdmin on the new range it adds them as aliases for eth0.
I've found the config setting in directadmin.conf for ethernet_dev and setting that to eth1 instead of eth0 prevents directadmin from starting up correctly.
I get the error: directadmin dead but pid exists when doing a service directadmin status after doing a restart of the service.
Changing back to eth0 works.
I'm sure at some point I will need to get my license file updated to the new ip, but is there a way to get it up and running before that? or am I doing something wrong?
Any help on this is greatly appreciated.
Thanks
We're having to move ISPs, which means we're getting a whole new IP range.
I've enabled the new ISP connection on eth1 and that seems to work fine. However, when I add IP addresses in DirectAdmin on the new range it adds them as aliases for eth0.
I've found the config setting in directadmin.conf for ethernet_dev and setting that to eth1 instead of eth0 prevents directadmin from starting up correctly.
I get the error: directadmin dead but pid exists when doing a service directadmin status after doing a restart of the service.
Changing back to eth0 works.
I'm sure at some point I will need to get my license file updated to the new ip, but is there a way to get it up and running before that? or am I doing something wrong?
Any help on this is greatly appreciated.
Thanks