In Zabbix 2.0.10, we have observed multiple Zabbix sessions for the same user lingering in the session table indefinitely even after a user.logout is issued for them.

For instance, we confirmed that we issued a logout with the following options:

{"params": {}, "jsonrpc": "2.0", "method": "user.logout", "auth": "6fd1b68662e4226acd0105f1b4cbf9bc", "id": 2}

However, session 6fd1b68662e4226acd0105f1b4cbf9bc was left in the zabbix.sessions table with a status of 0 indefinitely, among thousands of other sessions with status 0 for the same user. It would only be removed in a year by a housekeeping run cleaning up sessions based on timestamp.

Not all sessions lingered in the table after a logout was issued for them, only some seemed to be affected.

As a result, with time we would have zabbix.sessions tables of tens of thousands of rows, all looking approximately like this:

mysql> select * from sessions;
+----------------------------------+--------+------------+--------+
| sessionid                        | userid | lastaccess | status |
+----------------------------------+--------+------------+--------+
| 000065dacb6e240b57a670a2f0a31b0c |      3 | 1422420966 |      0 |
| 000111c4bd37434fe92bcfea92449c6a |      3 | 1424293144 |      0 |
| 000269887c94a1ebf9cfc277cab539fc |      3 | 1424412775 |      0 |
| 0002b89e86fcc41a34bc94c2dbe5818b |      3 | 1424435660 |      0 |
| 00036bd4b49a8a9837d232b38b8ace43 |      3 | 1424438230 |      0 |
| 000397479b428e63db0d62908903ea8a |      3 | 1423459774 |      0 |
...