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 (hubble): "No Data" #2094

Closed
liiiiiiii99 opened this issue Jun 25, 2024 · 11 comments
Closed

bug (hubble): "No Data" #2094

liiiiiiii99 opened this issue Jun 25, 2024 · 11 comments
Labels
s-ready Ready to be picked up t-bug A fix for a bug with the current system

Comments

@liiiiiiii99
Copy link

What is the bug?
I installed it using this command curl -sSL https://download.thehubble.xyz/bootstrap.sh | bash but it is showing "No Data".

How can it be reproduced? (optional)
N/A

Additional context (optional)
For context, I'm using WSL and Docker Desktop. and on Docker, here's the last line 2024-06-25 19:15:03 {"message":"Please wait... This may take several minutes\n","timestamp":"2024-06-25T11:15:03.502Z","type":"out","process_id":0,"app_name":"hubble"} and it seems to just be repeating it after a few minutes.

image

@github-actions github-actions bot added the s-triage Needs to be reviewed, designed and prioritized label Jun 25, 2024
@liiiiiiii99
Copy link
Author

And i think it restart automatically for some reason after showing the
2024-06-25 19:15:03 {"message":"Please wait... This may take several minutes\n","timestamp":"2024-06-25T11:15:03.502Z","type":"out","process_id":0,"app_name":"hubble"}

a few minutes it shows

2024-06-25 19:16:21 2024-06-25T11:16:21: PM2 log: App name:hubble id:0 disconnected
2024-06-25 19:16:21 2024-06-25T11:16:21: PM2 log: App [hubble:0] exited with code [1] via signal [SIGINT]
2024-06-25 19:16:21 2024-06-25T11:16:21: PM2 log: 0 application online, retry = 3
2024-06-25 19:16:23 2024-06-25T11:16:23: PM2 log: 0 application online, retry = 2
2024-06-25 19:16:25 2024-06-25T11:16:25: PM2 log: 0 application online, retry = 1
2024-06-25 19:16:27 2024-06-25T11:16:27: PM2 log: 0 application online, retry = 0
2024-06-25 19:16:27 2024-06-25T11:16:27: PM2 log: Stopping app:hubble id:0```

and just repeat in a loop.  for some reason

@youngatsavings1
Copy link

same issue to me

@youngatsavings1
Copy link

hubble-1 | 2024-06-25T21:07:01: PM2 log: App name:hubble id:0 disconnected
hubble-1 | 2024-06-25T21:07:01: PM2 log: App [hubble:0] exited with code [1] via signal [SIGINT]
hubble-1 | 2024-06-25T21:07:03: PM2 log: 0 application online, retry = 3
hubble-1 | 2024-06-25T21:07:05: PM2 log: 0 application online, retry = 2
hubble-1 | 2024-06-25T21:07:07: PM2 log: 0 application online, retry = 1
hubble-1 | 2024-06-25T21:07:09: PM2 log: 0 application online, retry = 0
hubble-1 | 2024-06-25T21:07:09: PM2 log: Stopping app:hubble id:0
hubble-1 | 2024-06-25T21:07:09: PM2 log: pid=29 msg=process killed
hubble-1 | 2024-06-25T21:07:09: PM2 log: PM2 successfully stopped
hubble-1 exited with code 0

@BlunderChia
Copy link

Same issue here, has anyone found a solution to this?

@liiiiiiii99
Copy link
Author

Not yet sadly. :(

@BlunderChia
Copy link

Probably it is because of pm2 log rotation. Dev team should build a workaround to the installation script.

@kingo233
Copy link

kingo233 commented Jul 2, 2024

Same issue, anyone can help me?

@prasadchinthala01
Copy link

facing same issu plz help
hubble 1

@youngatsavings1
Copy link

Bro i found solution just reinstall your vps and make sure you are using ubuntu 24.04 and let me know if it works. All the best

@sds sds mentioned this issue Jul 9, 2024
@sds
Copy link
Member

sds commented Jul 9, 2024

Hey everyone, we are aware of an issue where if your internet connection is interrupted at some point during the process, the snapshot can become corrupted and then the hubs end up in a restart loop.

If you see something like:

db.internal_error/Corruption: Corruption: IO error: No such file or directory: While open a file for random read: .rocks/rocks.hub._default/004134.sst: No such file or directory The file .rocks/rocks.hub._default/MANIFEST-000005 may be corrupted.

...in your logs, this is likely what's affecting you.

We're tracking this issue in #2042.

@sds sds added t-bug A fix for a bug with the current system s-ready Ready to be picked up and removed s-triage Needs to be reviewed, designed and prioritized labels Jul 9, 2024
@sanjayprabhu
Copy link
Contributor

This should be fixed by #2236, included in the latest release (1.14.3).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s-ready Ready to be picked up t-bug A fix for a bug with the current system
Projects
None yet
Development

No branches or pull requests

7 participants