This content has been marked as final. Show 2 replies
did you try a remote ./runcommand.sh Dgraph1 start (shut) to see how the process responds from the ITL ?
some guesses :
- any network issues (see how the dgraph responds on port 15000 (if this is the correct port) or how the EAC agent responds (8888 port)
- any Full File System ? check disk space on your MDEX
how many Dgraphs are included in your Dgraph Cluster ? 1 ? try and configure another Dgraph on another Host based on the same appconfig to check if the issue is with the index or the Dgraph
check if you need to extend the 120s startup time (but i fail to see why if there we no major changes)
hope that helps
After you issue the start command (either as part of a baseline update or with a runcommand.sh Dgraph1 start), you should see your Dgraph1.log file (in [your_app_folder]/data/dgraphs/Dgraph1/) get updated with information related to dgraph startup.
You should look there to see if your dgraph is actually starting in the 2 minute timeframe, the dgraph is up when you see the following line:
pid=[SOME_NUMBER] listening for HTTP connections on port [SOME_NUMBER] at [SOME_DATE_TIME]
If you don't see that, there is either an error starting the dgraph (you should see that in the same log file) or an error sending the command to start the dgraph (port 8888 not open, EAC Agent not running on the MDEX server, etc.).
If you do see a successful message starting the dgraph, it's likely that the EAC Central Server (i.e. likely where you ran the command) was not able to determine that the dgraph started. It usually does this by issuing an admin?op=ping to the dgraph port so it's likely that port 15000 (or whereever your dgraph is running) is blocked between those two servers.
Hopefully, that's enough for you to go on.