Error missing table SSO mappings after 2026R1.1

[xdatanet]

After upgrade I cannot login to the system with SSO.

The error was:

SQL Error [nagiosxi] : Table 'nagiosxi.xi_sso_mappings' doesn't exist

Please help us.

Regards,
Graziano.

[bbahn]

Hello @xdatanet,

Are you sure your upgrade went through properly? The upgrade process imports the sql schema in nagiosxi/nagiosxi-db/mysql/schema_80002.sql. You can import this into the nagiosxi table manually with

Code: Select all

mysql -u <root/nagiosxi> -p nagiosxi < ...../path/to/schema_80002.sql

, but I suspect that the upgrade didn't finish and thus you are likely missing some updates and you should try re-running the upgrade.

[xdatanet]

I reverted the VM and reapplied the update.

Same error.

Below the error I find launching the update manually from console.

Checked 93 hosts.
Checked 7 host groups.
Checked 0 service groups.
Checked 17 contacts.
Checked 8 contact groups.
Checked 214 commands.
Checked 37 time periods.
Checked 0 host escalations.
Checked 856 service escalations.
Checking for circular paths...
Checked 93 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 37 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 18
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
Last metadata expiration check: 1:12:33 ago on Thu 18 Dec 2025 03:51:35 PM CET.
Dependencies resolved.
Nothing to do.
Complete!
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1824 (HY000) at line 1: Failed to open the referenced table 'xi_users'
ERROR 1824 (HY000) at line 22: Failed to open the referenced table 'xi_users'
Copying over new XI directory...
SSO user metadata migration failed: SSO database tables do not exist.

NB: updated SSO to drastically improve performance for logging in and configuring users - BB
We cannot drastically access with SSO after 1.1

Regards,
Graziano.

[bbahn]

Your upgrade clearly failed given the error.

You can try importing the sql schema before upgrading to see what's going on there. What OS are you on? Have you made any modifications to the database?

[xdatanet]

CentOS 9.
My upgrade cannot fail every time I try...
I can revert the VM with a snapshot and the result is the same.
I never changed my database.
Actually, in 1.0.1 I can see the mapping table with the users correctly mapped.
But when I upgrade the table disappears...

How to check eventually the consistency of DB but now it works like a charm...

Regards,
Graziano.

[DoubleDoubleA]

Hi @xdatanet,

Sorry for the trouble there. Probably at this point I would put in a support ticket to get help with the upgrade issue, they can troubleshoot more deeply than we are going to be able to here on the forum.

Aaron

[bbahn]

@xdatanet,

If you're still encountering this issue, could you please show the results of this SQL command:

Code: Select all

SELECT ENGINE FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'nagiosxi';

This will tell us whether your tables are using the InnoDB engine, which became the default around 2010 and is required for the SSO schema to work.

I will have an update to the upgrade scripts that will migrate the tables to InnoDB to ensure this issue is fixed in the future. This should be out within the next release or two.

[op-team]

Hi,

I'm experiencing the same issue after upgrading from XI2024R2 to 2026R1.1 on REDHAT 9 -> viewtopic.php?t=76767

As suggested here, i have tried to manually apply the schema file:

Code: Select all

[root@nagios: /tmp/nagiosxi]# mysql -u nagiosxi -p nagiosxi < nagiosxi/nagiosxi-db/mods/mysql/schema_80002.sql
Enter password:
ERROR 1824 (HY000) at line 1: Failed to open the referenced table 'xi_users'

The result of the SQL command:

Code: Select all

mysql> SELECT ENGINE FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'nagiosxi';

+--------+

| ENGINE |

+--------+

| MyISAM |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| MyISAM |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| MyISAM |

| MyISAM |

| InnoDB |

| MyISAM |

| InnoDB |

| MyISAM |

| InnoDB |

| InnoDB |

| MyISAM |

| InnoDB |

| InnoDB |

| InnoDB |

| InnoDB |

| MyISAM |

| MyISAM |

| InnoDB |

+--------+

30 rows in set (0.00 sec)

Thanks in advance for your help

[bbahn]

If you update your xi_users table to InnoDB, you should be able to run the schema without issue. You can accomplish this with

Code: Select all

ALTER TABLE xi_users ENGINE = InnoDB;

Nagios XI 2026R1.1.1 will have a script that will update the table engines for the nagiosxi database and will resolve this issue.