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

Access mcrouter and logger services from WSL #336

Open
aregtech opened this issue Feb 19, 2024 · 0 comments
Open

Access mcrouter and logger services from WSL #336

aregtech opened this issue Feb 19, 2024 · 0 comments
Labels
bug Something isn't working challenge enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@aregtech
Copy link
Owner

aregtech commented Feb 19, 2024

Describe:
The mcrouter and logger are services that can run under Windows and Linux platform. If these services run under Windows, the applications running under WSL (Windows Subsystem for Linux) with Ubuntu distro cannot connect to mcrouter and logger. The other way work fine, i.e. if services run in WSL, applications under Windows easily connect mcrouter and logger.

As a first step, changed the IP address of mcrouter and logger, replaced 127.0.0.1 to 172.23.96.1 (selected from ipconfig). But it didn't help. As well tried to make changes in the firewall settings of Windows Defender. Not sure whether made in the right way, but it also didn't help.

To Reproduce

  1. Compile AREG SDK under Windows with enabled logging (default behavior).
  2. Start mcrouter.exe and logger.exe
  3. Optionally, to make sure that the there is a connection, can start logobserver.exe, type -r to start log observer and time -i to list connected instances. Result: it lists the mcrouter.exe ;
  4. Open WSL and compile AREG SDK under Linux (Ubuntu) with enabled logging (default behavior).
  5. Start logobserver.out, which theoretically should connect to logger.exe running under Windows, type -r to start observer, type -i to list connected instances. Result: it displays message that no instance is connected.
  6. Start any application with IPC (for example, the client service application of example 12). Result: nothing happens.

Expected behavior
The applications should connect to the logger and mcrouter independent whether they run under Windows, WSL or Linux machine.

Desktop:

  • OS: Windows and WSL with Ubuntu Linux distro
  • Hardware: x64
  • Compiler: msvc for Windows (cl compiler), g++ or clang++ for Linux
  • AREG SDK version: latest sources in repo

Additional context
I do believe it is not a software issue, rather than configuration or security settings. There is a known issue accessing Windows service from WSL, but I was not able to solve it easily.

To change the IP address of mcrouter, edit router::*::address::tcpip = 127.0.0.1 in areg.init. The * can be replaced by application name or leave * if it reflects to all applications.

To change the IP address of logger, edit logger::*::address::tcpip = 127.0.0.1 in areg.init. The * can be replaced by application name or leave * if it reflects to all applications.

@aregtech aregtech added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers challenge labels Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working challenge enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
Status: No status
Development

No branches or pull requests

1 participant