Redis: Whole windows 7 not responding due to MSI installer

Created on 28 Nov 2018  路  9Comments  路  Source: tporadowski/redis

I installed v4.0 x64 msi on Windows 7 64 bits. (latest release)
After installation whole system was not respnding.
So I revert installation to MSopentech 3.2.100 and again it is working fine.

Most helpful comment

Our Windows "Operations team" preference is native Windows Service monitoring. It fits with existing toolsets for those teams. While a lot of teams are moving to containerized environments, that would similarly deprecate the need for a Windows redis port. So if you are maintaining a Windows version of unix service, it is advisable to be Windows Services friendly.

All 9 comments

Could you please try to run redis-server.exe directly without installing the msi?
Report the console output if possible. Thanks

Ya Its working fine when I am running it directly using zip file:

  1. By extracting zip
  2. Through command line from extracted directory.

Do you need to run it as a registered windows service ?
I believe that we should drop support for installers and services and focus on keeping up with pairing with redis releases.
If you need to run as a service, you can start and monitor on the Task Scheduler easily.

Yes, +1 from my side for dropping MSI and service support.
Mainly if any issues with msi installer definitely affects installed services and messy to resolve the same.
So it is best strategy to keep up Redis releases until Redis Labs official support starts.

Our Windows "Operations team" preference is native Windows Service monitoring. It fits with existing toolsets for those teams. While a lot of teams are moving to containerized environments, that would similarly deprecate the need for a Windows redis port. So if you are maintaining a Windows version of unix service, it is advisable to be Windows Services friendly.

I second what @raveller says - I've been running Redis on Windows for quite some time and it's hard to do without service support, especially when you need to coordinate with other services for some reason (automation scripts)

I agree that windows service is important. I just don't believe it should belong to the same git as this repo. It could be a wrapper project mantained elsewhere. The purpose of this repo should be to mantain a windows port only in my opinion.

Redis (as most of Linux server applications) supports "daemonization" and therefore having Windows Services support built-in is the answer to lack of that functionality in Windows. I can't however imagine easy maintenance of this feature in a separate project/repo :) as this either has to be part of the resulting binary or a wrapper application that would spawn redis-server.exe (but then why another process?).

Closing due to inactivity and old Windows version.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yinlin66 picture yinlin66  路  9Comments

Kortenbach picture Kortenbach  路  12Comments

israellot picture israellot  路  25Comments

tporadowski picture tporadowski  路  33Comments

mehrdadn picture mehrdadn  路  7Comments