Seahub does not kill all instances after ./seahub.sh stop without sudo

Seafile Server
1

Hi

This is new to me.
Usually I could start and stop seafile and seahub with my normal user ( no “sudo”).

Now to stop seahub I have to use sudo.

It’s not the end of the world but still not convenient.

Could someone imagine what the reason for this is?

ck@mx:~/seafile/seafile-server-latest$ ./seafile.sh stop

Stopping seafile server ...
Done.
ck@mx:~/seafile/seafile-server-latest$ ./seahub.sh stop

Stopping seahub ...
pkill: killing pid 8109 failed: Operation not permitted
pkill: killing pid 8247 failed: Operation not permitted
pkill: killing pid 8248 failed: Operation not permitted
pkill: killing pid 8249 failed: Operation not permitted
pkill: killing pid 8250 failed: Operation not permitted
pkill: killing pid 8251 failed: Operation not permitted
Failed to stop seahub.
  • And with sudo it works:
ck@mx:~/seafile/seafile-server-latest$ sudo ./seahub.sh stop
[sudo] password for ck: 
Sorry, try again.
[sudo] password for ck: 

Stopping seahub ...
Done.
2

Mybe seahub was running as root user?

3

Thanks and hmmm

I at least did not start it as root.

The systemd start file uses the normal user (as per Seafile manual).

Would you know how I can check if it runs as root?

4

ps aux | grep seafile
or
ps aux | grep seahub

dont know the exact process name atm

5

Is this related to your other post? If yes, can you also close it?

6

I don’t know if this is realted to my other post.
That’s why it’s two different posts.

If it is, I will mark it, no worries.