[Solved] "IP address registered in Plesk is invalid or broken" / KB 122545 wrong solution

[Bitpalast]

Centos 7.1, Plesk 12.0.8, trying to upgrade "in-place" to 12.5. The system has an IPv4 and IPv6 address. Both were in use before the initial 12.0.8 installation was done. There have never been any problems at all with these addresses. In "Tools & Settings"->"IP addresses" both addresses are present.

Symptom: The pre-upgrade check fails with "IP address registered in Plesk is invalid or broken".
Following KB article 122545 the addresses are re-read. But there is not "repair" option anywhere (the KB article says one should click "repair" after re-reading the addresses). So even after following KB 122545 the problem still exists. The IP addresses that are clearly available on the system and have always been the same even before the first Plesk version was installed AND are also listed in the Plesk admin panel are not recognized by the pre-upgrade check.

How can the issue be solved?

 

[IgorG]

Try to run 'reread' in CLI with

# plesk bin ipmanage --reread

and check possible errors in output and then in Tools & Settings > IP addresses.

 

[Bitpalast]

Ran all fine with error code 0. No changes in "Tools & settings"->"IP addresses". Issue in pre-upgrade check still exists.

 

[vlikhtanskiy]

Hi @Peter Debik!

I have sevaral questions:
1. Is the broken IP address is IPv4 or IPv6?
2. Are here any warnings near IP addresses on Tools&Settings > IP Addresses after running Reread on this screen? You can post a screenshot here masking the IP addresses shown.

 

[Bitpalast]

(1) IPv4
(2) No. Screenshot attached.

 

[vlikhtanskiy]

Compare output of the following commands:
# plesk sbin ifmng --list
# ifconfig -a | grep "inet addr"
# ip addr list | grep "inet "

Do they return the same IP addresses except 127.0.0.1?

 

[Bitpalast]

(the X.XX sequence is identical among the ipv4-addresses and among the ipv6-addresses given)

[root@...]# ifconfig -a | grep "inet"
inet 136.24X.XX.75 netmask 255.255.255.255 broadcast 136.24X.XX.75
inet6 fe80::a62:66ff:XXXX:62fb prefixlen 64 scopeid 0x20<link>
inet6 2a01:4f8:XXX:84a::2 prefixlen 64 scopeid 0x0<global>
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>

[root@...]# ip addr list | grep "inet"
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
inet 136.24X.XX.75 peer 136.24X.XX.65/32 brd 136.24X.XX.75 scope global eth0
inet6 2a01:4f8:XXX:84a::2/64 scope global
inet6 fe80::a62:66ff:XXXX:62fb/64 scope link

[root@...]# plesk sbin ifmng --list
136.24X.XX.75 255.255.255.255 eth0 1
2a01:4f8:XXX:84a::2 64 eth0 0

The only difference I see is that Plesk does not know the fe80 ipv6-address, but it has never complained about that and there is nothing in the web servers using that address. The specific error message when trying the upgrade is:
"WARNING: IP address registered in Plesk is invalid or broken: 136.24X.XX.75"

I only found one independent blog entry on the issue: http://blog.matoski.com/articles/upgrade-plesk-11-5-to-12-fixing-dkim-dk/
However, that one is on Debian, we are on CentOS.

 

[vlikhtanskiy]

Everything is OK with your IP addresses. There is bug and this warning is false positive. You can agree to continue your upgrade.

 

[Bitpalast]

Solved. Upgrade did work despite warning. Thank you for your support.

 

[vlikhtanskiy]

Glad to help you!

 

[basavantk]

I am getting this following error. Is it safe to proceed? Can anyone suggest what needs to be done to fix this error and warning.