Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server replied: Internal Server Error (Could not rename part file to final file) #9091

Closed
killmasta93 opened this issue Apr 5, 2018 · 4 comments

Comments

@killmasta93
Copy link

Hi,
I was wondering if someone else has had the same issue?
Currently have Nextcloud 12.03 with NGINX. Recently using the windows application to sync my files. I had to add

``'filelocking.enabled' => false,

but now if i work on a document then save it im getting constant

          `` server replied: Internal Server Error (Could not rename part file to final file)

Thank you

@MorrisJobke
Copy link
Member

``'filelocking.enabled' => false,

Disabling this should not be done. If you run into performance issues, then use a memory cache like redis for this.

`` server replied: Internal Server Error (Could not rename part file to final file)

Then there should be some logs in the nextcloud.log file inside your data directory.

@killmasta93
Copy link
Author

killmasta93 commented Apr 5, 2018

Thanks for the reply when you say that this should not be done the file locking? As for the redis could not get a really good tutorial on configuring redis with NGINX most of them are with APACHE
I dont remember installing redis

ps ax | grep redis 6909 pts/0 S+ 0:00 grep --color=auto redis

@MorrisJobke
Copy link
Member

not get a really good tutorial on configuring redis with NGINX most of them are with APACHE
I dont remember installing redis

It's basically installing the package like apt-get install redis-server and then use the default. This should be all for the small instances.

@MorrisJobke
Copy link
Member

For setup questions please go to the forums: https://help.nextcloud.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants