Arch Linux

skoczo

Member

Registered: 2012-09-12

Posts: 55

e4rat, no log file and can't kill

Hi,

I installed e4rat but is don't work. No log file is created after boot.
In dmesg i found:

[skoczo@pc84 etc]$ dmesg | grep e4rat
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw libahci.ignore_sss=1 init=/sbin/e4rat-collect rw
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw libahci.ignore_sss=1 init=/sbin/e4rat-collect rw
[   93.482601] e4rat-collect[902]: segfault at 0 ip 00007f195a5b3d0a sp 00007fff00f54ab8 error 4 in libc-2.19.so[7f195a531000+1a4000]

sudo e4rat-collect -k

Cannot read pid from file /dev/.e4rat-collect.pid: No such file or directory Cannot dump log messages: /dev/kmsg: Bad file descriptor Discard 1 unwritten log message(s). 

/etc/e4rat.conf

;
; Configuration file for e4rat (reduce access time for ext4 filesystems)
; if option is not specified. e4rat will use default values.
;
; e4rat has a simple logging structure. Each event has a priority bit. The
; following priorities exist
;       1   errors
;       2   warnings
;       4   task statistics
;       8   information about a single step
;      16   debug message

; Specify default verbosity level (DEFAULT: 7)
verbose 31 

; Specify bit mask of log events written to disk (DEFAULT: 3)
loglevel  3

; collect only files which device type is ext4 (DEFAULT: true)
; ext4_only  true

; ignore already open files (DEFAULT: true)
; exclude_open_files  true

; timeout after collector will stop when started as init process (DEFAULT: 120)
timeout  120

; path to init process binary (DEFAULT: /sbin/init)
init /sbin/init

; Set target path log events should written to.
; If log_target is set so 'syslog' messages are send to syslogd.
; Default value is /dev/kmsg. It sends the messages to kernel's log ring buffer. (See also dmesg(1))
; log_target /dev/kmsg

; default rearrangement mode for e4rat-realloc (DEFAULT: auto)
defrag_mode auto

; default path to startup log file (DEFAULT: /var/lib/e4rat/startup.log)
startup_log_file /etc/e4rat_startup.log

/etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="libahci.ignore_sss=1 init=/sbin/e4rat-collect rw"

Can you help?

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: e4rat, no log file and can't kill

Try https://wiki.archlinux.org/index.php/E4 … ot_created

skoczo

Member

Registered: 2012-09-12

Posts: 55

Re: e4rat, no log file and can't kill

Try https://wiki.archlinux.org/index.php/E4 … ot_created

I just tried this but with no results

skoczo

Member

Registered: 2012-09-12

Posts: 55

Re: e4rat, no log file and can't kill

I tried to switch to e4rat-lite but still no startup.log file

[skoczo@localhost bin]$ sudo /bin/e4rat-lite-collect -k
Cannot read pid from file /dev/.e4rat-lite-collect.pid: No such file or directory
Cannot dump log messages: /dev/kmsg: Bad file descriptor
Discard 1 unwritten log message(s).
[skoczo@localhost bin]$ /bin/e4rat-lite-collect -k
Cannot read pid from file /dev/.e4rat-lite-collect.pid: No such file or directory
Cannot dump log messages: /dev/kmsg: Permission denied
Discard 1 unwritten log message(s).
[skoczo@localhost bin]$ ps aux | grep e4rat
root         1  0.0  0.1  25920  4576 ?        Ss   16:52   0:01 /bin/e4rat-lite-collect
skoczo    1210  0.0  0.0   9468  1616 pts/0    S+   17:29   0:00 grep e4rat
[skoczo@localhost bin]$ dmesg | grep e4rat
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/bin/e4rat-lite-collect rootfstype=ext4 libahci.ignore_sss=1
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/bin/e4rat-lite-collect rootfstype=ext4 libahci.ignore_sss=1
[skoczo@localhost bin]$ 

Can you help?

Edit:

ls -l /var/log/ | grep e4rat -rwxrwxrwx  1 root root                 0 Jul  2 16:22 e4rat-startup.log

/etc/e4rat-lite.conf

; e4rat-lite configuration file

[Global]

; Path to the main initialization process
init_file=/usr/lib/systemd/systemd

; Default location of the boot log
startup_log_file=/var/log/e4rat-startup.log

; ------------------

[Collect]

; Collect only files on ext4 devices [true/false]
ext4_only=true

; Ignore opened files (running processes) [true/false]
exclude_open_files=true

; Time (in seconds) to wait before finalizing the collection
timeout=120

; ------------------

[Realloc]

; Defragmentation method [auto/pa/tld/locality_group]
defrag_mode=auto

Last edited by skoczo (2014-07-02 16:46:02)

skoczo

Member

Registered: 2012-09-12

Posts: 55

Re: e4rat, no log file and can't kill

I see thar e4rat shows some info before system boot but it is too fast to read that.
How can i get this info?

journalctl -b | grep e4rat

lip 08 18:35:39 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/sbin/e4rat-collect rootfstype=ext4 libahci.ignore_sss=1
lip 08 18:35:39 localhost kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/sbin/e4rat-collect rootfstype=ext4 libahci.ignore_sss=1
lip 08 18:35:47 localhost gdm-Xorg-:0[480]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/sbin/e4rat-collect rootfstype=ext4 libahci.ignore_sss=1

dmesg | grep e4rat

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/sbin/e4rat-collect rootfstype=ext4 libahci.ignore_sss=1
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8086134b-1cfa-430b-9ea9-a9af02c5a076 rw init=/sbin/e4rat-collect rootfstype=ext4 libahci.ignore_sss=1

Shows nothing interesting
How to get these logs?

SpyChicken

Member

Registered: 2013-01-27

Posts: 11

Re: e4rat, no log file and can't kill

I had the same problem, but I was able to solve it by compiling a kernel with CONFIG_AUDIT and CONFIG_AUDITSYSCALL

dunkles

Member

From: Chile

Registered: 2010-04-26

Posts: 67

Re: e4rat, no log file and can't kill

same problem here