Upgrade via notification breaks systemd service
See original GitHub issue- I got a notification saying “There’s an update available, press to Update”.
- My systemd unit failed.
code-server.service: Start request repeated too quickly.
- EDIT: I had to update the folder name to
.1588265231799
. - After a manual restart it ran fine again.
I’m not sure this is a bug in code-server or an issue with running it as a systemd service.
My unit for reference:
[Unit]
Description=VSCode server
[Service]
ExecStart=%h/dev/code-server-3.1.1-linux-x86_64/code-server --host 127.0.0.1 --disable-ssh %h/dev
Restart=always
[Install]
WantedBy=default.target
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Upgrade via notification breaks systemd service #1580 - GitHub
I got a notification saying "There's an update available, press to Update". My systemd unit failed. code-server.service: Start request ...
Read more >Upgrade from 16.04 to 18.04 has broken systemd - Ask Ubuntu
Looking through xenial's (16.04) packages on Launchpad it requires libsystemd0 (229-4ubuntu21.31). So although the upgrade did happen from 16.04 ...
Read more >Bug #1773859 “Upgrades to 18.04 fail due to systemd-shim”
[Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart.
Read more >Bug#944645: systemd: upgrade breaks dbus
systemd upgrade broke dbus, which in turn prevents normal operation of APT and upgrade of packages that depend upon dbus messages. ... See...
Read more >Auto upgrade/notification with systemd timer/service units.
Here's the contents. Notes, that sets a variable called CHK with a value of the command, above there wherever $CHK is used in...
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
That was it! I missed that before. Admittedly trying to get back up and running quickly didn’t help.
Unknown option --disable-ssh
So I changed it back to the original folder and dropped the option and 3.2 runs like a charm now!
Sweet.