I didn’t move anything. I’m doing everything with manual and don’t make any ‘my’ moves.
But first of all, I have problem with first command.
ccnet-server -c conf -f -
It threw ‘failed to start ccnet session’ error.
And second command.
I made your command ‘touch’ and still it isn’t working. I’m attaching prt scr with errors.
You are starting ccnet-server from the tests folder and specifying it to use the conf folder under that folder. However, it is reporting that it cannot load ccnet.conf from that folder, /home/artur/dev/seafile-server/tests/conf/ccnet.conf.
First, verify that the file exists in that folder.
Then, you are creating a folder called seafile-data under the conf folder and then trying to find seafile.conf there, which certainly won’t exist.
The seafile.conf and ccnet.conf files will be located in /conf under whatever folder you originally installed seafile in on install. In your case, it appears to be /home/artur/dev/seafile-server.
So, your conf folder is probably /home/artur/dev/seafile-server/conf, which is different, not only from where you try starting ccnet, but also from you are telling ccnet that it is located.
Where did the folder “tests” come from?
Which manual are you referencing, btw? Which section?
Ok… I just read through that section of the manual. First off, there is some deprecated information in there, such as running in fastcgi mode. But, that isn’t your problem. I only mention it because there may be some other information that has changed since this section was last updated and it may be deprecated as well.
Let’s navigate to /home/artur/dev/seafile-server/tests/conf and then see if ccnet.conf exists. If so, post it here. If not, we need to figure out what went wrong.
Then, navigate to /home/artur/dev/seafile-server/tests/conf/seafile-data and check to see if seafile.conf exists. If so, post it here. If not, we need to figure out what went wrong.
Then, navigate to /home/artur/dev/seahub, and cat setenv.sh and post the results here.
Then, in the same folder, ls -al | grep setenv, and post the results here.
Also, that extra dash at the end of the ccnet-server line appears odd to me. I know it’s that way in the manual, but I’m not certain it’s correct. Another thing I noticed is the . setenv.sh… The dot looks suspicious to me as well… usually, to run a script, it’s ./setenv.sh… But, we aren’t to that point yet, so we’ll worry about that one when we get to it.