webrtc cannot connect to session with errcode 251
Bug #1946709 reported by
Chaoxin Hu
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Anbox Cloud |
Incomplete
|
Undecided
|
Gary.Wang | ||
Bug Description
Created an anbox instance on AWS, successfully launched application. But when trying to connect to session it reports "lost WebRTC connection". And when I check the session console in Web page, it shows "service exited with status 251", and sometimes "service killed with status SEGV"
I switched different networks from my browser side and it yields same result. I am using chrome and Edge and the outcome is the same.
Is this issue from the anbox side, the application side, the webrtc, or browser? Can I find any relevant logs about this?
Revision history for this message
| Gary.Wang (gary-wzl77) wrote | #1 |
| Changed in anbox-cloud: | |
| assignee: | nobody → Gary.Wang (gary-wzl77) |
| Changed in anbox-cloud: | |
| status: | New → Incomplete |
To post a comment you must log in.
Hey
Thanks for reaching out.
When the above issue happened, could you enter the ams node and dump the logs of the container which ended up to the error status as follows and share them with us?
```
$ amc show-log <container_id> system.log | system.log
$ amc show-log <container_id> android.log | android.log
$ amc show-log <container_id> xxxxxxx-
```
Thanks