Hi
I installed Seeddms Successful, and create group ,user & folder, but when i upload a file from ADD Document or Drag & Drop i have "ERROR! An error has occurred ". Who can help me ?!
Hello!
I have SeedDMS running for years now but since yesterday it is not possible to upload anything, it is the same error message. This is why I do not want to open a new discussion.
It does not work in the Drag&Drop or in the single file upload. (The multi file Java Applet never worked)
At least for me it is some space or file count limit. Because as soon as I delete some files I can upload again. But it needs to be a software limit as there is a lot of physical storage space left:
Size Used Avail Use% Mounted on
903G 96G 762G 12% /
Is there some limit either in the database or in the software or even in the file system for a maximum number of files that can be handled? Or a maximum storage space that can be handled?
How can I troubleshoot this issue as the error message doesn't give any information and in the log of DMS there is nothing about this (only the things like user login etc.)? Is there a table in the db that I can have a look at? As the system is used for years and files are continously added I could imagine that some limits are reached (e.g. some key that is an integer). If I go to "Contents Overview" I never receive a complete list, the script runtime limit is reached before the list is rendered completly (stops at ~18k items and is not nearly the end of the folder tree).
I have now deleted some files from the DMS and it works again but I am afraid that it happens soon again.
There are limits causes by the database and the file system. The highest document id is 2^31, which isn't very easily reached. A more likely limit it the number of sub directories on your hard disk. SeedDMS puts each document into its own directory. ext3 doesn't allow more than 31998 subdirectories. If that is the limit you are facing, then consider to use ext4 instead
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems like exactly the ext3 limit is the reason: Currently - after deleting files - I have still more than 31k subfolders in my data directory. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 32K sub-directories limit is per directory not for the whole filesystem. With ext4 that is 64K. That is not a lot in todays digital documents, photos etc. Even with so many files there is a substantial delay in searching the directory. You can upgrade your ext3 system to ext4 just make sure you have a working backup. You can even change to other filesystems (ex, RiserFS) that have different limits.
I think that SeedDMS should consider a better storage scheme (may b eas an option) than the one-dir-per-document model. This model is bound to hit limits eventually in large installations with hundreds of thousands of documents.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ext4 can have more than 64k subdirs if the dir_nlink feature is turned on.
seeddms has a configuration parameter maxDirID which will force seeddms to use a two level folder hiearchy on disk for storage of documents. maxDirID holds the number of documents per directory. That would even allow to have on ext3 31998^2 documents. If you use this opition, then make sure you don't change it afterwards, otherwise seeddms will not find the documents anymore.
I usually do not recommend to set maxDirID because of the above disadvantage. I consider even 100k subdirectories not as a performance problem on ext4.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Dear Uwe Steinmann
Whats about my problem, I still have file upload problem!😞
Can you remote connect to my server ? If you can, please give me a mail to send you server information. Thank You
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have this same problem with my SeedDMS server running 5.1.16. After running 3 years today it has stopped accepting uploads until I erased some files. on its /data/104876 directory has a max inode of 65K on an ext4 partition.
Based on the comments above including an explanation from Uwe, how did you solve this problem? The discussion on this thread did not tackle any fix expecially not touching the MaxiD config option.
Any suggestions? Should I reformat partition to reiserfs with its fastest journaling plus no 64K inode limitation?
Suggestions please.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have installed SeedDms 6.0.17.1 running on Debian. It all looks fine but when we tried to upload any document at all it gives the message "ERROR! An error has occurred". We are kind of lost on this and do not know how to fix it. Can anybody please help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Uwe. Just saw your message. We now are retaking the installation and issue. Will get back to you, but may need to talk to you privately to get some assitance/consulting. Can you provide a email address to contact you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I installed Seeddms Successful, and create group ,user & folder, but when i upload a file from ADD Document or Drag & Drop i have "ERROR! An error has occurred ". Who can help me ?!
Hardware :
HP Proliant DL380p Gen8
Raid 5
32 GB Memory
OS:
CentOS 7
Thank You
Afshin Movafegh
Last edit: Afshin Movafegh 2016-08-15
Hello!
I have SeedDMS running for years now but since yesterday it is not possible to upload anything, it is the same error message. This is why I do not want to open a new discussion.
It does not work in the Drag&Drop or in the single file upload. (The multi file Java Applet never worked)
At least for me it is some space or file count limit. Because as soon as I delete some files I can upload again. But it needs to be a software limit as there is a lot of physical storage space left:
Size Used Avail Use% Mounted on
903G 96G 762G 12% /
Is there some limit either in the database or in the software or even in the file system for a maximum number of files that can be handled? Or a maximum storage space that can be handled?
How can I troubleshoot this issue as the error message doesn't give any information and in the log of DMS there is nothing about this (only the things like user login etc.)? Is there a table in the db that I can have a look at? As the system is used for years and files are continously added I could imagine that some limits are reached (e.g. some key that is an integer). If I go to "Contents Overview" I never receive a complete list, the script runtime limit is reached before the list is rendered completly (stops at ~18k items and is not nearly the end of the folder tree).
I have now deleted some files from the DMS and it works again but I am afraid that it happens soon again.
BR
There are limits causes by the database and the file system. The highest document id is 2^31, which isn't very easily reached. A more likely limit it the number of sub directories on your hard disk. SeedDMS puts each document into its own directory. ext3 doesn't allow more than 31998 subdirectories. If that is the limit you are facing, then consider to use ext4 instead
It seems like exactly the ext3 limit is the reason: Currently - after deleting files - I have still more than 31k subfolders in my data directory. Thanks!
The 32K sub-directories limit is per directory not for the whole filesystem. With ext4 that is 64K. That is not a lot in todays digital documents, photos etc. Even with so many files there is a substantial delay in searching the directory. You can upgrade your ext3 system to ext4 just make sure you have a working backup. You can even change to other filesystems (ex, RiserFS) that have different limits.
I think that SeedDMS should consider a better storage scheme (may b eas an option) than the one-dir-per-document model. This model is bound to hit limits eventually in large installations with hundreds of thousands of documents.
ext4 can have more than 64k subdirs if the dir_nlink feature is turned on.
seeddms has a configuration parameter maxDirID which will force seeddms to use a two level folder hiearchy on disk for storage of documents. maxDirID holds the number of documents per directory. That would even allow to have on ext3 31998^2 documents. If you use this opition, then make sure you don't change it afterwards, otherwise seeddms will not find the documents anymore.
I usually do not recommend to set maxDirID because of the above disadvantage. I consider even 100k subdirectories not as a performance problem on ext4.
Hello Dear Uwe Steinmann
Whats about my problem, I still have file upload problem!😞
Can you remote connect to my server ? If you can, please give me a mail to send you server information. Thank You
please contact me privately at info@seeddms.org
I have this same problem with my SeedDMS server running 5.1.16. After running 3 years today it has stopped accepting uploads until I erased some files. on its /data/104876 directory has a max inode of 65K on an ext4 partition.
Based on the comments above including an explanation from Uwe, how did you solve this problem? The discussion on this thread did not tackle any fix expecially not touching the MaxiD config option.
Any suggestions? Should I reformat partition to reiserfs with its fastest journaling plus no 64K inode limitation?
Suggestions please.
ext4 doesn't have that limit. See https://unix.stackexchange.com/questions/239146/linux-folder-size-limit/239150
We have installed SeedDms 6.0.17.1 running on Debian. It all looks fine but when we tried to upload any document at all it gives the message "ERROR! An error has occurred". We are kind of lost on this and do not know how to fix it. Can anybody please help!
This can have many reasons. Is there any error msg in your apache or php log?
Dear Uwe. Just saw your message. We now are retaking the installation and issue. Will get back to you, but may need to talk to you privately to get some assitance/consulting. Can you provide a email address to contact you?