I setup my own EC2 instance now with the same data and Fuseki version.
the only difference I did is to use OpenJDK 11 from the OS repository -
I'll keep it running and see if and when it crashes.
By the way, you can also start the fuseki-server with --loc param such
that you wouldn't need an assembler file (just for simplicity).
On 24.10.22 10:22, Lorenz Buehmann wrote:
Hi,
I'm pretty sure this was just OOM killed. Default Fuseki settings are
nowadays 4GB unless you overwrite the JVM_ARGS environment variable [1]
Indeed, you could also check the OS logs to find the reason for
killing the process but I would assume it's because of low memory
Cheers,
Lorenz
[1]
https://github.com/apache/jena/blob/main/jena-fuseki2/apache-jena-fuseki/fuseki-server#L105
On 23.10.22 21:36, Bob DuCharme wrote:
The good news is that I have gotten Fuseki running on a free tier AWS
EC2 instance with very little trouble and was able to use the HTML
interface and the SPARQL endpoint, as described at
https://www.bobdc.com/blog/ec2fuseki/
The bad news: it just randomly stops, even when there has been no
querying activity, typically after 30-60 minutes of being up:
17:17:50 INFO Server :: OS: Linux
5.10.144-127.601.amzn2.x86_64 amd64
17:17:50 INFO Server :: PID: 3314
17:17:51 INFO Server :: Started 2022/10/23 17:17:51 UTC
on port 3030
Killed
The instance has 1GB of memory. I had only loaded 162K of data.
Should I set JVM_ARGS different from the default?
Thanks,
Bob
