[systemd-devel] Failed to open system journal: Invalid argument

[Kay One]

Hi Lennart,

Thanks for the reply.
JFFS2 is the file system being used in my case. Also, if I would delete
/var/log/journal directory then these errors are stopping.
Meaning while writing to persistence storage this error is persisting all
the time.

cat /proc/cmdline
console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2

df -Tk
Filesystem           Type       1K-blocks      Used Available Use% Mounted
on
/dev/root            *jffs2*          81792     61220     20572  75% /
devtmpfs             devtmpfs      506040         4    506036   0% /dev
tmpfs                tmpfs         514744         4    514740   0% /dev/shm
tmpfs                tmpfs         514744     13268    501476   3% /run
tmpfs                tmpfs         514744         0    514744   0%
/sys/fs/cgroup
tmpfs                tmpfs         514744         0    514744   0% /tmp
/dev/mtdblock1       *jffs2*          20416      6784     13632  33%
/home/root/apps
tmpfs                tmpfs         102948         0    102948   0%
/run/user/0

Suspicious cause for this error:
------------------------------------------


mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 28, 0) = -1 EINVAL
(Invalid argument)



STRACE Detailed DUMP:
===================
Please find the attachment (strace.log)

*************************************************
root at arria10:~# cat /var/log/messages | tail -f
May 21 11:03:31 arria10 syslog.warn kernel: [  981.997820]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:03:31 arria10 syslog.warn kernel: [  982.348838]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:21 arria10 syslog.warn kernel: [ 1031.993905]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:21 arria10 syslog.warn kernel: [ 1032.001617]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:21 arria10 syslog.warn kernel: [ 1032.011077]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:21 arria10 syslog.warn kernel: [ 1032.019424]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:31 arria10 syslog.warn kernel: [ 1041.993815]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:31 arria10 syslog.warn kernel: [ 1042.001527]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:31 arria10 syslog.warn kernel: [ 1042.010622]
systemd-journald[748]: Failed to open system journal: Invalid argument
May 21 11:04:31 arria10 syslog.warn kernel: [ 1042.018886]
systemd-journald[748]: Failed to open system journal: Invalid argument

Regards,
Karnik Jain

On Mon, May 20, 2019 at 3:10 PM Lennart Poettering <lennart at poettering.net>
wrote:

> On Sa, 18.05.19 09:59, Kay One (kayone007 at gmail.com) wrote:
>
> > *[ 2002.668599] systemd-journald[743]: Journal effective settings
> seal=yes
> > compress=yes compress_threshold_bytes=512B*
> > *[ 2002.679080] systemd-journald[743]: Failed to open system journal:
> > Invalid argument*
>
> Hmm, this is interesting. I wonder how that happens. Does stracing the
> journald show anything interesting? i.e. some syscall throwing EINVAL?
>
> What's the file system used?
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20190521/261695af/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: strace.log
Type: application/octet-stream
Size: 478052 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20190521/261695af/attachment-0001.obj>