-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibilities with MySQL 8 #15
Comments
I am also interested in this script. With zabbix 5.4 it is more changes necessary.
is it possible to update script? |
I don't know how to do this 🙁
I find some time ago this script because have had some problems with my zabbix installation ...
[cid:5e501f69-59b1-46a3-839b-40d5b7db8965]
Francisco Jose Tudel Escalona
Departamento de Sistemas
Telf. 968 321 073 / 656 386 544
www.overtel.com<http://www.overtel.com/>
HORARIO 1-JULIO A 31-AGOSTO: 8:00-15:00
…________________________________
De: Maryna Khvastova ***@***.***>
Enviado: jueves, 15 de julio de 2021 10:22
Para: mattiasgeniar/zabbix-orphaned-data-cleanup ***@***.***>
Cc: Francisco Tudel Escalona ***@***.***>; Author ***@***.***>
Asunto: Re: [mattiasgeniar/zabbix-orphaned-data-cleanup] Incompatibilities with MySQL 8 (#15)
I am also interested in this script. With zabbix 5.4 it is more changes necessary.
Count the amount of rows that would be deleted for orphaned alerts entries Table: alerts orphaned actions: 0 Table: alerts orphaned events: 0 Table: alerts orphaned users: 0 Table: alerts orphaned media_types: 0 Count the amount of rows that would be deleted for orphaned application entries that no longer map back to a host Table: applications orphaned hosts: ERROR 1146 (42S02) at line 1: Table 'zabbix.applications' doesn't exist Count the amount of rows that would be deleted for orphaned auditlog details (such as logins) Table: auditlog_details orphaned audits: 0 Table: auditlog orphaned users: 0 Count the amount of rows that would be deleted for orphaned conditions Table: conditions orphaned actions: 0 Count the amount of rows that would be deleted for orphaned functions Table: functions orphaned items: 0 Table: functions orphaned triggers: 0 Count the amount of rows that would be deleted for orphaned graph items Table: graphs_items orphaned graphs: 0 Table: graphs_items orphaned items: 0 Count the amount of rows that would be deleted for orphaned host macro's Table: hostmacro orphaned hosts: 0 Count the amount of rows that would be deleted for orphaned item data Table: items orphaned hosts: 0 Table: items_applications orphaned applications: ERROR 1146 (42S02) at line 1: Table 'zabbix.items_applications' doesn't exist Table: items_applications orphaned items: ERROR 1146 (42S02) at line 1: Table 'zabbix.items_applications' doesn't exist Count the amount of rows that would be deleted for orphaned HTTP check data Table: httpstep orphaned httptests: 0 Table: httpstepitem orphaned httpsteps: 0 Table: httpstepitem orphaned items: 0 Table: httptest orphaned applications: ERROR 1146 (42S02) at line 1: Table 'zabbix.applications' doesn't exist Count the amount of rows that would be deleted for orphaned maintenance data Table: maintenances_groups orphaned maintenances: 0 Table: maintenances_groups orphaned groups: ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups)' at line 1 Table: maintenances_hosts orphaned maintenances: 0 Table: maintenances_hosts orphaned hosts: 0 Table: maintenances_windows orphaned maintenances: 0 Table: maintenances_windows orphaned timeperiods: 0 Count the amount of rows that would be deleted for orphaned mappings Table: mappings orphaned valuemaps: ERROR 1146 (42S02) at line 1: Table 'zabbix.mappings' doesn't exist Count the amount of rows that would be deleted for orphaned media items Table: media orphaned users: 0 Table: media orphaned media_types: 0 Table: rights orphaned user groups: 0 Table: rights orphaned groups: ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups)' at line 1 Table: sessions orphaned users: 0 Count the amount of rows that would be deleted for orphaned screens Table: screens_items orphaned screens: ERROR 1146 (42S02) at line 1: Table 'zabbix.screens_items' doesn't exist Count the amount of rows that would be deleted for orphaned events & triggers Table: trigger_depends orphaned triggers(triggerid_down): 0 Table: trigger_depends orphaned triggers(triggerid_up): 0 Count the amount of records in the history/trends table for items that no longer exist Table: history orphaned items: 0 Table: history_uint orphaned items: 0 Table: history_log orphaned items: 0 Table: history_str orphaned items: 0 Table: history_text orphaned items: 0 Table: trends orphaned items: 55 Table: trends_uint orphaned items: 168 Count the amount of records in the events table for triggers/items that no longer exist Table: events orphaned triggers(src=0, obj=0): 7 Table: events orphaned triggers(src=3, obj=0): 0 Table: events orphaned items(src=3, obj=4): 0 Count the amount of acknowledges in the acknowledges table for events which would be deleted previously Table: acknowledges orphaned events: 0 Table: acknowledges orphaned users: 0 Table: acknowledges orphaned events(src=0|3): 0 Table: acknowledges orphaned events(src=3, obj=4): 0
is it possible to update script?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#15 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARU7NOJSBJXVWDNR6MGZR7LTX2LFHANCNFSM4TZX2HFQ>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From: https://www.zabbix.com/forum/zabbix-help/374145-is-table-groups-on-mysql-missing-after-update-3-2-11-to-4-0-4
table groups does not exist anymore, changed the name to hstgrp.
Can you please update script :-)
Those tables were renamed to make it compatible with MySQL 8 since those words are reserved in new release of MySQL
The text was updated successfully, but these errors were encountered: