Re: [otrs] Need TicketID errors after full disk

On 05/17/2011 04:27 PM, Michiel Beijen wrote:

I'm guessing you have tickets without articles, because you're using ArticleStorageFS and the disk was full? Obviously, if the disk is full, OTRS can actually not write the tickets and not do anything remotely useful; depending on the situation you might be able to recover emails from your email server. You'll have to detect and get rid of the tickets that have issues manually (maybe by using GenericAgent). -- Mike

On Tue, May 17, 2011 at 15:14, Tiemen Ruiten wrote:

...

Hello,

The filesystem our OTRS-installation is running on filled up completely this Friday and unfortunately, since I was away for a long weekend, this was only noticed on Monday. The server had a hard reboot (argh), possibly leaving the mysql-database in an inconsistent state.

Anyway I'm now getting these errors:

[Tue May 17 12:31:19 2011][Error] [Kernel::System::User::GetUserData][150] Need User or UserID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Queue::GetStandardResponses][249] Got no StandardResponseID or QueueID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::TicketPermission][3198] Need TicketID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::TicketPermission][3198] Need TicketID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::TicketPermission][3198] Need TicketID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::TicketPermission][3198] Need TicketID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::TicketFlagGet][7530] Need TicketID! [Tue May 17 12:31:19 2011][Error][Kernel::Output::HTML::ArticleCheckPGP::new][38] Need ArticleID! [Tue May 17 12:31:19 2011][Error][Kernel::Output::HTML::ArticleCheckSMIME::new][38] Need ArticleID! [Tue May 17 12:31:19 2011][Error][Kernel::System::Ticket::Article::ArticleGet][1644] No such article for TicketID (69632)!

Can someone give me some pointers on what the best course of action might be?

Tiemen

All the accounts are retrieved with POP so the emails were unfortunately lost. We created a mysql query to destroy all problem tickets and that seems to have restored database consistency. We're using ArticleStorageDB by the way.