User Tools

Site Tools


Sidebar

tarantoolctl:logs

Q. What’s going on here?

2016-11-09 23:43:01.737 [2249] main/101/tarantoolctl xlog.cc:1310 E> XlogError: : failed to read log file header
2016-11-09 23:43:01.737 [2249] main/101/tarantoolctl F> can't initialize storage: : failed to read log file header
2016-11-09 23:43:01.737 [2249] main/101/tarantoolctl F> can't initialize storage: : failed to read log file header

I moved the log and the snapshot out of the way - and it came back to life. (2016)

A. Apparently, it’s the old log file format, or the log file is empty. We never create empty log files, so maybe it’s a disk or file system failure.

A new file is created as follows: we first create an .xlog.inprogress file, then we write a file header, and then we rename the file. Of course, it may happen so that the directory inode is flushed before the file inode, and then the system reboots - in this case, you can end up in a situation like this one.

The only fix would be to sync the data in the file before renaming it, but as long as we have a special sync mode, we don't sync stuff explicitly in write mode.

Comments

Enter your comment. Wiki syntax is allowed:
U P M W K
 
tarantoolctl/logs.txt · Last modified: 2018/05/25 20:35 by eabates

Real Time Web Analytics