-
Notifications
You must be signed in to change notification settings - Fork 2
Question: extractor stops outputting but doesn't quit. #8
Comments
I bumped the logback to 6 files and it seemed to run a bit further but then I removed the |
No worries. The first time I recall the 4 files were about 5.0-5.1GB each and the second time they were 5.2GB each for sure. So I would say not the same amount of output, but Is there something I can do to see what it thinks its doing when it gets like this? |
Maybe its my use of |
I would just use |
Ok I just started it again with the command
We'll see what happens. |
Sorry got busy and left this till now. Apparently it ran for 2.5 hours and then froze. The process is still there, no exception in the log...just hung. The log file
The triple directory.
All the threads appear to be sleeping in Not sure what to do next. |
This is weird. I started the tool running against my production objectStore and it was kicking along all nice and easy.
Once it had filled 5 20MB log files and 20GB of triples it just stopped outputting anything.
The process is still active (in a screened session), but it is not doing anything I can see.
Could it be that my
logback.xml
is causing this? It is weird that I set the RollingFIleAppender to<maxIndex>5</maxIndex>
and thats when the process stops.I tried deleting the log files, but that had no effect.
Thoughts?
The text was updated successfully, but these errors were encountered: