[Article] KDE 4.2 Review From Inside Out. Part 2: Applications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday 24 January 2009 10:51:47 Anne Wilson wrote:
> I'm not sure what's going on here. ?I see that sometimes, but at other
> times it moves on just as quickly as it ever did. ?So far I haven't noticed
> any pattern to the behaviour.

For me, it's every time - first it says it's processing messages, then threads, 
then groups. Once the numbers count down, the message I'm trying to read 
appears. I went into System Settings/Akonadi Configuration and clicked on the 
'Test' button and I got a list that contained some errors - one said 'My 
Sequel Server Log Contains Errors'; If I clicked on the error this appeared: 
"The MySQL server error log file 
'/home/cj/.local/share/akonadi/db_data/mysql.err' contains errors." 
and opening that, I found a great list, which in part contained the following:
******************************************************
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
090118 22:34:47  InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
090118 22:34:47  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-
codes.html
InnoDB: Could not open or create data files.
InnoDB: If you tried to add new data files, and it failed here,
InnoDB: you should now edit innodb_data_file_path in my.cnf back
InnoDB: to what it was, and remove the new ibdata files InnoDB created
InnoDB: in this failed attempt. InnoDB only wrote those files full of
InnoDB: zeros, but did not yet use them in any way. But be careful: do not
InnoDB: remove old data files which contain your precious data!
090118 22:34:47 [ERROR] Default storage engine (InnoDB) is not available
090118 22:34:47 [ERROR] Aborting

090118 22:34:47 [Note] /usr/libexec/mysqld: Shutdown complete
********************************************************
These are dated several days back, so I don't know if they're relevant to my 
issue, but, does anyone know what they mean? 

-- 
Claude Jones
Brunswick, MD



[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux