UpdateClient flow doesn't work on Ubuntu
See original GitHub issueRunning UpdateClient from Ubuntu fails as the service restarts in the middle of the dpkg -i, killing all child processes leaving the service stopped and non-functional.
Jul 02 13:14:56 ubuntu grrd[13119]: (Reading database ... 141574 files and directories currently installed.)
Jul 02 13:14:56 ubuntu systemd[1]: Stopping grr linux amd64...
Jul 02 13:14:56 ubuntu systemd[1]: Stopped grr linux amd64.
Issue Analytics
- State:
- Created 4 years ago
- Comments:18
Top Results From Across the Web
Investigate why Flow doesn't work on 32 bit Ubuntu · Issue #270
I use an Odroid (so ARM) Ubuntu 16.04 and it's relevant for me. Fortunately, I can run Flow through ESLint on Sublime on...
Read more >ratop - display and update sorted network flow data
When read from a file, ratop displays the resulting flow caches when the file is completed, updating its status display line with each...
Read more >Upgrade Ubuntu desktop - Tutorials - Ubuntu Community Hub
Hi, I am currently using Ubuntu 21.10 and after running updates, i still can't update to 22.04. Even when I run sudo do-release-upgrade...
Read more >Thunderbird email client update policy - Desktop
In Ubuntu there was no issue getting Thunderbird approved to be updated in the same way as Firefox in this case. When the...
Read more >Ubuntu Server Documentation
This chapter provides an overview of installing Ubuntu Server Edition. There is more detailed documentation on other installer topics. Preparing to Install.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@atkinsj, my understanding is that the client update mechanism hasn’t worked in a long time and it’s not clear when it stopped functioning, since it’s not tested.
We’re looking at prioritising this issue in Q4 and reimplementing/fixing the client update mechanism with adequate testing. If everything goes fine, this will be fixed in December GRR release.
Ah gotcha, for some reason I thought this was Python generated server side and pushed to the client. Will update via config management to 3401. Thanks!