Can't start server (cause of linux memory monitor)


(jeong) #1

Hello.

I have a trouble to start stardog server.

This is the log.

INFO  2018-07-13 09:55:48,810 [main] com.complexible.stardog.cli.impl.ServerStart:call(235): Memory options
INFO  2018-07-13 09:55:48,810 [main] com.complexible.stardog.cli.impl.ServerStart:call(236): Memory mode: DEFAULT
INFO  2018-07-13 09:55:48,810 [main] com.complexible.stardog.cli.impl.ServerStart:call(237): Min Heap Size: 2.0G
INFO  2018-07-13 09:55:48,810 [main] com.complexible.stardog.cli.impl.ServerStart:call(238): Max Heap Size: 1.9G
INFO  2018-07-13 09:55:48,810 [main] com.complexible.stardog.cli.impl.ServerStart:call(239): Max Direct Mem: 1.0G
INFO  2018-07-13 09:55:48,811 [main] com.complexible.stardog.cli.impl.ServerStart:call(240): Max Mapped Mem: 115M
INFO  2018-07-13 09:55:48,811 [main] com.complexible.stardog.cli.impl.ServerStart:call(241): System Memory: 16G
INFO  2018-07-13 09:55:51,015 [Stardog-Linux-Memory-Monitor] com.complexible.stardog.api.LinuxMemoryMonitor:run(118): Memory monitor thread shutdown
Waiting for running tasks to complete...done. Executor service has been shut down.
Stardog server 5.3.2 shutdown on Fri Jul 13 09:55:51 KST 2018.

What should I do in this case? ??


(Pavel Klinov) #2

I don’t think the Linux Memory Monitor causes the shutdown. Can you share the exact commands or script you’re using to start Stardog?

Best,
Pavel


(system) #3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.