Closed PDiracDelta closed 2 years ago
I've managed to work around this by temporarily changing permissions on the socket file:
chmod 777 runtime/seafile.sock
The file normally has 700 permissions (changed it back after I created an admin user) and was owned by the seafile
user. Therefore I could not successfully execute reset-admin.sh
as pi nor as root. I suspect this is also why the install script didn't create an admin user. This should probably be fixed?
You should run all seafile scripts with the seafile user. This: sudo -u seafile bash seafile.sh
should work for you but I cannot really test it as I found out about this issue because seafile.sh does not create runtime/seafile.sock
on my machine.
You should close this issue, your had a permission problem but running the scripts as seafile will solve it.
You should run all seafile scripts with the seafile user. This:
sudo -u seafile bash seafile.sh
should work for you but I cannot really test it as I found out about this issue because seafile.sh does not createruntime/seafile.sock
on my machine.You should close this issue, your had a permission problem but running the scripts as seafile will solve it.
Thanks for the suggestion! I have a working system atm and don't have free time to verify this right now; but I'm happy to close it if an additional person can confirm after testing. Or a seafile developer.
I made an update from 8.0.7 to 9.0.2 and have the same issue but neither suggestion worked (my system does not have runtime/seafile.sock either)
@Xalendis at least one suggestion from many worked ;-) Closing.
Fresh 8.0.0 build and install on RPI2B with RPI OS. Starting seafile and seahub works fine, but:
seafile
user via systemd service, but withsudo ./seahub start
) it saysWhat can I do to fix these issues? EDIT: interestingly, I get exactly the same error when I try to run
sudo ./reset-admin.sh
.