Anbox reports parsing errors for vhal messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Anbox Cloud |
Fix Released
|
Medium
|
Simon Fels |
Bug Description
Seeing the following in logs from Anbox with 1.23.0-
Aug 14 13:42:39 foo anbox-starter[
Aug 14 13:42:39 foo anbox-starter[
The error stays regardless how often you connect again to the stream. The only thing which changes is that the protobuf error is not showing up again:
Aug 14 13:57:09 aaos13 anbox-starter[
Aug 14 13:57:09 aaos13 anbox-starter[
Restarting Anbox + Android typically fixes the problem.
Changed in anbox-cloud: | |
milestone: | none → 1.23.1 |
assignee: | nobody → Alexis Janon (ajanon) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in anbox-cloud: | |
milestone: | 1.23.1 → 1.23.2 |
Changed in anbox-cloud: | |
status: | Triaged → Fix Committed |
assignee: | Alexis Janon (ajanon) → Simon Fels (morphis) |
Changed in anbox-cloud: | |
status: | Fix Committed → Fix Released |
Strace'ing the vhal serivces shows it is actually responding to Anbox when it is sending the prof config request
1375 <... read resumed>"0002", 4) = 4 20\0\"\ 31\10\200\ 230\200\ 217\1\20\ 3\30\1 \200\200\ 200\7U\ 0\0\0\0] \0\0\0\ 0\""... , 2562) = 2562
1375 read(6, "\10\2", 2) = 2
1375 write(6, "0a02", 4) = 4
1375 write(6, "\10\3\