Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not start-up the docker with the access-address, version 3.5.4 #5

Closed
onokonem opened this issue Apr 4, 2015 · 10 comments
Closed

Comments

@onokonem
Copy link

onokonem commented Apr 4, 2015

Hi

this is exactly the same as #1 , but with different aerospike version

Apr 04 2015 23:50:41 GMT: CRITICAL (info): (thr_info.c:info_interfaces_static_fn:5074) external address:10.243.40.132 is not matching with any of service addresses:172.17.0.6:3000

any suggestions?

Thank you

@mtendjou
Copy link
Member

mtendjou commented Apr 5, 2015

As of version 3.3.26, you can solve this by adding the keyword 'virtual' after the access-address, if the access-address is not matching any physical address, for example:

service {
                address any
                port 3000

                access-address 10.243.40.132 virtual
        }

@onokonem
Copy link
Author

no, the virtual keyword does not work for me

@mtendjou
Copy link
Member

Which version are you using?

@onokonem
Copy link
Author

3.5.4

@mtendjou
Copy link
Member

Could you paste your configuration file? (you can mask IP addresses or anything that may be sensitive, just want to double check if everything is correct).

@mtendjou
Copy link
Member

Thanks for the input.

network {
  service {
    port 3000
    access-address <%=os.getenv("NODE_EXT_ADDR")%> virtual
  }

  fabric {
    port 3001
    access-address <%=os.getenv("NODE_INT_ADDR")%> virtual
  }

I am pretty sure that access-address in the fabric sub-stanza is not supported. The default there should be address any.

Also, under the service sub-stanza, you should have address any (am not sure if it will default if not specified at all like in your example). I will try to provide you with more details but this may be what's causing this error in the log (haven't got a chance to try to reproduce yet though).

@mtendjou
Copy link
Member

Any luck? We checked in the code and it really seems pretty straight forward that this error message message CRITICAL (info): (thr_info.c:info_interfaces_static_fn:5074) external address:10.243.40.132 is not matching with any of service addresses:172.17.0.6:3000 would only show up if the address really didn't match or if the virtual keyword is not added right.

Can you try by adding IP address instead of the os.getenv and removing the access address from the fabric sub-stanza?

Thanks.

@artworkad
Copy link

Just checked this with the recent version and it worked for me without a problem.

@onokonem
Copy link
Author

Great!

@volmarl volmarl closed this as completed Sep 19, 2017
mcoberly2 added a commit that referenced this issue May 21, 2021
Update Dockerfile (added back python3-pip)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants