Skip to content

Memcr corrupted execution flow #103

@adrianM27

Description

@adrianM27

Observed for version last commit dfeaa80

Memcr execution flow gets corrupted and jumps to not enabled code parts and exits:

2025-06-02T01:29:18.850Z memcr[3892]: [+] got MEMCR_CHECKPOINT for 15959.
2025-06-02T01:29:18.850Z memcr[3892]: [+] Checkpoint request scheduled...
2025-06-02T01:29:18.851Z memcr[3892]: [+] handling MEMCR_CHECKPOINT for 15959.
2025-06-02T01:29:18.851Z memcr[3892]: [+] Service waiting for worker checkpoint with timeout 20[s]...
2025-06-02T01:29:18.858Z memcr[3892]: [16215] memcr worker is started to checkpoint 15959.
2025-06-02T01:29:18.859Z memcr[3892]: [+] seizing target pid 15959
2025-06-02T01:29:18.859Z memcr[3892]: [i] 1 thread
2025-06-02T01:29:18.859Z memcr[3892]: [+] blocking signals
2025-06-02T01:29:18.859Z memcr[3892]: [+] restore crc:
2025-06-02T01:29:18.864Z memcr[3892]: [-] dump checksum do not match!
2025-06-02T01:29:18.864Z memcr[3892]: [16215] Restore failed! Killing the target app...

//DobbyInit terminated - pending signal is 5 sent by memcr to seize the pid
2025-06-02T01:29:18.865Z audit[15959]: ANOM_ABEND auid=4294967295 uid=30004 gid=30000 ses=4294967295 subj=dobby_default (enforce) pid=15959 comm="DobbyInit" exe="/usr/libexec/DobbyInit" sig=5 res=1

// memcr restarted
2025-06-02T01:29:19.438Z memcr[16388]: [x] Trying to configure UNIX /tmp/memcrcom socket.
2025-06-02T01:29:19.454Z memcr[16388]: [x] Waiting for a checkpoint command on a socket

Memcr runs in service mode, checksum and encryption is not enabled, compression LZ4 is enabled

memcr -d -N -l /tmp/memcrcom -f -z -t 20

Issue observed only for DobbyInit process and repeats several times in a row with the same log flow. Memcr restart helped to recover only single time. System reboot seems to recover

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions