BRPOP/BLPOP requests always closed by server after 600 seconds

[tony]

Hello everybody,

I'm talking to a Redis server via Python sockets and when sending a
indefinitely blocking lpop/rpop command with timeout "0" the client
connection is always closed by the server after approx. 600 seconds.

I configured the Redis server with "timeout 0" so that client
conenction timeouts are disabled. However, br-/rlpop with timeouts <
600secs works. I'm glad for any help.

Can anyone confirm this issue?

Specs:
Using Mac OS X 10.5.5 with a custom build of redis 2.0.0 RC2. Aside
from "timeout 0" my Redis server uses the default factory settings.

best regards,

peter

[Salvatore Sanfilippo]

Hello,

I assume you are hacking against 127.0.0.1 right?

Cheers,
Salvatore

> --
> You received this message because you are subscribed to the Google Groups "Redis DB" group.
> To post to this group, send email to redi...@googlegroups.com.
> To unsubscribe from this group, send email to redis-db+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/redis-db?hl=en.
>
>

--
Salvatore 'antirez' Sanfilippo
http://invece.org

"Once you have something that grows faster than education grows,
you’re always going to get a pop culture.", Alan Kay

[Pieter Noordhuis]

This issue was just solved on IRC. The configuration filename was not
passed as argument when redis-server was started. Idea: rename
redis.conf to redis.conf.example or something, to prevent ambiguity
whether or not Redis autoloads redis.conf in the same path.

Cheers,
Pieter

[Salvatore Sanfilippo]

On Mon, Jul 19, 2010 at 3:36 PM, Pieter Noordhuis <pcnoo...@gmail.com> wrote:
> This issue was just solved on IRC. The configuration filename was not
> passed as argument when redis-server was started. Idea: rename
> redis.conf to redis.conf.example or something, to prevent ambiguity
> whether or not Redis autoloads redis.conf in the same path.

Ok, I see this many times every week, I guess the warning Redis prints
at startup is not big enough ;)

Cheers,
Salvatore

[tony]

Hahaha ... I noticed this warning RIGHT NOW! :-) Dear Google, please
don't index this thread.


On 19 Jul., 15:40, Salvatore Sanfilippo <anti...@gmail.com> wrote:

> On Mon, Jul 19, 2010 at 3:36 PM, Pieter Noordhuis <pcnoordh...@gmail.com> wrote:
> > This issue was just solved on IRC. The configuration filename was not
> > passed as argument when redis-server was started. Idea: rename
> > redis.conf to redis.conf.example or something, to prevent ambiguity
> > whether or not Redis autoloads redis.conf in the same path.
>
> Ok, I see this many times every week, I guess the warning Redis prints
> at startup is not big enough ;)
>
> Cheers,
> Salvatore
>
> --

> Salvatore 'antirez' Sanfilippohttp://invece.org