Running g5g.2xlarge image - iOS WebRTC Camera crash

Hey Terence
  Thanks for the bug report.
  We confirm the issue that when streaming from safari(IOS devices), a native crash happened if opening up the camera application. And this issue only happened to applications that are created with a GPU instance type, like g4.3. That's the reason why you hit this issue when you installed Anbox Cloud appliance on g5g.2xlarge instance(where Nvidia T4G GPU is plugged) but not on c4g.2xlarge.
  I just created an internal bug tracking for this. The fix to this bug should be included in the next minor release(1.15.0) and I will keep you posted on any updates for the upcoming release.

BR
Gary

Hi Gary,

I've received,
Anbox stream failed Error: failed to communicate with the signaler

Do you think it's the same issue caused by g4.3?

1) I've tried to delete the session and recreate
2) I've to restart the whole system
3) I've tried to delete/recreate the application

All of it is not working, now i can't login into any of the session.

Would you be able to suggest any logs i should look into?

Do you think it's the same issue caused by g4.3?
A: no, that's a different issue.
   Do you mean whenever you create a new session from a dashboard, it failed with an error like
"Anbox stream failed Error: failed to communicate with the signaler"?

   Looks like the dashboard was unable to access the stream gateway. It seemed to me it stopped working all of sudden, am i right? Do you recall what have you done prior to the issue occurrence?
   Are you streaming from safari on ios device or chrome? any chance you can debug ios safari for your mac [1] and check the logs or do a remote debug if you stream from Android Chrome browser

   Would you mind dumpping the logs of anbox-stream-gateay via:
   $ juju ssh -m appliance:anbox-cloud anbox-stream-gateway/0 sudo snap logs -n=all anbox-stream-gateway

[1] https://www.busbud.com/blog/debug-ios-safari-mac/
[2] https://developer.chrome.com/docs/devtools/remote-debugging/

BR
Gary

2022-08-02T03:20:48Z anbox-stream-gateway.daemon[3529]: I0802 03:20:48.097555 3529 http_api.go:987] Service: Disconnecting previous client before preparing session cbjjj83hnbs028ptncn0
2022-08-02T03:20:48Z anbox-stream-gateway.daemon[3529]: E0802 03:20:48.097983 3529 http_api.go:1022] Service: Failed to disconnect clients for session cbjjj83hnbs028ptncn0: <nil>

I recall trying to use the Javascript SDK on another domain
https://github.com/anbox-cloud/anbox-streaming-sdk/tree/master/js

An while connecting and refreshing, it suddenly not working. And all the session suddenly stopped even new session

1. Regarding the logs that you shared above, that's all you have? it seems to me the logs of anbox-stream-gateway got truncated and from the last few lines, all looked fine.
Could you paste full logs of anbox-stream-gateway by running
```
juju ssh -m appliance:anbox-cloud anbox-stream-gateway/0 sudo snap logs -n=all anbox-stream-gateway
```

2. As I mentioned above, you could do a remote debug by connecting client device, and what do you find from the console by following [1] or [2]?

3. If you don't have an Android or IOS device to do the remote debug, what if you navigate to the dashboard from the desktop browser, like chrome, and enable dev tool, can you launch a new session successfully? if not, what kind of error message do you see from the `console` tab ? [3]

BR
Gary

[1] https://www.busbud.com/blog/debug-ios-safari-mac/
[2] https://developer.chrome.com/docs/devtools/remote-debugging/
[3] https://developer.chrome.com/docs/devtools/console/

1. That's the error message i've received, it wasn't truncated

2. Sadly i destroyed the instance and it couldn't be replicated

3. I was using Mac OS Chrome browser (Desktop)
 - Launched a new session successfully? Yes, amc ls showed instance running and dashboard appeared green
 - Console tab - i've launched through dashboard

2. Sadly i destroyed the instance and it couldn't be replicated
A: yeah, that's a bit sad.

3. I was using Mac OS Chrome browser (Desktop)
 - Launched a new session successfully? Yes, amc ls showed instance running and dashboard appeared green
A：And you can get stream working when launching a new session from the dashboard ? when you click the `Exit stream` and Join the same session, is everything working fine?

 - Console tab - i've launched through dashboard
A: Any error you find until now whenever you launch a new session or join a session?

Can get stream working when launching a new session from the dashboard ?
- No - Anbox stream failed Error: failed to communicate with the signaler

When you click the `Exit stream` and Join the same session, is everything working fine?
- No - Anbox stream failed Error: failed to communicate with the signaler

Any error you find until now whenever you launch a new session or join a session?
- No error when i see the screen, the instance run successfully, waiting for the session to load... but no screen appearing, when refresh - Anbox stream failed Error: failed to communicate with the signaler

I've replicated the issue

1) Setup Cloud Application Init
2) Setup Application without APK on Dashboard
3) Run a session
- Work all fine
5) Bind a domain name with the instance IP address example.com -> 1.2.3.4 (instance ip)
4) Setup domain name TLS using Certbot on example.com
https://discourse.ubuntu.com/t/set-up-tls-for-the-anbox-cloud-appliance/28552
5) Setup streaming client token
https://anbox-cloud.io/docs/howto/stream/access
5) Setup JS SDK running the example js
https://github.com/anbox-cloud/anbox-streaming-sdk/tree/master/examples/js
- Replace the gateway with https://example.com
- Replacing APP with Session ID
- Replace token with the token created
6) Run https with cert on different port http://example.com:8000
7) Visit the website with the html
8) Error on website
AnboxStream failed: failed to communicate with the signaler
9) Visit any session shows
It show: AnboxStream failed: failed to communicate with the signaler
10) Create new application and new session
It show: AnboxStream failed: failed to communicate with the signaler

Thanks for those steps.

Could you run the following commands and share the output with us?

1. sudo snap get anbox-cloud-appliance experimental.location
2. juju ssh -m appliance:anbox-cloud anbox-stream-gateway/0 -- sudo cat /var/snap/anbox-stream-gateway/common/service/config.yaml | head -n5

BR
Gary

I've followed the steps, and realised that both the location address is different, i've fixed the address and fix the https cert, currently the streaming it's working fine

Thanks Gary

You're welcome. Good to hear you fixed that.
It's a bug in our documentation that if you don't want to reboot the machine after configuring the https cert and location for the appliance, you need to run the following command:

$ sudo systemctl start snap.anbox-cloud-appliance.reboot-checker.service

This enables the components like gateway/dashboard to use the location that you specified through `experimental.location` config in the end.

Is there a nightly build for the patched version?

Does 1.15.0 still on track on August 24, 2022?

> Is there a nightly build for the patched version?

We currently only provide stable images, no nightly/beta/candidate.

> Does 1.15.0 still on track on August 24, 2022?

Yes, it is.

ubuntu@ip-192-168-3-51:~$ anbox-cloud-appliance status
status: ready
update-available: false
reboot-needed: false

not able to update to 1.15.0

How can i check my current version?

Somehow the update was possible, i've updated the code however,

"Anbox stream failed Error: connector failed to connect: failed to join session" When i launch camera app inside Safari IOS browser

The bug doesn't seems to be fixed

Could you help to check if the application got updated after 1.15.0 images were imported to AMS? Something like,

$ amc application show <application_name>
$ amc image show $(amc application show <application_name> | grep "parent-image" | cut -d' ' -f2)

Could you share the output of the above commands with us?

Thanks.

BR
Gary

It's working fine after i recreate the application
Thanks

So looks like the application didn't get updated in time after the images were refreshed in AMS. It depends on the number of applications created in AMS and the free resources that your deployment owns to schedule a base container for an application update. Usually, after the parent images got updated(in your case, 1.14.x -> 1.15.0), AMS will schedule an update for each application and a new revision of the application will be generated automatically afterward.

Anyway, it's good to hear it's working fine now.