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

[Bug]: Fluvio cluster fails to start on Arch Linux and Debian #3862

Closed
drc-infinyon opened this issue Feb 12, 2024 · 5 comments
Closed

[Bug]: Fluvio cluster fails to start on Arch Linux and Debian #3862

drc-infinyon opened this issue Feb 12, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@drc-infinyon
Copy link
Contributor

What happened
Fluvio cluster fails to start on ArchLinux and Debian

Expected behavior
fluvio cluster start should start a local cluster

Describe the setup

  • Installed latest version of fluvio and fvm - 0.11.4
  • What version of Fluvio are you using? fluvio version

How to reproduce it (as minimally and precisely as possible)
Steps to reproduce the behavior:

  1. Run the command 'fluvio cluster start'

Log output

javi@nasa ~> fluvio cluster start
📝 Running pre-flight checks
    ✅ Local Fluvio is not installed
🎉 All checks passed!
✅ Local Cluster initialized
👤 Profile set
✅ SC Launched
🤖 Starting SPU: (1/1) /                                                                                                                          🤖 Starting SPU: (1/1) /                                                                                                                          
🤖 Starting SPU: (1/1) \                                                                                                                          2024-02-12T14:14:28.238181Z ERROR fluvio_cluster::start::local: waited too long: 300 secs, bailing out
An unknown error occurred: not able to provision:1 spu in 300 secs

Depending on your setup, here's how you can get the logs:

  • For a local Fluvio installation on Mac:
    • Run cat /usr/local/var/log/fluvio/flv_sc.log for SC logs
    • Run cat /usr/local/var/log/fluvio/spu_log_XXXX.log for each SPU
      • E.g. when running 1 SPU, there will be spu_log_5001.log
  • For a Fluvio installation on Minikube:
    • Run kubectl logs fluvio-sc for SC logs
    • Run kubectl logs fluvio-spg-main-X for each SPU

Environment (please complete the following information):
OS: [e.g. Linux, Mac]

Linux nasa 6.7.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10 +0000 x86_64 GNU/Linux

cargo 1.75.0 (1d8b05cdd 2023-11-20)

Additional context
Add any other context about the problem here.

@drc-infinyon drc-infinyon added the bug Something isn't working label Feb 12, 2024
@javihernant
Copy link

Hi! I originally reported this issue through fluvio discord server. I'm attaching both flv_sc.log and spu_log_XXXX.log logs.
flv_sc.log
spu_log_5001.log

@digikata
Copy link
Contributor

digikata commented Feb 12, 2024

It looks like we're using localhost in a number of places and it's dns is not resolving on this system. Another fluvio developer w/ Arch does not have a localhost hosts file, but their localhost does resolve.

@javihernant
Copy link

I confirm that was the issue!

@digikata
Copy link
Contributor

Filed this issue for longer - med term improvement of defaults for this bug. #3866

@digikata
Copy link
Contributor

@javihernant Thanks for confirming! Since there is a pretty straightforward workaround, I will close this issue and we'll work in a deeper resolution in 3866.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants