/lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

Bug #1773148 reported by errors.ubuntu.com bug bridge on 2018-05-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Status tracked in Cosmic
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Dimitri John Ledkov 🌈 (xnox) wrote :

journald appears to sigabort upon rotating systemd journal file, in fsync... 😱

#0 0x00007f6d47f7c237 in fsync (fd=46) at ../sysdeps/unix/sysv/linux/fsync.c:27
        resultvar = 0
        sc_cancel_oldtype = 0
        sc_ret = <optimized out>
#1 0x00007f6d47abf6a0 in fsync_directory_of_file.lto_priv.56 (fd=<optimized out>) at ../src/journal/journal-file.c:483
        path = 0x55c0f3ce1540 "/var/log/journal/<valid uuid>/system@<valid uuid>-0000000000<suffix>-000<another-suffix>.journal"
        dn = 0x55c0f3cda680 "/var/log/journal/<same uuid>"
        dfd = 46
        st = {st_dev = 64768, st_ino = 29360293, st_nlink = 1, st_mode = 33184, st_uid = 0, st_gid = 101, __pad0 = 0, st_rdev = 0, st_size = 134217728, st_blksize = 4096, st_blocks = 262152, st_atim = {tv_sec = 1523965107, tv_nsec = 217770755}, st_mtim = {tv_sec = 1523965108, tv_nsec = 564627151}, st_ctim = {tv_sec = 1523965108, tv_nsec = 564627151}, __glibc_reserved = {0, 0, 0}}
        r = <optimized out>
#2 0x00007f6d47b347a7 in journal_file_rotate (f=0x7fffc919e0c0, compress=<optimized out>, seal=<optimized out>, deferred_closes=0x55c0f3cd2e00) at ../src/journal/journal-file.c:3496
        p = 0x55c0f3ce1470 "/var/log/journal/<valid uuid>/system@<valid uuid>-0000000000<suffix>-000<another-suffix>.journal"
        l = <optimized out>
        old_file = 0x55c0f3d27760
        new_file = 0x0
        r = <optimized out>
        __PRETTY_FUNCTION__ = "journal_file_rotate"
#3 0x000055c0f2c80f71 in do_rotate (s=<optimized out>, f=0x7fffc919e0c0, name=0x55c0f2c8bae7 "system", seal=<optimized out>, uid=0) at ../src/journal/journald-server.c:466
#4 0x000055c0f2c810ce in server_rotate (s=0x7fffc919e020) at ../src/journal/journald-server.c:488
#5 0x000055c0f2c8372b in write_to_journal (priority=6, n=21, iovec=0x7fffc919a880, uid=0, s=0x7fffc919e020) at ../src/journal/journald-server.c:717
#6 dispatch_message_real (s=0x7fffc919e020, iovec=0x7fffc919a880, n=21, m=<optimized out>, c=<optimized out>, tv=<optimized out>, priority=6, object_pid=0) at ../src/journal/journald-server.c:877
#7 0x000055c0f2c83a78 in server_driver_message (s=0x7fffc919e020, object_pid=<optimized out>, message_id=<optimized out>, format=<optimized out>) at ../src/journal/journald-server.c:911
#8 0x000055c0f2c88692 in dev_kmsg_record (l=163, p=<optimized out>, s=0x7fffc919e020) at ../src/journal/journald-kmsg.c:160
#9 server_read_dev_kmsg (s=<optimized out>, s=<optimized out>) at ../src/journal/journald-kmsg.c:346
#10 0x00007f6d47abb160 in source_dispatch (s=s@entry=0x55c0f3cd44d0) at ../src/libsystemd/sd-event/sd-event.c:2303
#11 0x00007f6d47abb3fa in sd_event_dispatch (e=<optimized out>, e@entry=0x55c0f3cd3f10) at ../src/libsystemd/sd-event/sd-event.c:2663
#12 0x00007f6d47abb589 in sd_event_run (e=<optimized out>, timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2723
#13 0x000055c0f2c78b16 in main (argc=<optimized out>, argv=<optimized out>) at ../src/journal/journald.c:110

Dimitri John Ledkov 🌈 (xnox) wrote :

I wonder if systemd is actually killing journald, whilst it is stuck fsyncing....

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers