Oh no, now Iām nowing it! Itās the same problem I often have with yaourt. Somewhere in the script a the command is python. On a normal server OS, e.g. Debian and CentOS, python 2.7 will appear. But on Arch python 3.6 will appear. You have to make something with the alias command and put itin your .bashrc.
We are one step closerā¦ But, if I can recall correctly, you canāt use Python arguments and script arguments at the same time from the command line. The arguments for Python have to be parsed into a file. I think itās called sys.argv, but I donāt remember right off hand.
The problem is, the process is spawning. Then, itās dying for some strange reason. At least this time, the error is different. Try to run seafdav, then check the controller log for the pid. Then, ps -auxww | grep
Example based on your last controller log you posted: ps -auxww | grep 3191
If that process is running, but the PID file canāt be found, then the problem lies with the file not being generated for some odd reason.
I think itās an typically Arch problem. I like Arch, too, but I would never use it for Server. You should change to another OS or put Seafile into a debian container.
I am having the same issue. I have also been upgrading to the latest version of Seafile and removing FCGI from my existing config, all so that I can get WebDAV to run (specifically, so I can point a number of iOS apps to use my privately hosted WebDAV rather than a public cloud service).
Reading through this thread, I was having the same issues, though I am running on Ubuntu. Having installed pip install --upgrade WsgiDAV I now have v2.3.0. I have changed the apache and seafdav.conf config files to use port 8089 as I know its not in use.
I am using the iOS Transmit app to test access to the WebDAV site. I presume I should be using the HTTPS option, host URL is my external Seafile website address and port is 443. I have tried my new 8089 port as well, which also fails.
Your problem is not the same as the original poster. He would run it and it would terminate nearly immediately after running it, and the PID would disappear from the process list. Yours appears to be running.
Are you getting errors anywhere? Are you using NGinx/Apache? What are the symptoms of your problem?
Did you change your seafdav.conf file to set fastcgi to false? What about your NGinx/Apache config? Do you see any fastcgi entries anywhere in there?
I just noticed that you are the same person from another threadā¦ lolā¦ So, I know a little more about your setup. So, we just need to find what behaviors you are getting with Seafdav.
I am using Apache. The main Seafile server is running. I can log in via the browser and Mac app, and tested uploading and moving some files, so presuming all functionality is ok.
I get āUnable to connect to the serverā error message using Documents on iOS and āCould not connect to server ā¦ā with iOS Transmit.
Iāve been following this thread since it started. Iām having the exact same problem as @paapereira
Iāve been able to replicate everything done is this thread - controller.log says it spawns a pid but nothing is logged to seafdav.log. If anyone has any suggestions, Iāll be following this thread as I need WebDav support for my phone.
Hey @bionade24
Iām running CentOS 7.4.1708.
I did read your reply above, and as it happens Iām running python 2.7.5. Unfortunately it seems to kill your CentOS py 2.7 theory