Hi all
Thanks for the help, especially Mr. Gallegos by reponder so fast, I was doing this test and apparently resolved the issue, log messages returned to normal, but after running the mysqlcheck command I got another message and wanted to know how could affect me.
\MySQL\bin>mysqlcheck --repair -u root otrs -p
Enter password:
otrs.agosto OK
otrs.agosto1 OK
otrs.agosto2 OK
otrs.agosto3 OK
otrs.article OK
otrs.article_attachment OK
otrs.article_flag OK
otrs.article_plain OK
otrs.article_search OK
otrs.article_sender_type OK
otrs.article_type OK
otrs.auto_response OK
otrs.auto_response_type OK
otrs.calendar_event OK
otrs.calendar_event_involved OK
otrs.change_cab OK
otrs.change_cip_allocate OK
otrs.change_condition OK
otrs.change_freekey OK
otrs.change_freetext OK
otrs.change_history OK
otrs.change_history_type OK
otrs.change_item OK
otrs.change_notification OK
otrs.change_notification_grps OK
otrs.change_notification_rec OK
otrs.change_state_machine OK
otrs.change_template OK
otrs.change_template_type OK
otrs.change_wo_freekey OK
otrs.change_wo_freetext OK
otrs.change_workorder OK
otrs.cip_allocate OK
otrs.condition_action OK
otrs.condition_attribute OK
otrs.condition_expression OK
otrs.condition_object OK
otrs.condition_operator OK
otrs.configitem OK
otrs.configitem_counter OK
otrs.configitem_definition OK
otrs.configitem_history OK
otrs.configitem_history_type OK
otrs.configitem_version OK
otrs.customer_company OK
otrs.customer_preferences OK
otrs.customer_user OK
otrs.faq_attachment OK
otrs.faq_category OK
otrs.faq_category_group OK
otrs.faq_history OK
otrs.faq_item OK
otrs.faq_language OK
otrs.faq_log OK
otrs.faq_state OK
otrs.faq_state_type OK
otrs.faq_voting OK
otrs.follow_up_possible OK
otrs.general_catalog OK
otrs.general_catalog_preferences OK
otrs.generic_agent_jobs OK
otrs.group_customer_user OK
otrs.group_role OK
otrs.group_user OK
otrs.groups OK
otrs.imexport_format OK
otrs.imexport_mapping OK
otrs.imexport_mapping_format OK
otrs.imexport_mapping_object OK
otrs.imexport_object OK
otrs.imexport_search OK
otrs.imexport_template OK
otrs.julio OK
otrs.julio1 OK
otrs.julio2 OK
otrs.julio3 OK
otrs.junio OK
otrs.junio1 OK
otrs.junio2 OK
otrs.junio3 OK
otrs.link_object OK
otrs.link_relation OK
otrs.link_state OK
otrs.link_type OK
otrs.mail_account OK
otrs.notification_event OK
otrs.notification_event_item OK
otrs.notifications OK
otrs.package_repository OK
otrs.parent
note : The storage engine for the table doesn't support repair
otrs.personal_queues OK
otrs.postmaster_filter OK
otrs.process_id OK
otrs.queue OK
otrs.queue_auto_response OK
otrs.queue_preferences OK
otrs.queue_standard_response OK
otrs.role_user OK
otrs.roles OK
otrs.salutation OK
otrs.search_profile OK
otrs.service OK
otrs.service_customer_user OK
otrs.service_preferences OK
otrs.service_sla OK
otrs.sessions OK
otrs.setiembre OK
otrs.signature OK
otrs.sla OK
otrs.sla_preferences OK
otrs.standard_attachment OK
otrs.standard_response OK
otrs.standard_response_attachment OK
otrs.support_bench_test OK
otrs.system_address OK
otrs.theme OK
otrs.ticket OK
otrs.ticket_history OK
otrs.ticket_history_type OK
otrs.ticket_index OK
otrs.ticket_lock_index OK
otrs.ticket_lock_type OK
otrs.ticket_loop_protection OK
otrs.ticket_priority OK
otrs.ticket_state OK
otrs.ticket_state_type OK
otrs.ticket_type OK
otrs.ticket_watcher OK
otrs.time_accounting OK
otrs.user_preferences OK
otrs.users OK
otrs.valid OK
otrs.virtual_fs OK
otrs.virtual_fs_db OK
otrs.virtual_fs_preferences OK
otrs.web_upload_cache OK
otrs.xml_storage OK
\MySQL\bin>
Julio Angulo
Telf.: +51 1 4150300 anexo: 1468
Movil: +51 997066155
De: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] En nombre de Carlos Andrés Gallego Arboleda
Enviado el: Martes, 25 de Septiembre de 2012 06:13 p.m.
Para: User questions and discussions about OTRS.
Asunto: [IE]:Re: [otrs]can´t see history ticket
HI
If you database is on MySQL you can log as root and excecute this command
mysqlcheck --repair -u USER otrs -p
Use your password and wait.
2012/9/25 DM_Julio Angulo <dm_jangulo@equifax.com.pe>
hi guys, checking the log I find this message:
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:01 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
[Tue Sep 25 13:05:02 2012][Error][Kernel::System::Ticket::HistoryAdd][6265] Table '.\otrs\ticket_history' is marked as crashed and should be repaired, SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'
Now when I see the history of the ticket not displayed
I do not understand the message, any help
thanks
Julio Angulo
Telf.: +51 1 4150300 anexo: 1468
Movil: +51 997066155
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs