seaf-fuse is already running, pid nnnnnnn

[gnr8shn]

Following FUSE in Docker deployment. Receive seaf-fuse is already running as shown below.

root@aadcb1a183ba:/opt/seafile/seafile-server-latest# ./seaf-fuse.sh start /seafile-fuse

seaf-fuse is already running, pid 118958
118962

root@aadcb1a183ba:/opt/seafile/seafile-server-latest# 

Within the /optseafile/seafile-server-latest/seaf-fuse.sh script the function validate_already_running checks for seaf-fuse. This is too broad, it captures the script name before the binary seaf_fuse is run. I suggest the following:

function validate_already_running () {
    # if pid=$(pgrep -f "seaf-fuse" 2>/dev/null); then
    if pid=$(pgrep -f "fuse.log" 2>/dev/null); then
        echo "seaf-fuse is already running, pid $pid"
        echo
        exit 1;
    fi
}

Raspberry Pi 5, Debian 12 (bookworm). arm64. Using seafileltd/seafile-mc:12.0-latest, mariadb:10.11, memcached:1.6.29

[freeplant]

It is a known issue. We will fix it soon.