New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flow server does not start (v0.105.1) #8012
Comments
I'm having the same issue; it creates a lock file but no log file and no error output. I manually removed the lock file to no avail. I did get it to work by running as a superuser ( |
/cc @mroch |
can you try running the Flow binary directly instead of via node? Just want to rule out that extra layer of complexity. |
Running the binaries directly is how I figured out it works as a superuser, but not as a plain user. |
which linux distro/release? |
the output of
|
Linux Mint 19.2; node v12.8.0 |
Does running |
It does. |
I just installed Mint and got this:
seems like it ran with |
flow server re-execs itself as
I think something is wrong with systemd-run here (and our limited check for support didn't catch it) but I'm on mobile and can't investigate right now. |
in @xthule's strace: in my strace (also Mint): |
I don't really know what i'm looking at but here's where our straces diverge: xthule's
mine
|
I don't know if the
|
mine (it's the same):
|
Well now you're not helping. |
huh, i can repro over SSH but not from a "real" console (via vmware). |
That makes it sound like it's something from the shell. |
it's this bug: systemd/systemd#3388 confirmed because I see this in /var/log/syslog:
|
Found it in my journalctl. |
Mint is using "hybrid" cgroup mode on systemd 237 (the fix is in 238 :(). the distro we use internally is legacy mode on systemd 242.
it sounds like this bug affects systemd <= 237 in unified or hybrid mode. @gabelevi sounds like we need to detect this case. |
It looks like the merge request to fix the error comes after version 237, which is what Ubuntu Bionic (and Mint Tessa) are using. There are a few workarounds until the distros upgrade, possibly the best being booting using the legacy cgroup controller: |
confirmed it works properly in Ubuntu 19.04 (systemd 240) |
Is there any way to make this work on Ubuntu 18.04 LTS? |
testing a fix. if it works I think we'll roll a 0.105.2 patch release. (cc @avikchaudhuri, @gabelevi) |
Using the link I provided above you can change your grub command line to enable the legacy controller. Doing this worked for me and so far has not adversely affected anything on my system. |
Fine. Be that way. :) Thanks for the quick response. |
Summary: systemd < 238 has a bug that breaks `systemd-run --user --scope` (systemd/systemd#3388). just trying `--user` wasn't sufficient to detect it, but `--user --scope` does. ### Linux Mint 19.2 ``` $ systemd-run --version systemd 237 $ systemd-run --quiet --user -- true $ echo $? 0 $ systemd-run --quiet --user --scope -- true $ echo $? 1 ``` ### Ubuntu 19.04 ``` $ systemd-run --version systemd 240 $ systemd-run --quiet --user -- true $ echo $? 0 $ systemd-run --quiet --user --scope -- true $ echo $? 0 ``` Fixes #8012 Reviewed By: avikchaudhuri Differential Revision: D16770275 fbshipit-source-id: 1fe08d97b5f7ff3efc2ff7db7411adc0fded7b77
Ok, the fix is deployed in v0.105.2! It detects that |
Flow version: 0.105.0
Expected behavior
flow server
should start a serverVersion 0.104.0 is working as expected:
Actual behavior
The text was updated successfully, but these errors were encountered: