Skip to content
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

Can't run daemonded, daemon-tty, etc. on some Linux #1392

Closed
illwieckz opened this issue Oct 26, 2024 · 3 comments
Closed

Can't run daemonded, daemon-tty, etc. on some Linux #1392

illwieckz opened this issue Oct 26, 2024 · 3 comments

Comments

@illwieckz
Copy link
Member

illwieckz commented Oct 26, 2024

Can't run daemonded, daemon-tty, etc. on some Linux, here with daemonded:

Warn: Could not bind singleton socket at file:
 "/tmp/.unvanquished-server-3893AD6762EA7A4328C37822C2B8727E/socket",
 error: "No such file or directory"

It is related to the filesytem, if I use TMPDIR="$(pwd)" (and then use another filesystem than /tmp) it works.

@illwieckz
Copy link
Member Author

  • Ubuntu 20.04.6 LTS focal
  • /tmp is part of / which is mounted as ext4 defaults,relatime,lazytime,errors=remount-ro

@illwieckz
Copy link
Member Author

illwieckz commented Oct 26, 2024

With daemon-tty:

Warn: Could not bind singleton socket at file:
 "/tmp/.unvanquished-3893AD6762EA7A4328C37822C2B8727E/socket",
 error: "No such file or directory" 

@illwieckz
Copy link
Member Author

illwieckz commented Oct 26, 2024

Forget about it, logs were full and because /tmp was not a separate partition, it could not write to it.

Because I first experienced the macOS bug I then believed it was a variant of it:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants