Situation: Connecting IOIO Bridge to android_x86 in Virtualbox
*adb connected to 10.10.10.3:5555 (where 10.10.10.3 is VBox)*
adb forward tcp:4545 tcp:5555
java -jar ioiobridge.jar COM3
The output Seems
Connecting to IOIO... Connected!
Connecting to Android application... Connected!
Bridge is running...
Bridge closed.
Connecting to IOIO... Connected!
Connecting to Android application... Connected!
Bridge is running...
Bridge closed.
Connecting to IOIO... Connected!
Connecting to Android application... Connected!
Bridge is running...
Bridge closed.
Connecting to IOIO... Connected!
Connecting to Android application... Connected!
Bridge is running...
Bridge closed.
Connecting to IOIO... Connected!
Connecting to Android application... Connected!
Bridge is running...
Bridge closed.
what am i going wrong ?
can anyone guess ?
I Found the answer,
Its Because the Android Program is Closing the connection
Reason:Error with opening IOIO Instance (i haven't used AbstactIOIOActivity or its new version , i am working around IOIO Factory)
if any one in future faces the problem the error is in programming side establishing connection,just use IOIO Libs ,otherwise do a roundup job to create your own as i did.
Related
I am facing this error "OperationalError at /results/
connection to server at "localhost" (127.0.0.1), port 5432 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (::1), port 5432 failed: Cannot assign requested address
Is the server running on that host and accepting TCP/IP connections?" when I try to run a django application that I just deployed in railway.app.
What is the problem and how can I fix?
When I run the application locally it works well, it is my first time deploying a django application to production and I have no idea how to solve that issue, your help is greatly appreciated.
I just realized that the error is due to not using railway's database. Apparently it was running localhost and my postgres' port, created a postgres database in railway and connected to the deployed django app and it is now working well. Thank you #Laurenz Albe for reminding me that.
I've been following this guide https://medium.com/#pellea/using-adb-with-wsl2-7aebbb070a47 and so far have gotten to the point where WSL2 can see the emulator(s) running on Windows through Android Studios -> AVD manager. For example, on both Windows and WSL2, adb devices correctly shows:
List of devices attached
emulator-5554 device
However, when I go to my expo app and try to launch the Android emulator, I get the following error message:
Couldn't start project on Android: could not connect to TCP port 5554: Connection refused
This is after I've tried the following:
exporting ADB_SERVER_SOCKET=tcp:<MY IP>:5037 in my WSL2 profile(s)
Unblocking WSL2 vEthernet connections from my Windows firewall via (from the above link)
Set-NetFirewallProfile -DisabledInterfaceAliases "vEthernet (WSL)"
I've portforwarded 5554 from Windows to WSL2, as well as 5037 (from 0.0.0.0 to 127.0.0.1):
$WSL_CLIENT = bash.exe -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'";
$WSL_CLIENT -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
$WSL_CLIENT = $matches[0];
iex "netsh interface portproxy add v4tov4 listenport=5554 listenaddress=127.0.0.1 connectport=5554 connectaddress=$WSL_CLIENT"
The ports are as follows:
netsh interface portproxy show all
Listen on ipv4: Connect to ipv4:
Address Port Address Port
--------------- ---------- --------------- ----------
127.0.0.1 8081 172.25.38.171 8081
0.0.0.0 5037 127.0.0.1 5037
127.0.0.1 5554 172.29.149.0 5554
Just had the same issue with Expo.
Here is what fixed it for me:
Check for a process that uses port 5555 (Terminal)
netstat -ano | findstr 5555
Kill the process using its ID (PowerShell)
Stop-Process -ID [PROCESS_ID] -Force
Then it started working.
I had the exact same problem, but with a different setup (using Expo with the Metro bundler on a Mac). I worked around it by trying different virtual device images. Maybe the same can help you.
The virtual device that works with me so far is the one selected in this screenshot: https://i.stack.imgur.com/CFTJ0.png. The other two in the screenshot have the same problem. I don't really know the actual reason, must be something with port access with those other emulated devices.
Image details:
Name: 4 WVGA (Nexus S) API 29
API: 29
Target: Android 10.0 (Google APIs)
CPU/ABI (x86)
I'm sure other images work as well (or configuring the others somehow), i just haven't tried many more because it takes so long and they're so big.
Did you try to map port 5554 to Windows IP instead? (or localhost). The Android emulator is running on Windows, not WSL2, so the port proxy should be from WSL2 to Windows, not backwards.
Have you already solved it in another manner?
I have an application signed for microsoft store which starts a web socket server on localhost (0.0.0.0:8081) on launching. Then I run python script with websocket client on the same host and try to connect to server (ws://127.0.0.1:8081) and it couldn't connect. But I can connect without any problems if I run this python script from another PC. Actually it works fine on local PC on another platforms: Win7, MacOS.
What i tried:
disabled windows firewall and defender
tried to add exception for application using CheckNetIsolation LoopbackExempt
tried to connect using different ip (0.0.0.0, 127.0.0.1, pc name)
It seems like I have to switch/set on/off some option for application or win10, but I can't find it
Thanks for help in advance
I found a solution https://learn.microsoft.com/en-us/windows/iot-core/develop-your-app/loopback
if you want to connect smth to win application on win 10 you should run
CheckNetIsolation.exe LoopbackExempt -is -n=your application
permanently
the best way to add it to start up menu
This is the error when trying to run icecast2 from the serving using the terminal (command line): sudo icecast2 -b -c /etc/icecast2/icecast.xml
Error message:
EROR connection/connection_setup_sockets Could not create listener socket on
port 8000
EROR connection/connection_setup_sockets No listening sockets established
Server startup failed. Exiting
I can load the icecast server from browser BUT no mount points. Please help.
Sounds like Icecast is already running.
Why are you trying to start it manually? You should use systemd or the init script that comes with the Icecast package of your distribution.
There isn't any error on installation and on startup I get the below message :
Server started listening on port 20223
Failed to open browser, please navigate to http://localhost:20223/
But the server is instance is not reachable # http://localhost:20223/ or
http://localhost:20223/slamdata/index.html
netstat -pnlt show the server is up & listening to port
tcp6 0 0 :::20223 :::* LISTEN 24564/java
any help ?
This was initially caused by a threading issue that was identified and resolved. If a user's virtual (or physical) environment had only one CPU available then the Scalaz executor might hang. It should not matter how many CPUs a server has now. See here for SD-1574 in JIRA.
Recent versions of SlamData (i.e. late April 2016 and newer) do not have this problem.