Re: Issue 226 in redis: strsep not found on solaris - needed for redis-cli.c to compile.

Comment #2 on issue 237 by antirez: Redis VM not working on Solaris
http://code.google.com/p/redis/issues/detail?id=237

Please can someone check with GDB where it starts looping?

Thanks,
Salvatore

Updates:
	Status: Done

Comment #1 on issue 132 by antirez: Comment at the top of  
utils/redis-copy.rb applies to redis-sha1.rb
http://code.google.com/p/redis/issues/detail?id=132

done, thanks

Comment #4 on issue 119 by pahowes: Unable to compile on Mac OS X Leopard 

(running on a PowerPC G4)
http://code.google.com/p/redis/issues/detail?id=119

The underlying problem is that redis.c is mucking around with the thread  
context and CPU registers, which of course is CPU-specific.  Here is the  
fix for redis-2.0.0-rc4:

1. edit redis.c
2. go to line 10838.
3. Change the "#else" to "#elsif defined (__i386__)"
4. Below line 10839 add the following:
     #else
       return (void*) uc->uc_mcontext->__ss.__srr0;

The final version should look like this:

     #if defined(_STRUCT_X86_THREAD_STATE64) && !defined(__i386__)
       return (void*) uc->uc_mcontext->__ss.__rip;
     #elif defined (__i386__)
       return (void*) uc->uc_mcontext->__ss.__eip;
     #else
       return (void*) uc->uc_mcontext->__ss.__srr0;
     #endif

You should now be able to compile with the following command:

     CFLAGS='-mmacosx-version-min=10.5 -arch i386 -arch x86_64 -arch ppc  
-sysroot=/Developer/SDKs/MacOSX10.5.sdk' make

Updates:
	Status: Done

Comment #6 on issue 260 by antirez: r.keys() from redis-py v1.34.1 failing
 
against redis 2.0.0-rc1
http://code.google.com/p/redis/issues/detail?id=260

(No comment was entered for this change.)

Comment #1 on issue 303 by antirez: Disk space full crashes redis-server  
(upon restart)
http://code.google.com/p/redis/issues/detail?id=303

Accepted, thanks for reporting, It is unlikely this will be fixed in 1.2
as  
2.0 is going to be released.

I'll fix the issue and report here asap.

Cheers,
Salvatore

Updates:
	Status: Verified

Comment #3 on issue 212 by pcnoordhuis: Interactive redis-cli crashes when
 
issuing a command after period of inactivity
http://code.google.com/p/redis/issues/detail?id=212

Reconnecting when the connection has timed out in interactive mode is
fixed  
in both 2.0 and master.

Comment #2 on issue 167 by antirez: Dissapointing responsiveness of Redis 

when using append only file mode
http://code.google.com/p/redis/issues/detail?id=167

updates about this:

1) With the current Linux kernel it is not possible to flush on a
different  
thread, as write(2) will block anyway in the main thread. This sucks but I
 
don't think this is going to get fixed in little time.
2) We have now in Redis master an option so that fsync(2) is not called  
when there is a background saving/log-rewrite operation in progress. It's
a  
trick... but works.
3) All this is highly dependent on the file system used and the mount  
options.
4) "fsync none" is a trivial way to completely fix this problem but the  
drawback is that up to 30 seconds of logs can be lost.
5) fsync always is now optimized, it is still very very slow but much  
faster than before.

I'm leaving this open as it's an open problem but I don't think there are 

very good way to fix this at the moment, still with the latest changes we 

mitigated the problem enough. Currently when very low latency is required
a  
two box setup with a saving slave may be the best option.

Updates:
	Status: Verified

Comment #2 on issue 294 by antirez: [BUG][redis-cli] faulty commands mess 

subsequent reponse
http://code.google.com/p/redis/issues/detail?id=294

(No comment was entered for this change.)

Updates:
	Status: Started

Comment #1 on issue 235 by antirez: redis server not starting on linux  
redhat RHEL 3
http://code.google.com/p/redis/issues/detail?id=235

Hello, this bug sounds very strange! Can you please provide the redis.conf
 
used?

Cheers,
Salvatore

Updates:
	Status: Verified

Comment #2 on issue 225 by antirez: redis-cli REPL loop 'wrong number of  
arguments'
http://code.google.com/p/redis/issues/detail?id=225

This is now fixed.

Updates:
	Status: Accepted

Comment #1 on issue 202 by antirez: Redis does not include man pages in
the  
upstream distribution (Github)
http://code.google.com/p/redis/issues/detail?id=202

Ok we should actually ping the author of this man pages and ask if we can 

include this in the Redis distribution... but then there is the problem of
 
a complex "make install" target that we are currently avoiding at all.

Anyway at least including the man pages makes sense. Accepted.

Cheers,
Salvatore

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 300 by hatemogi: redis-check-dump shows an overflowed value with
 
huge .rdb.
http://code.google.com/p/redis/issues/detail?id=300

What steps will reproduce the problem?
1. make a huge dump.rdb file.
2. run redis-check-dump with that file.
3. I see an overflowed value in the result.

What is the expected output? What do you see instead?

I see below

$ ls -la data/dump.rdb
-rw-rw-r--  1 dante dante 11853271020 Aug  5 15:24 data/dump.rdb
$ ./redis-check-dump data/dump.rdb
==== Processed 9971202 valid opcodes (in -1031630877 bytes)  

Updates:
	Status: Accepted

Comment #1 on issue 106 by antirez: Incorrect parsing of redis.conf save  
parameters
http://code.google.com/p/redis/issues/detail?id=106

yep not cool at all, accepted. I've some plan to rewrite most of the  
configuration file parsers and for sure sanity checks including parameters
 
types and limits will be supported as well.

Updates:
	Status: Verified

Comment #4 on issue 97 by antirez: Ubuntu 9.10 /etc/init.d/redis-server  
[stop|restart] does not force a sync to disk
http://code.google.com/p/redis/issues/detail?id=97

this is now fixed (as Chris suggested)

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 312 by themig.adx: redis-server hanging when being populated
with  
keys-values w/expire with VM enabled
http://code.google.com/p/redis/issues/detail?id=312

What steps will reproduce the problem?
1. Start redis-server with
    vm-enabled yes
    vm-max-memory 2147483648
    vm-page-size 32
    vm-pages 134217728
    etc
2. From a standalone executable issue commands in a loop that will do the 

following:
    getset random_key random_value
    expire random_key 2592000
3. When the server gets across boundary of its virtual machine (2 G)it  
stops responding to cli and to "redis-stat vmstat" with about 48% CPU busy
 
on our LINUX system, probably falling into a loopwhole of VM swapping.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 296 by bjarni.runar: redis-cli does not handle EOF in monitor  
mode correctly
http://code.google.com/p/redis/issues/detail?id=296

What steps will reproduce the problem?
1. run redis-cli in monitor mode
2. killall redis-server

What is the expected output? What do you see instead?

redis-cli should exit, as the server is no longer running. It does not,  
instead it spews infinite newlines.


What version of the product are you using? On what operating system?

redis 2.0.0rc3


Please provide any additional information below.

Patch attached, fixes the issue.

Attachments:
	redis-cli-newlines.patch  798 bytes

Updates:
	Status: Verified

Comment #1 on issue 219 by antirez: With AOF fsyncing after every command 

redis-server can end up with partially applied transactions inside
dataset.
http://code.google.com/p/redis/issues/detail?id=219

This is now fixed, either the whole transaction or nothing will be written
 
in the AOF stream.

Thanks for reporting,
Salvatore

Updates:
	Status: Verified

Comment #3 on issue 197 by antirez: Inconsistent? Handling of whitespace
in  
keys, at least in redis-cli
http://code.google.com/p/redis/issues/detail?id=197

This is now completely fixed, since Redis 2.0:


redis> set "any kind of key\n" foo
OK
redis> get "any kind of key\n"
"foo"

Closing :)
Salvatore

Updates:
	Status: Verified

Comment #1 on issue 179 by antirez: redis-cli fails after error in  
multi/exec
http://code.google.com/p/redis/issues/detail?id=179

Fixed in redis master,

Cheers,
Salvatore

Updates:
	Status: Verified

Comment #3 on issue 168 by antirez: Feature Request] redis-cli needs a  
auth-option
http://code.google.com/p/redis/issues/detail?id=168

This was fixed indeed (see the -a option of redis-cli)