Skip navigation links

MySQL Forums :: memcached :: memcached error Could not connect to NDB


Advanced Search

Re: memcached error Could not connect to NDB
Posted by: deepak m ()
Date: March 20, 2012 06:27AM

hi

for the previous situation got little bit solution, but still problem is there

actually i am trying to access the memcached for NO-SQL access,
but i configured memcsached in one of the SQL node there mysqld is running..
if i am trying to run memcached its not accepting...becz memcached with nosql access will not use SQL(mysqld process)

i stopped that mysqld process and then trying run the same service again, which passes that step but in the later step its showing error

got error like


[root@cent2 ~]# /usr/local/mysql/bin/memcached -E /usr/local/mysql/lib/ndb_engine.so -e "connectstring=10.10.221.157:1186;role=db-only;debug=true" -vv -c 20 -u root -p 11211
main --> ndb_initialize()
main print_debug_startup_info(): sizeof Ndb : 144
main print_debug_startup_info(): sizeof NdbInstance : 64
main print_debug_startup_info(): sizeof workitem : 136
main print_debug_startup_info(): sizeof ExternalValue : 96
main --> connect_to_primary_cluster()
20-Mar-2012 17:18:16 IST NDB Memcache 5.5.19-ndb-7.2.4 started [NDB 7.2.4; MySQL 5.5.19]
Contacting primary management server (10.10.221.157:1186) ...
main --> ClusterConnectionPool::connect()
Connected to "10.10.221.157:1186" as node id 6.
Invalid table "ndbmemcache.meta"
Segmentation fault


later i just imported the database ndbmemcache as

/usr/local/mysql/bin/mysql -uroot -pmysql < /usr/local/mysql/share/memcache-api/ndb_memcache_metadata.sql

now i exicuted once again the previous command without debug option

[root@cent2 ~]# /usr/local/mysql/bin/memcached -E /usr/local/mysql/lib/ndb_engine.so -e "connectstring=10.10.221.157:1186;role=db-only" -vv -c 20 -u root -p 11211 20-Mar-2012 17:21:01 IST NDB Memcache 5.5.19-ndb-7.2.4 started [NDB 7.2.4; MySQL 5.5.19]
Contacting primary management server (10.10.221.157:1186) ...
Connected to "10.10.221.157:1186" as node id 6.
Retrieved 3 key prefixes for server role "db-only".
The default behavior is that:
GET uses NDB only
SET uses NDB only
DELETE uses NDB only.
The 2 explicitly defined key prefixes are "b:" (demo_table_large) and "t:" (demo_table_tabs)
open_connections_to_all_clusters() failed
Segmentation fault


it passes the connectivity phase, but still problem is there

can any one know why open_connections_to_all_clusters() is failed


thanks in advance



Edited 1 time(s). Last edit at 03/21/2012 03:21AM by deepak m.

Options: ReplyQuote


Subject Views Written By Posted
memcached error Could not connect to NDB 2520 deepak m 02/24/2012 04:15AM
Re: memcached error Could not connect to NDB 1225 john.duncan 02/24/2012 08:10AM
Re: memcached error Could not connect to NDB 1349 deepak m 02/27/2012 07:25PM
Re: memcached error Could not connect to NDB 1200 Kamil J 03/06/2012 11:52AM
Re: memcached error Could not connect to NDB 1258 deepak m 03/20/2012 03:03AM
Re: memcached error Could not connect to NDB 1657 deepak m 03/20/2012 06:27AM
Re: memcached error Could not connect to NDB 2046 deepak m 03/26/2012 01:03AM
Re: memcached error Could not connect to NDB 1201 john.duncan 03/26/2012 09:15AM
Re: memcached error Could not connect to NDB 1136 deepak m 03/27/2012 03:25AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.