Closed emme1444 closed 2 years ago
This should have been fixed in #778. There will be a release with a fix today.
Thanks for the response! I'll try it out tomorrow.
Hi @elprans!
Ok, so I've tried out cli version 2.0.0-dev.811+1a17756
. I don't know if this is what you meant when you said there'd be a fix for later today, but anyway. I mean the warning message added in #778 exists so yeah.
This version does have the warning but it doesn't really help me, since the message only mentions auto-startup. However, like I explained in the issue description above, EdgeDB does not want to start the instance at all. As you can see with the updated logs below. All calls to systemctl
return exit status: 1
.
No `edgedb.toml` found in `/home/user/dev/edgedb/init_test3` or above
Do you want to initialize a new project? [Y/n]
> Y
Specify the name of EdgeDB instance to use with this project [default: init_test3]:
> init_test3
Checking EdgeDB versions...
Specify the version of EdgeDB to use with this project [default: 2.0-rc.3]:
> 2.0-rc.3
┌─────────────────────┬───────────────────────────────────────────────┐
│ Project directory │ /home/user/dev/edgedb/init_test3 │
│ Project config │ /home/user/dev/edgedb/init_test3/edgedb.toml │
│ Schema dir (empty) │ /home/user/dev/edgedb/init_test3/dbschema │
│ Installation method │ portable package │
│ Version │ 2.0-rc.3+8c42ac9 │
│ Instance name │ init_test3 │
└─────────────────────┴───────────────────────────────────────────────┘
Version 2.0-rc.3+8c42ac9 is already installed
Initializing EdgeDB instance...
[systemctl] Failed to connect to bus: No such file or directory
[2022-07-23T13:55:35Z WARN edgedb::portable::linux] failed to reload systemd daemon: systemctl failed: exit status: 1 (command-line: "systemctl" "--user" "daemon-reload")
[systemctl] Created symlink /home/user/.config/systemd/user/default.target.wants/edgedb-server@init_test3.socket → /home/user/.config/systemd/user/edgedb-server@init_test3.socket.
[systemctl] Failed to connect to bus: No such file or directory
[2022-07-23T13:55:35Z WARN edgedb::portable::project] Error running EdgeDB as a service: service start failed: exit status: 1 (command-line: "systemctl" "--user" "start" "edgedb-server@init_test3.socket")
EdgeDB will not start on next login. Trying to start database in the background...
Specifying instance name as positional argument is deprecated. Use `-I init_test3` instead.
[systemctl] Failed to connect to bus: No such file or directory
edgedb error: service start failed: exit status: 1 (command-line: "systemctl" "--user" "start" "edgedb-server@init_test3.socket")
Running edgedb instance list
[systemctl] Failed to connect to bus: No such file or directory
┌───────┬────────────┬───────┬──────────────────┬──────────┐
│ Kind │ Name │ Port │ Version │ Status │
├───────┼────────────┼───────┼──────────────────┼──────────┤
│ local │ init_test3 │ 10703 │ 2.0-rc.3+8c42ac9 │ inactive │
└───────┴────────────┴───────┴──────────────────┴──────────┘
shows the instance as inactive
.
Running edgedb instance start init_test3
outputs the following.
Specifying instance name as positional argument is deprecated. Use `-I init_test3` instead.
[systemctl] Failed to connect to bus: No such file or directory
edgedb error: service start failed: exit status: 1 (command-line: "systemctl" "--user" "start" "edgedb-server@init_test3.socket")
I genuinely don't understand. What am I missing?
Can you show the output of env
command?
I can't reproduce that on Windows 11 on wsl2. Do you have some specific shell configuration file? Do you use default shell or a custom one? Or maybe you're running edgedb
command from a script or other command?
I am using zsh
(oh-my-zsh
). However I can reproduce the issue using bash
too.
The following is the same for both zsh
and bash
.
$ which edgedb
/home/user/.local/bin/edgedb
$ file $(which edgedb)
/home/user/.local/bin/edgedb: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, BuildID[sha1]=ce3509ecb4488ffd8036e15d13e8c58e32d96e08, stripped
EdgeDB CLI version 2.0.0-dev.811+1a17756
Ah, right, it's the new GUI support in windows that set XDG_RUNTIME_DIR
. I was finally able to reproduce that. Should be easy to fix.
2.0-rc.3
)2.0.0-dev.810+fd4a23a
Ubuntu 22.04 (WSL2 on Windows 11)
Steps to Reproduce:
edgedb project init
in the WSL shell in a directory on the WSL filesystem.I stumbled on to #647, however the output presented there seems to suggest it's possible to start the instance with
edgedb instance start
, just not "auto-startable", if I understood correctly. My instance, however, does not want to start at all, as suggested by the lack of suggestion.Am I missing something? Are there any workarounds? Or did I stumble onto something unseen?