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

Open-promise never resolved if .conf file contains logfile #7

Open
sebastiansondergaard opened this issue Feb 20, 2017 · 3 comments
Open
Assignees

Comments

@sebastiansondergaard
Copy link

Hi.

We tried to use the redis-server package to start a local redis instance configured by a .conf file.

We can successfully start an instance if we don't specify any logfile in the .conf file. But when it's specified redis is started and creates a logfile as expected but the open-promise is never resolved.

We attached the .conf-file which is causing the issue and hope that you can clarify the issue for us.

Best regards
Sebastian and Martin
redis.conf.txt

@BrandonZacharie
Copy link
Owner

Thanks for the report. I'll have a look.

@BrandonZacharie
Copy link
Owner

BrandonZacharie commented Feb 20, 2017

Specifying a log file makes Redis write messages to that file; redis-server expects those messages to come from stdout.

If there's a way to get these things to work together, I'd like to explore that solution. If there isn't, I suppose we'll need to parse the configuration file for a logfile statement and then tail the given file instead of stdout.

@JonathanBristow
Copy link

A possible workaround which worked for my use case:

const server = new RedisServer({
         port: 6379,
         conf: ''
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants