• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Pre-upgrade check from 12.0.18 to 12.5.30 warning

Jat

New Pleskian
Hi,

I'm trying to upgrade to the last Plesk panel version in a Ubuntu 14.04 server, but i get this warning:

"Parallels Panel pre-upgrade check...
/etc/init.d/apparmor: 35: .: Can't open /lib/apparmor/functions
WARNING: Unable to find "main" IP address in psa database. Please, check http://kb.odin.com/en/112417 for more details."

I have followed the kb resolution showed in the message but still showing the same warning.
Apparmor is not installed in my system.
 
But do you have file /etc/init.d/apparmor on your server? Make sure that Apparmor package is completely uninstalled and disable apparmor init script with

# /etc/init.d/apparmor stop
# /etc/init.d/apparmor teardown
# update-rc.d -f apparmor remove
 
Hi,

I have renamed the appamor init script and now i don't get the appamor error, but still getting the "WARNING: Unable to find "main" IP address in psa database." and the KB resolution is not working for me.
Any idea?
 
Try to fix it with

# /usr/local/psa/bin/ipmanage --reread
 
I already did it, this procedure is in the KB but not resolve :(

root@xxxx:/etc/init.d# /usr/local/psa/bin/ipmanage --reread
IP addresses were reread from the system.
 
And what is output of following SQL query from psa database?

select id, ip_address, main from IP_Addresses;
 
Set it to 'true' with

update IP_Addresses set main='true' where id=2;

BTW, it is strange that you have not IP address with id=1 and main='true' in this table. Are you sure that you have no missing IP address?
 
Not sure what do you mean with missing IP address. This two links show the IP setup i have in the server:

http://screencast.com/t/YjAfKT4MqcW
http://screencast.com/t/K9FVoO2Lu

Now i'm done with that command, this is the output:

mysql> update IP_Addresses set main='true' where id=2;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

mysql> select id, ip_address, main from IP_Addresses;
+----+----------------+------+
| id | ip_address | main |
+----+----------------+------+
| 2 | 159.171.xxx.xxx | true |
+----+----------------+------+

Must i try to update Plesk now, or need to do any other step before?
 
It seems that update process have finished without errors.

Thank for your help, have a nice day! :)
 
Hi,
I have the same issue but with updating Onyx version to 17.5.3.
Pre-upgrade check show "WARNING: Unable to find "main" IP address in psa database."
I read KB article Unable to list APS applications: Search results could not be loaded at the moment
and yes, I have in plesk database two IP-s with false main status

1. 188.99.xx.xxx false
2. 22a01:4f8:10a:xxxx::2 false

Those two IP-s are in Tools and Settings, and I Reread it, but nothing changed.
Is it safe to change that 1. IP to True, and after that run update?
What's the worst that can happen?
 
Yes it is safe. You can simply manually update the data set to "true". The major difference afterwards is that the IP address will be shown in bold face type and that Plesk prohibits its removal through the GUI IP address function. Else there are no consequences that follow from the manual change.
 
Helo Peter,
thank you for answer.

I changed it and updated plesk to 17.5.3.
And yes, that IP address after changing status to true, was bold.
After rereading IPs, again status for that IP was changed to "false"
 
I do not know why this is happening, I think it is a bug, but don't really know whether it is or whether a setting on the server is causing the utility to treat both IP addresses equally and set both to false.
 
Back
Top