Open hpadhuka opened 9 years ago
This is not necessarily a problem from LiveMirror but nevertheless, I tried to explicitly declare any I/O input for proper file descriptor release just tin case.
If the commit doesn't not fix the problem, maybe there is another process in the system that allocates files beyond the ulimit
limit. In any case it might be good to restart in order to release any files already open.
I encountered the same problem of too many open file handles.
File limit settings
-bash-4.1$ ulimit unlimited -bash-4.1$ cat /proc/sys/fs/file-max 13130532 -bash-4.1$ lsof | wc -l 2717
-bash-4.1$ [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default-cli) on project live-mirror: An exception occured while executing the Java class. null: InvocationTargetException: File ./lastPublishedFile.txt not fount! ./lastPublishedFile.txt (Too many open files) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Lately, the liveSyn.sh is failing with [INFO LiveSync] Up-to-date with last published changeset, sleeping for a while ;) -bash-4.1$ [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.2:java (default-cli) on project live-mirror: An exception occured while executing the Java class. null: InvocationTargetException: File ./lastPublishedFile.txt not fount! ./lastPublishedFile.txt (Too many open files) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Any idea what might be wrong ?
Thx, Hari