Mailing-List: contact issues-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Tue, 21 Nov 2017 23:59:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@geode.apache.org
Message-ID: <JIRA.13077727.1496767074000.294094.1511308740154@Atlassian.JIRA>
In-Reply-To: <JIRA.13077727.1496767074000@Atlassian.JIRA>
References: <JIRA.13077727.1496767074000@Atlassian.JIRA> <JIRA.13077727.1496767074127@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GEODE-3038) A server process shuts down quietly
 when path to cache.xml is incorrect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Nov 2017 23:59:05 -0000


    [ https://issues.apache.org/jira/browse/GEODE-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261701#comment-16261701 ] 

ASF GitHub Bot commented on GEODE-3038:
---------------------------------------

agingade commented on issue #677: GEODE-3038: A server process shuts down quietly when path to cache.xml is incorrect
URL: https://github.com/apache/geode/pull/677#issuecomment-346200020
 
 
   @anton-mironenko Thanks for submitting the patch.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> A server process shuts down quietly when path to cache.xml is incorrect
> -----------------------------------------------------------------------
>
>                 Key: GEODE-3038
>                 URL: https://issues.apache.org/jira/browse/GEODE-3038
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Anton Mironenko
>            Priority: Minor
>
> Geode version: 1.1.1, 1.3.0 (latest develop snapshot)
> If I start a server with incorrect path to Server.xml, it shuts down quietly without any message in the log. 
> An expected behavior would be the error message "Server.xml not found in the path [...], shutting down"
> Here are the steps to reproduce, please use GEODE-3003 for zip files.
> Test preparation:
> ---------------------
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to the values of your host1 and host2
> 4) do the bullets 1)-4) for host2, the folder where you unzip the file should be the same as on the first host
> Test running:
> ---------------
> 0) change start-server.sh so that the path to Server.xml is wrong
> cache-xml-file=$SERVERXML_DIR/Server.xml
> ->
> cache-xml-file=$SERVERXML_DIR/Server_.xml
> 1) run ./start-locator.sh on host1
> 2) after some pause run ./start-server
> 3) observe the server started and immediately stopped,
> 4) observe in the server logs, server1/cacheserver.log:
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] Received cluster configuration from the locator
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] 
>   ***************************************************************
>   Configuration for  'cluster'
>   
>   Jar files to deployed
> [info 2017/06/06 18:32:05.141 MSK host1-server-1 <main> tid=0x1] Requesting cluster configuration
> [info 2017/06/06 18:32:05.143 MSK host1-server-1 <main> tid=0x1] Got response with jars: 
> [info 2017/06/06 18:32:05.209 MSK host1-server-1 <main> tid=0x1] Initializing region _monitoringRegion_10.50.3.38<v1>1025
> [info 2017/06/06 18:32:05.222 MSK host1-server-1 <main> tid=0x1] Region _monitoringRegion_10.50.3.38<v1>1025 requesting initial image from 10.50.3.38(host1-locator-0-20236:27511:locator)<ec><v0>:1024
> [info 2017/06/06 18:32:05.227 MSK host1-server-1 <main> tid=0x1] _monitoringRegion_10.50.3.38<v1>1025 is done getting image from 10.50.3.38(host1-locator-0-20236:27511:locator)<ec><v0>:1024. isDeltaGII is false
> [info 2017/06/06 18:32:05.228 MSK host1-server-1 <main> tid=0x1] Initialization of region _monitoringRegion_10.50.3.38<v1>1025 completed
> [info 2017/06/06 18:32:05.812 MSK host1-server-1 <main> tid=0x1] GemFireCache[id = 2117642238; isClosing = true; isShutDownAll = false; created = Tue Jun 06 18:32:05 MSK 2017; server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing.
> [info 2017/06/06 18:32:05.855 MSK host1-server-1 <main> tid=0x1] Shutting down DistributionManager 10.50.3.38(host1-server-1:27773)<v1>:1025. 
> [info 2017/06/06 18:32:05.961 MSK host1-server-1 <main> tid=0x1] Now closing distribution for 10.50.3.38(host1-server-1:27773)<v1>:1025
> [info 2017/06/06 18:32:05.962 MSK host1-server-1 <main> tid=0x1] Stopping membership services
> [info 2017/06/06 18:32:05.964 MSK host1-server-1 <Geode Failure Detection Server thread 0> tid=0x1d] GMSHealthMonitor server thread exiting
> [info 2017/06/06 18:32:05.964 MSK host1-server-1 <main> tid=0x1] GMSHealthMonitor server socket is closed in stopServices().
> [info 2017/06/06 18:32:05.968 MSK host1-server-1 <main> tid=0x1] GMSHealthMonitor serverSocketExecutor is terminated
> [info 2017/06/06 18:32:05.974 MSK host1-server-1 <main> tid=0x1] DistributionManager stopped in 119ms.
> [info 2017/06/06 18:32:05.974 MSK host1-server-1 <main> tid=0x1] Marking DistributionManager 10.50.3.38(host1-server-1:27773)<v1>:1025 as closed.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)