Article ID: 112253, created on Sep 12, 2011, last review on May 11, 2014

  • Applies to:
  • Plesk for Linux/Unix

Symptoms

When an IP address is added under a reseller account (Resellers, ResellerXX, IP Addresses, Add IP), the system responds with the following error:
Home>Resellers>ResellerXX>IP addresses>
ERROR: PleskFatalException

      

Up Level
Unable to load object of type IPAddress with id=5: Table->select() failed:
no such row in the table

0: common_func.php3:3273
    objectMakerEx(string 'IPAddress', integer '5')
1: IPPoolManager.php:993
    IPPoolManager::toString(integer '5', string 'exclusive')
2: class.PoolIPAddForm.php:49
    PoolIPAddForm->assign(array)
3: client.ipaddress.properties.php:68
    plesk__client__ipaddress__properties->renderAddForm()
4: client.ipaddress.properties.php:50
    plesk__client__ipaddress__properties->render(boolean true)
5: client.ipaddress.properties.php:33
    plesk__client__ipaddress__properties->accessItem(string 'GET', NULL
    null)
6: UIPointer.php:595
    UIPointer->access(string 'GET')
7: plesk.php:52

Cause

This issue is caused by an inconsistency in the Parallels Plesk Panel database. Orphan entries (referred to as IP addresses) remain attached to the Plesk administrator IP pool when the IP addresses are removed from the system.

Resolution

Step 1:
Find these IP addresses using the following query to the Parallels Plesk Panel database:
mysql> select ip_pool.id,ip_pool.ip_address_id,IP_Addresses.id from ip_pool left join IP_Addresses on ip_pool.ip_address_id=IP_Addresses.id where IP_Addresses.id is NULL;
+----+---------------+------+
| id | ip_address_id | id   |
+----+---------------+------+
|  1 |             5 | NULL |
|  1 |             6 | NULL |
|  1 |             7 | NULL |
|  1 |            30 | NULL |
|  1 |            31 | NULL |
|  1 |            33 | NULL |
|  1 |            34 | NULL |
+----+---------------+------+


Step 2:
Remove orphan entries using a query similar to the query below:
mysql> delete from ip_pool where ip_address_id in (5,6,7,30,31,33,34);

a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF