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

Cannot start samba. Cannot start bootstrap #1181

Closed
conrad82 opened this Issue Feb 21, 2016 · 11 comments

Comments

Projects
None yet
4 participants
@conrad82

conrad82 commented Feb 21, 2016

Hi,

I am unable to run samba. It worked right after install, but it does not work any more. I believe it is a similar problem I have seen in other issues. Help?

Rockstor was installed using the ISO on the web page. When samba stopped working the first time, I tried reinstalling rockstor again (using a new download and usb install disk of the ISO on web page). Samba worked for a few days, presumably to a reboot or after activating auto-update.

I have tried to install the test version, but it did not change anything.

This is the error message I get from the shell:

[root@nas_sn17 ~]# /opt/rockstor/bin/bootstrap BTRFS device scan complete Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded

running systemctl:
[root@nas_sn17 ~]# systemctl status rockstor-bootstrap -l ● rockstor-bootstrap.service - Rockstor bootstrapping tasks Loaded: loaded (/etc/systemd/system/rockstor-bootstrap.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2016-02-21 09:20:13 CET; 5h 55min ago Process: 22819 ExecStart=/opt/rockstor/bin/bootstrap (code=exited, status=1/FAILURE) Main PID: 22819 (code=exited, status=1/FAILURE)

Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 bootstrap[22819]: Max attempts(15) reached. Connection errors persist. Failed to bootstrap. Error: Internal Server Error: No JSON object could be decoded Feb 21 09:20:13 nas_sn17 systemd[1]: rockstor-bootstrap.service: main process exited, code=exited, status=1/FAILURE Feb 21 09:20:13 nas_sn17 systemd[1]: Failed to start Rockstor bootstrapping tasks. Feb 21 09:20:13 nas_sn17 systemd[1]: Unit rockstor-bootstrap.service entered failed state. Feb 21 09:20:13 nas_sn17 systemd[1]: rockstor-bootstrap.service failed.

I tried this after over 1 day of uptime, so it is not a bootup problem (which I have seen in other issues).

[root@nas_sn17 ~]# uptime 15:16:23 up 1 day, 6:47, 1 user, load average: 0.18, 0.13, 0.08

@schakrava schakrava added the bug label Feb 28, 2016

@schakrava schakrava added this to the Kilauea Iki milestone Feb 28, 2016

@schakrava schakrava self-assigned this Feb 28, 2016

@schakrava

This comment has been minimized.

Member

schakrava commented Feb 29, 2016

Thanks for reporting this issue. Random question, but may be related. Do you still have this issue? If so, how does your Storage -> Disks screen look like? Are there any entries with long disk names with recycle bin icon next to their name? A screenshot would be great if possible.

@conrad82

This comment has been minimized.

conrad82 commented Mar 1, 2016

Hi,

thank you for your reply!

yes I still have the issue and can confirm it happens after first reboot. I tried reinstalling and rebooting to confirm. I have now installed Rockstor again and not rebooted so at the time samba is working

You are right, there is one with a long name. There is no recycle bin icon. However, I have not rebooted yet if that is relevant.

In case it is relevant, I originally had 3 hdd's for the pool.
I then added a new one (sdb) and removed two older ones after the balancing completed.

Let me know if there is some more information i could provide that could help resolving this issue

image

@schakrava

This comment has been minimized.

Member

schakrava commented Mar 28, 2016

Sorry for the late reply, but any chance you could e-mail the logs (/opt/rockstor/var/log) to support@rockstor.com?

schakrava added a commit to schakrava/rockstor-core that referenced this issue Mar 28, 2016

Make Pool mouting logic more robust. rockstor#1181
Try by-label and then by each device in the set. log and throw
appropriate exceptions to communicate clearly.

schakrava added a commit that referenced this issue Mar 28, 2016

Merge pull request #1234 from schakrava/1181_part1
Make Pool mouting logic more robust. #1181
@conrad82

This comment has been minimized.

conrad82 commented Apr 2, 2016

Hi,

error logs have been sent to support@rockstor.com. Apr 2, 2016, 8:38 AM (Central European Time)

@schakrava

This comment has been minimized.

Member

schakrava commented Apr 3, 2016

Hello @conrad82 . The logs were very helpful. The bug is being triggered because of usage calculation for a phantom share. Fortunately, it's been fixed in 0ce536f already. Looks like you are running stable updates, so you'll get the fix with next update. We are planning to release it in next 1-2 weeks.

I'll keep this issue open until we confirm that's the only bug effecting you. Let's sync up post release of 3.8-13.

@conrad82

This comment has been minimized.

conrad82 commented Apr 7, 2016

Glad to hear it! I will let you know how -13 works out when it arrives

@peterdenhaan

This comment has been minimized.

peterdenhaan commented Apr 11, 2016

@schakrava wanted to add that I just had a problem with identical presentation to this one, and quickly patching in 0ce536f did indeed fix it.

In my case, the root cause was rockstor_rockstor running out of metadata space. I'm running quite a few docker containers and their volumes are probably making heavy metadata demands. The pool wouldn't even rebalance for lack of space. I got out of that corner by temporarily adding a flash drive to the pool. Once the filesystem was working again, I ran into the above error. I suspect some of the qgroup data got out of whack.

@schakrava

This comment has been minimized.

Member

schakrava commented Apr 20, 2016

Fixed by #1234

@schakrava schakrava closed this Apr 20, 2016

@conrad82

This comment has been minimized.

conrad82 commented Apr 22, 2016

3.8-13 indeed seems to have fixed the problem!

Good job!

@holmesb

This comment has been minimized.

holmesb commented May 15, 2016

I'm having this issue with 3.8-13, so it isn't closed.

[root@nas03 ~]# systemctl -l status rockstor-bootstrap.service
● rockstor-bootstrap.service - Rockstor bootstrapping tasks
Loaded: loaded (/etc/systemd/system/rockstor-bootstrap.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2016-05-15 15:51:38 BST; 2h 42min ago
Process: 13070 ExecStart=/opt/rockstor/bin/bootstrap (code=exited, status=1/FAILURE)
Main PID: 13070 (code=exited, status=1/FAILURE)
May 15 15:51:38 nas03 bootstrap[13070]: Exception occured while bootstrapping. This could be because rockstor.service is still starting up. will wait 2 seconds and try again. Exception: Internal Server Error: No JSON object could be decoded
...

image
I have emailed my logs to support@rockstor.com

@holmesb

This comment has been minimized.

holmesb commented May 21, 2016

When attempting to start the bootstrap service, rockstor logs showed a "Not found" error when running command btrfs qgroup show /mnt2/rockstor_rockstor
So I ran command btrfs quota enable /mnt2/rockstor_rockstor
Now samba and the rockstor-bootstrap.service start successfully! :-)

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