Open korau opened 3 years ago
Hi,
I believe this can happen due to the following reasons.
The server IP address specified in "config.ncconf" file or in "add key="NCacheServer.BindToIP" value=""" tag inside "Alachisoft.NCache.Service.exe.config" file is not correct. This can happen when you have multiple IP addresses configured or IP has been changed on machine. The "config.ncconf" file got corrupted when it was being modified.
Please share the following details with us so that we can analyze this on our end.
The "config.ncconf" file from the server where you're facing this issue. Execute the cmdlet "ipconfig" using command prompt and share the complete output with us.
You can also start with a clean install and verify that the current IP address of the machine is correctly propagated in both files ("Alachisoft.NCache.Service.exe.config" and "config.ncconf") and that should help fix the issue.
Please provide the feedback on this and we'll take it from there.
Took some time to come back around to this. I can confirm the IP addresses inside the Alachisoft.NCache.Service.exe.config file and the config.ncconf.
Both servers .67 and .191 are having this problem. In both instances there is only a single IP bound the NICs on these machines.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration>
<cache-config cache-name="testcache" inproc="False" last-modified="">
<cache-settings>
<cache-topology topology="replicated">
<storage type="heap" cache-size="28672mb"/>
<cleanup interval="15sec"/>
<eviction-policy enabled-eviction="False" default-priority="normal" eviction-ratio="5%"/>
<performance-counters enable-counters="True" snmp-port="0"/>
<logging enable-logs="True" trace-errors="True" trace-notices="False" trace-debug="False" log-path=""/>
<cluster-settings operation-timeout="60sec" stats-repl-interval="60sec" use-heart-beat="False">
<data-replication synchronous="True"/>
<cluster-connection-settings cluster-port="8710" port-range="1" connection-retries="2" connection-retry-interval="2secs" operation-timeout="60sec" stats-repl-interval="1sec"/>
</cluster-settings>
</cache-topology>
<client-death-detection enable="False" grace-interval="60sec"/>
</cache-settings>
<cache-deployment deployment-version="0">
<servers>
<server-node ip="XXX.XXX.XXX.67"/>
<server-node ip="XXX.XXX.XXX.191"/>
</servers>
</cache-deployment>
</cache-config>
</configuration>
I have resolved the issue, the solution in this case was to do a clean install on another host and used the config ID generated for the out of the box replicated cache.
Is there any way to properly generate these id's in OSS? The additional cache guide in the OSS documentation still doesn't mention this requirement or a method to generate.
As previously referenced in https://github.com/Alachisoft/NCache/issues/51 new installs of 5.0 FP3 OSS do not appear to be able to start any newly created cache's outside of the out of the box examples provisioned on install.
When attempting to start the cache a Specified cacheId is not registered exception is generated.
Then inclusion of a configID as was previous noted in 51 does not appear to resolve this issue.