IP address not present on the interface, Click to repair

[Tsi-Shawn]

Looking around the Internet for a resolution I found a post here from 2009 that stated this was repaired in Plesk 10. I am running 10.4 on CentOS6 and every time I reboot my server I have to go in and repair each I.P, which leaves remote reboots a can't do.

Any help would be appreciated.

Shawn

 

[Tsi-Shawn]

Is there no one that has run into this since the 10+ release?

 

[Faris Raouf]

I have run into problems where an IP address that's NOT actually allocated on any interface is listed in plesk, but from the sounds of it some other issue is affecting you.

Please can you be more specific? When you have to say "have to go in and repair" what do you actually mean? Into Plesk?
If that's the case then it is possible that the network interfaces are not coming up before Plesk starts (try delaying the plesk startup). Or into the data centre because the network interface isn't running? If that's the case then there may be something totally non-plesk going on on the network side. Plesk 10 (11 is different) should not touch ifcfg files at boot and normally doesn't do anything network related (though there are exceptions).

Or something else again?
Is there nothing to see in dmesg or boot.log or /var/log/messages relating to network/ethernet on reboot that might help you pinpoint the issue?

 

[Tsi-Shawn]

After a server reboot I have to go into the Plesk Control Panel and then under Settings - IP's I have to reload the IP's then click repair next to them to re-bind them. Only then can my customers have web access back. I have read that this was patched in 10+ but I still have this issue.