Lachim / redis

Automatically exported from code.google.com/p/redis
2 stars 0 forks source link

Unknown command error response for 'keys' command #573

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What version of Redis you are using, in what kind of Operating System?
redis 2.2.2 (CentOS 5)
redis-cli 2.2.7 (CentOS 5)

What is the problem you are experiencing?

redis-cli shown unknown command error for 'keys' command once. 
redis> del "LOCAL_adlge:122-727"
(integer) 1
redis> keys LOCAL_ad*
(error) ERR unknown command 'keys'
redis> keys
(error) ERR wrong number of arguments for 'keys' command
redis> keys LOCAL_ad*
1) "LOCAL_ad:1111"
2) "LOCAL_ad:1112"
3) "LOCAL_ad:1114"
4) "LOCAL_ad_search_buffer"

What steps will reproduce the problem?
NA

Do you have an INFO output? Please past it here.
redis_version:2.2.2
redis_git_sha1:00000000
redis_git_dirty:0
arch_bits:64
multiplexing_api:epoll
process_id:7288
uptime_in_seconds:653459
uptime_in_days:7
lru_clock:689998
used_cpu_sys:9.62
used_cpu_user:10.80
used_cpu_sys_childrens:10.50
used_cpu_user_childrens:3.94
connected_clients:1
connected_slaves:0
client_longest_output_list:0
client_biggest_input_buf:0
blocked_clients:0
used_memory:7002024
used_memory_human:6.68M
used_memory_rss:9744384
mem_fragmentation_ratio:1.39
use_tcmalloc:0
loading:0
aof_enabled:0
changes_since_last_save:92
bgsave_in_progress:0
last_save_time:1307133475
bgrewriteaof_in_progress:0
total_connections_received:9489
total_commands_processed:75999
expired_keys:2
evicted_keys:0
keyspace_hits:68053
keyspace_misses:7912
hash_max_zipmap_entries:512
hash_max_zipmap_value:64
pubsub_channels:0
pubsub_patterns:0
vm_enabled:0
role:master
allocation_stats:0=75945,2=759,6=1,8=33,9=9855,10=32480,11=16218,12=23696,13=440
76,14=22805,15=10047,16=742515,17=12224,18=134,19=37342,20=305,21=1313,22=8730,2
3=5488,24=111807,25=519,26=28030,27=13,28=40,29=15,30=877,31=55,32=34689,33=147,
34=3,35=112,36=64,37=5359,38=5035,39=714,40=76237,41=1191,42=42,43=8,44=22,45=30
191,46=26,47=1951,48=38113,49=15778,50=320,51=7,52=172,53=33180,54=2,55=99,56=39
97,57=11611,58=1,59=2,60=6949,62=2,63=37,64=2565,65=53,66=49,67=2067,68=1575,69=
1555,70=38,71=3,72=21,73=69,74=1,76=2,77=2,79=1,80=88,85=4,87=1939,88=10122,92=1
,93=3,94=18,95=35,96=91,97=14,103=1,105=1,109=11,112=9397,113=10,119=49,120=2,12
1=1,122=18,123=8,124=40,125=94,126=1321,127=44,128=14,129=11,130=3,131=9,132=33,
133=26,134=4,135=3,136=5,137=3,138=7,139=25,140=15,141=62,142=3,143=6,144=2,145=
4,146=6,147=11,148=18,149=15,150=6,151=2,152=5,153=580,154=3,155=3,156=6,157=3,1
58=2,159=143,160=7,161=3,162=10,163=6,164=16,165=1,166=4,167=1673,168=17,169=149
,170=2,171=7,172=5,173=4,174=5,175=416,176=5,177=4,178=14,179=3,180=1,181=47,182
=3,183=6972,184=4,185=167,186=27,187=20,188=461,189=1,190=253,191=2663,192=183,1
93=802,194=20,195=1760,196=1689,197=4210,198=1050,199=3207,200=538,201=648,202=2
2,203=93,204=63,205=32,206=317,207=79,208=1445,209=553,210=84,211=42,212=421,213
=425,214=479,215=151,216=57,217=53,218=77,219=458,220=94,221=7,222=79,223=55,224
=20,225=323,226=55,227=1018,228=24,229=32,230=667,231=1267,232=764,233=23,234=28
,235=99,236=11,237=68,238=58,239=6,240=9,241=12,242=28,243=12,244=46,245=4,246=1
2,247=25,248=27,249=13,250=9,251=1879,252=7,253=12,254=35,255=16,>=256=29016
db0:keys=799,expires=0

If it is a crash, can you please paste the stack trace that you can find in
the log file or on standard output? This is really useful for us!

Please provide any additional information below.

Original issue reported on code.google.com by arunvija...@gmail.com on 3 Jun 2011 at 8:56

GoogleCodeExporter commented 8 years ago
Do you have an exact sequence of operations to reproduce this, or can explain 
the circumstances (e.g. timeout between issuing these commands)?

Thanks,
Pieter

Original comment by pcnoordh...@gmail.com on 14 Jun 2011 at 6:44

GoogleCodeExporter commented 8 years ago
That's the cli copy-paste. I was trying to delete certain keys. I had deleted 
one and wanted to list out rest out the pattern . When the error happened 
(There was no timeout - may be 4-5 seconds delay from me between each command), 
I tried keys command without arguments - and looked like command came back 
working immediately after the error. Well, I couldn't reproduce this though. 

BTW, these are two 64bit machines and are equipped with public IPs. 

Original comment by arunvija...@gmail.com on 14 Jun 2011 at 9:15

GoogleCodeExporter commented 8 years ago
Thanks for the info. Because this can't be reproduced and the details you give 
don't clearly point towards a possible cause, I'm closing this issue.

Original comment by pcnoordh...@gmail.com on 6 Jul 2011 at 12:02