[/map
{"- map/map "})
[/map/topicref
{"- map/topicref "}) [/map/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Dgraph Administrative Tasks (navtitle][/map/topicref/topicmeta/linktext
{"- map/linktext "}) Dgraph Administrative Tasks (linktext][/map/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) This section describes some basic administrative tasks for the Dgraph, contains Dgraph troubleshooting tips, and describes the Dgraph logs. (shortdesc] (topicmeta][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Checking the status of the Dgraph (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Checking the status of the Dgraph (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) A quick way of checking the health of a Dgraph is to get its status from the Endeca Server. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) About connecting Web browsers to the data store (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) About connecting Web browsers to the data store (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) For security reasons, you should never allow user Web browsers to connect directly to the machine hosting the Endeca Server and the Endeca data stores. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph core dump files (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph core dump files (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) In the rare case of a Dgraph crash, the Dgraph writes its core dump files on disk. (shortdesc] (topicmeta][/map/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph crash dump files on Windows (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph crash dump files on Windows (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) On Windows, all Dgraph crash dump files are saved on disk by default. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph core dump files on Linux (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph core dump files on Linux (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) It is recommended to use the ulimit -c unlimited setting for the Dgraph process core dump files. Non-limited core files contain all Dgraph data that is resident in memory (RSS of the Dgraph process). (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Collecting debugging information (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Collecting debugging information (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Before attempting to debug an issue with the data store, collect the following information. (shortdesc] (topicmeta][/map/topicref/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Logs created by the Dgraph (navtitle][/map/topicref/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Logs created by the Dgraph (linktext][/map/topicref/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) The Dgraph creates several logs, although some of these logs depend on your implementation and the components that you may be using. This topic provides a summary of these logs. (shortdesc] (topicmeta] (topicref] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Running multiple Dgraphs on the same Windows machine (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Running multiple Dgraphs on the same Windows machine (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) If you have more than one Endeca data store running on a single Windows machine, the Endeca Server, by default, assigns each Dgraph a port that does not conflict with other Dgraph ports on that machine. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Identifying connection errors (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Identifying connection errors (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) If the Dgraph standard out log contains connection broken messages, although it may look like the problem occurred with the Dgraph, the actual cause of the problem is usually a broken connection between the server that hosts the front-end application and the server that hosts the Dgraph. (shortdesc] (topicmeta] (topicref] (topicref]
[/map/reltable
{"- map/reltable "})
[/map/reltable/relheader
{"- map/relheader "}) [/map/reltable/relheader/relcolspec
{"- map/relcolspec "}) (relcolspec][/map/reltable/relheader/relcolspec
{"- map/relcolspec "}) (relcolspec]
(relheader]
[/map/reltable/relrow
{"- map/relrow "}) [/map/reltable/relrow/relcell
{"- map/relcell "})
[/map/reltable/relrow/relcell/topicref
{"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta
{"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Collecting debugging information (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext
{"- map/linktext "}) Collecting debugging information (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Before attempting to debug an issue with the data store, collect the following information. (shortdesc] (topicmeta] (topicref] (relcell][/map/reltable/relrow/relcell
{"- map/relcell "})
[/map/reltable/relrow/relcell/topicref
{"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta
{"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Logs created by the Dgraph (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext
{"- map/linktext "}) Logs created by the Dgraph (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) The Dgraph creates several logs, although some of these logs depend on your implementation and the components that you may be using. This topic provides a summary of these logs. (shortdesc] (topicmeta] (topicref] (relcell]
(relrow]
[/map/reltable/relrow
{"- map/relrow "}) [/map/reltable/relrow/relcell
{"- map/relcell "})
[/map/reltable/relrow/relcell/topicref
{"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta
{"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph core dump files (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph core dump files (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) In the rare case of a Dgraph crash, the Dgraph writes its core dump files on disk. (shortdesc] (topicmeta] (topicref] (relcell][/map/reltable/relrow/relcell
{"- map/relcell "})
[/map/reltable/relrow/relcell/topicref
{"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta
{"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph crash dump files on Windows (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph crash dump files on Windows (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) On Windows, all Dgraph crash dump files are saved on disk by default. (shortdesc] (topicmeta] (topicref]
[/map/reltable/relrow/relcell/topicref
{"- map/topicref "}) [/map/reltable/relrow/relcell/topicref/topicmeta
{"- map/topicmeta "}) [/map/reltable/relrow/relcell/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Managing Dgraph core dump files on Linux (navtitle][/map/reltable/relrow/relcell/topicref/topicmeta/linktext
{"- map/linktext "}) Managing Dgraph core dump files on Linux (linktext][/map/reltable/relrow/relcell/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) It is recommended to use the ulimit -c unlimited setting for the Dgraph process core dump files. Non-limited core files contain all Dgraph data that is resident in memory (RSS of the Dgraph process). (shortdesc] (topicmeta] (topicref] (relcell]
(relrow]
(reltable]
(map]