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

WSL 2.0: networkingMode=mirrored docker-ce oracle db container connection timeout #12419

Open
1 of 2 tasks
codeart1st opened this issue Dec 30, 2024 · 4 comments
Open
1 of 2 tasks
Labels

Comments

@codeart1st
Copy link

codeart1st commented Dec 30, 2024

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.4.8.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04.1 LTS

Other Software

docker-ce (systemd service): 27.4.1, build b9d17ea
Oracle DB container: 19.3.0.0.0

Repro Steps

Run docker container based on container-registry.oracle.com/database/enterprise:19.3.0.0-slim with port mapping -p 1522:1521. Connect to the DB with JDBC driver jdbc:oracle:thin:@localhost:1522:DBNAME.

Expected Behavior

Connecting to an oracle db container with localhost instead of specific ip from windows host should work as any other db container (running docker-ce under systemd).

Actual Behavior

This will not work because of a timeout.

***********************************************************************
2024-12-30T08:07:46.657733664Z 
2024-12-30T08:07:46.657736642Z Fatal NI connect error 12537, connecting to:
2024-12-30T08:07:46.657739545Z  (ADDRESS=(PROTOCOL=tcp)(HOST=172.17.13.1)(PORT=43102))
2024-12-30T08:07:46.657742471Z 
2024-12-30T08:07:46.657745214Z   VERSION INFORMATION:
2024-12-30T08:07:46.657748038Z 	TNS for Linux: Version 19.0.0.0.0 - Production
2024-12-30T08:07:46.657751476Z 	Oracle Bequeath NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
2024-12-30T08:07:46.657754534Z 	TCP/IP NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
2024-12-30T08:07:46.657757600Z   Version 19.3.0.0.0
2024-12-30T08:07:46.657760469Z   Time: 30-DEC-2024 08:07:45
2024-12-30T08:07:46.657763435Z   Tracing not turned on.
2024-12-30T08:07:46.657766266Z   Tns error struct:
2024-12-30T08:07:46.657769048Z     ns main err code: 12537
2024-12-30T08:07:46.657771906Z     
2024-12-30T08:07:46.657774747Z TNS-12537: TNS:connection closed
2024-12-30T08:07:46.657777673Z     ns secondary err code: 12560
2024-12-30T08:07:46.657780830Z     nt main err code: 507
2024-12-30T08:07:46.657784333Z     
2024-12-30T08:07:46.657787481Z TNS-00507: Connection closed
2024-12-30T08:07:46.657790359Z     nt secondary err code: 0
2024-12-30T08:07:46.657793206Z     nt OS err code: 0
2024-12-30T08:07:46.657796059Z 2024-12-30T08:07:45.714256+00:00
2024-12-30T08:07:46.657799032Z opiodr aborting process unknown ospid (627) as a result of ORA-609

Using the current ip address from WSL2 (eth1) jdbc:oracle:thin:@192.168.1.114:1522:DBNAME the connection works fine.
I only have problems with oracle db containers. Other containers like PostgreSQL or Microsoft SQL Server works fine.
Maybe it's related to an firewall issue or a more specific TNS oracle problem.

.wslconfig

[wsl2]
guiApplications=true
networkingMode=mirrored
dnsTunneling=true
autoProxy=false

[experimental]
autoMemoryReclaim=gradual
sparseVhd=true
hostAddressLoopback=true

Diagnostic Logs

WslNetworkingLogs-2024-12-30_09-18-32.zip

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@codeart1st
Copy link
Author

Copy link

Diagnostic information
.wslconfig found
Detected appx version: 2.4.8.0
optional-components.txt not found

Copy link

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/18273093/WslNetworkingLogs-2024-12-30_09-18-32.zip
.wslconfig found
Detected appx version: 2.4.8.0
optional-components.txt not found

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

No branches or pull requests

2 participants