The terminal shows “systemctl: Unit nslcd.service could not be found”
the different widgets on the dashboard show on the one hand only 12,9GB being used on the other hand still the correct 900GB being used out of the 7TB share
Please - can you help me?!
What has happened to my system?
My last backup was done a few months ago
Fu**, I had in mind to run another backup after New Year…
Editing / problem partly solved: Samba Service was OFF due to a normal reboot? strange
I can access my files, BUT Rock-ons can’t be switched on - same error “nslcd.service could not be found”
Any ideas how to get Rock-ons again staying enabled?
@glenngould Hey there, glad you were able to figure out your data “problem”. Do you have ssh/command line access to your server?
If not, just click on ‘System Shell’ under the rock-ons tab:
Then type, sudo docker ps and see if anything outputs. If you weren’t aware, Docker containers are your Rock-On plugins. Just re-branded for Rockstor theme consistency.
Here’s a sample output:
[1:0:4][root@rockstor:pts/0][~]
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ef6503e10b29 rocketchat/rocket.chat "node main.js" 5 months ago Up 18 hours 0.0.0.0:3000->3000/tcp rocketchat
4cffd3e72328 mongo "/entrypoint.sh mongo" 5 months ago Up 18 hours 27017/tcp mongodb.rocketchat
8ca614e38742 linuxserver/plex "/sbin/my_init" 5 months ago Up 18 hours plex-linuxserver.io
3065a6cefc34 linuxserver/headphones "/sbin/my_init" 5 months ago Up 18 hours 0.0.0.0:8181->8181/tcp linuxserver-headphones
a90e1c05443a linuxserver/couchpotato "/sbin/my_init" 5 months ago Up 18 hours 0.0.0.0:5050->5050/tcp couchpotato
7c360ccfe37b linuxserver/sickrage "/sbin/my_init" 5 months ago Up 18 hours 0.0.0.0:8081->8081/tcp sickrage
24cdfb8793ae linuxserver/sabnzbd "/sbin/my_init" 5 months ago Up 18 hours 0.0.0.0:9090->9090/tcp, 0.0.0.0:8084->8080/tcp sabnzb
524d1f34889c owncloud "/entrypoint.sh apach" 5 months ago Up 18 hours 0.0.0.0:8085->80/tcp, 0.0.0.0:8085->80/udp owncloud-official
@glenngould Yep, that means your docker service isn’t running and probably is hanging on some dependent modules.
First off, based on your shell status, you’re running as root.
I’ve tried “sudo docker ps” but no output…
So you don’t need sudo (superuser do). You can just run the commands below without that.
Try this:
systemctl --failed
It should output all the failed units within systemd:
[1:0:2][root@rockstor:pts/0][~]
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● kdump.service loaded failed failed Crash recovery kernel arming
kdump.service “failing” is normal and will only activate when trying to capture a kernel dump, which you aren’t experiencing at the moment.
The Docker / Rockstor services rely on the rockstor.service and the rockstor-bootstrap.service, so if these are failing then you have big problems. But since you’re able to get to the dashboard I think you’re okay here.
There are 2 sysd units that should be running related to Docker / Rock-ons:
● docker.socket - Docker Socket for the API
Loaded: loaded (/etc/systemd/system/docker.socket; disabled; vendor preset: disabled)
Active: active (running) since Wed 2017-01-11 17:20:23 MST; 1 day 6h ago
Listen: /var/run/docker.sock (Stream)
And
● docker.service - Docker Application Container Engine
Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2017-01-11 17:20:38 MST; 1 day 6h ago\
These both should be Active status. To check these individually, run this:
systemctl status docker.socket systemctl status docker.service
Here is the log which tells us a problem with the bootstrap service
[root@rockstor ~]# journalctl -xe
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Exception occured while bootstrapping.
Jan 13 10:08:15 rockstor bootstrap[8616]: Max attempts(15) reached. Connection e
Jan 13 10:08:15 rockstor systemd[1]: Received SIGCHLD from PID 8616 (bootstrap).
Jan 13 10:08:15 rockstor systemd[1]: Child 8616 (bootstrap) died (code=exited, s
Jan 13 10:08:15 rockstor systemd[1]: Child 8616 belongs to rockstor-bootstrap.se
Jan 13 10:08:15 rockstor systemd[1]: rockstor-bootstrap.service: main process ex
Jan 13 10:08:15 rockstor systemd[1]: rockstor-bootstrap.service changed start ->
Jan 13 10:08:15 rockstor systemd[1]: Job rockstor-bootstrap.service/start finish
Jan 13 10:08:15 rockstor systemd[1]: Failed to start Rockstor bootstrapping task
Jan 13 10:08:15 rockstor systemd[1]: Sent message type=signal sender=n/a destina
Jan 13 10:08:15 rockstor systemd[1]: Sent message type=signal sender=n/a destina
Jan 13 10:08:15 rockstor systemd[1]: Job docker.service/start finished, result=d
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 13 10:08:15 rockstor polkitd[2127]: Unregistered Authentication Agent for un
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=or
lines 979-1001/1001 (END)
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: 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
Jan 13 10:08:15 rockstor bootstrap[8616]: Max attempts(15) reached. Connection errors persist. Failed to bootstrap. Error: [‘Internal Server Error: No JSON object could be decoded’]
Jan 13 10:08:15 rockstor systemd[1]: Received SIGCHLD from PID 8616 (bootstrap).
Jan 13 10:08:15 rockstor systemd[1]: Child 8616 (bootstrap) died (code=exited, status=1/FAILURE)
Jan 13 10:08:15 rockstor systemd[1]: Child 8616 belongs to rockstor-bootstrap.service
Jan 13 10:08:15 rockstor systemd[1]: rockstor-bootstrap.service: main process exited, code=exited, status=1/FAILURE
Jan 13 10:08:15 rockstor systemd[1]: rockstor-bootstrap.service changed start -> failed
Jan 13 10:08:15 rockstor systemd[1]: Job rockstor-bootstrap.service/start finished, result=failed
Jan 13 10:08:15 rockstor systemd[1]: Failed to start Rockstor bootstrapping tasks.
Jan 13 10:08:15 rockstor systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=13 reply_cookie=0 error=n/a
Jan 13 10:08:15 rockstor systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=6990 reply_cookie=0 error=n/a
Jan 13 10:08:15 rockstor systemd[1]: Job docker.service/start finished, result=dependency
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=6990 reply_cookie=0 error=n/a
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=6991 reply_cookie=0 error=n/a
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1/unit/rockstor_2dbootstrap_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged co
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/org/freedesktop/systemd1/unit/rockstor_2dbootstrap_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged co
Jan 13 10:08:15 rockstor polkitd[2127]: Unregistered Authentication Agent for unix-process:8816:7782387 (system bus name :1.113, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 13 10:08:15 rockstor systemd-logind[1814]: Got message type=signal sender=org.freedesktop.DBus destination=n/a object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameOwnerChanged cookie=239 reply_cookie=0 error=n/a
~
I’ve tried again to enable Rock-ons which ended in the following message via a pop-up “Unknown internal error doing a POST to /api/sm/services/docker/start”
[root@rockstor ~]# systemctl restart rockstor-bootstrap.service
Job for rockstor-bootstrap.service failed because the control process exited with error code. See "systemctl status rockstor-bootstrap.service" and "journalctl -xe" for details.
Running “systemctl status rockstor-bootstrap.service” as stated above shows the following
● rockstor-bootstrap.service - Rockstor bootstrapping tasks
Loaded: loaded (/etc/systemd/system/rockstor-bootstrap.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-01-16 07:21:09 CET; 26min ago
Process: 1289 ExecStart=/opt/rockstor/bin/bootstrap (code=exited, status=1/FAILURE)
Main PID: 1289 (code=exited, status=1/FAILURE)
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: 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']
Jan 16 07:21:09 rockstor bootstrap[1289]: Max attempts(15) reached. Connection errors persist. Failed to bootstrap. Error: ['Internal Server Error: No JSON object could be decoded']
and “journalctl -xe” this
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=:1
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=or
Jan 16 07:21:09 rockstor polkitd[2127]: Unregistered Authentication Agent for un
Jan 16 07:21:15 rockstor udevadm[1709]: calling: info
Jan 16 07:21:15 rockstor udevadm[1710]: calling: info
Jan 16 07:21:15 rockstor udevadm[1711]: calling: info
Jan 16 07:21:15 rockstor udevadm[1712]: calling: info
Jan 16 07:21:16 rockstor udevadm[1731]: calling: info
Jan 16 07:21:16 rockstor udevadm[1732]: calling: info
Jan 16 07:21:16 rockstor udevadm[1733]: calling: info
Jan 16 07:21:16 rockstor udevadm[1738]: calling: info
Jan 16 07:22:22 rockstor udevadm[2269]: calling: info
Jan 16 07:22:22 rockstor systemd[1]: Got notification message for unit systemd-j
Jan 16 07:22:22 rockstor systemd[1]: systemd-journald.service: Got notification
Jan 16 07:22:22 rockstor systemd[1]: systemd-journald.service: got WATCHDOG=1
Jan 16 07:22:22 rockstor udevadm[2270]: calling: info
Jan 16 07:22:22 rockstor udevadm[2271]: calling: info
Jan 16 07:22:22 rockstor udevadm[2272]: calling: info
Jan 16 07:22:22 rockstor udevadm[2293]: calling: info
Jan 16 07:22:22 rockstor udevadm[2294]: calling: info
Jan 16 07:22:22 rockstor udevadm[2295]: calling: info
Jan 16 07:22:22 rockstor udevadm[2298]: calling: info
lines 979-1001/1001 (END)
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=:1.1 destination=n/a object=/
Jan 16 07:21:09 rockstor systemd-logind[1814]: Got message type=signal sender=org.freedesktop.DBus destinat
Jan 16 07:21:09 rockstor polkitd[2127]: Unregistered Authentication Agent for unix-process:1283:32698025 (s
Jan 16 07:21:15 rockstor udevadm[1709]: calling: info
Jan 16 07:21:15 rockstor udevadm[1710]: calling: info
Jan 16 07:21:15 rockstor udevadm[1711]: calling: info
Jan 16 07:21:15 rockstor udevadm[1712]: calling: info
Jan 16 07:21:16 rockstor udevadm[1731]: calling: info
Jan 16 07:21:16 rockstor udevadm[1732]: calling: info
Jan 16 07:21:16 rockstor udevadm[1733]: calling: info
Jan 16 07:21:16 rockstor udevadm[1738]: calling: info
Jan 16 07:22:22 rockstor udevadm[2269]: calling: info
Jan 16 07:22:22 rockstor systemd[1]: Got notification message for unit systemd-journald.service
Jan 16 07:22:22 rockstor systemd[1]: systemd-journald.service: Got notification message from PID 1138 (WATC
Jan 16 07:22:22 rockstor systemd[1]: systemd-journald.service: got WATCHDOG=1
Jan 16 07:22:22 rockstor udevadm[2270]: calling: info
Jan 16 07:22:22 rockstor udevadm[2271]: calling: info
Jan 16 07:22:22 rockstor udevadm[2272]: calling: info
Jan 16 07:22:22 rockstor udevadm[2293]: calling: info
Jan 16 07:22:22 rockstor udevadm[2294]: calling: info
Jan 16 07:22:22 rockstor udevadm[2295]: calling: info
Jan 16 07:22:22 rockstor udevadm[2298]: calling: info
I want to thank you @exelan for your support so far. I’m not sure how to move on and get this solved, so I ask you to possible comment on @suman or @Flyer or @phillxnet - who could support best to get this Rock-ons service again up and running on my machine?
Maybe the upcoming next release 3.9.0 and the upgrade itself will solve this issue (?) - I’m have my doubts
Or is the only solution to do a fresh/new installation of Rockstor (last option to me)
Thank you commenting or directing where to go with this.
Sorry for the delay, I was on vacation and tried to avoid anything digital. So to answer your first reply:
That’s what I figured, so there must be some issue with the binaries themselves in /bin. The Rock-ons should be secondary to your bigger problem of rockstor-bootstrap.service failing to start, this is a serious deal that will make the Rock-on plugins moot in the bigger picture of your system. I’m sure @phillxnet, @Flyer, and @suman would tend to agree.
What is the current version of your Rockstor build?:
Share/Pool : actually Pool usage computes snapshots and metadata too, while share usage is wrong (well, right and wrong: it reports only current data, not considering snapshots data -> open issue, working to patch it )
nslcd.service -> nss & samba so 1) check you’re running Rockstor latest version (thanks @exelan for great support!) 2)IMPORTANT: have yum update to get latest samba&other packages fixing major bug related nss/name resolving (check around forum posts, full of this)
Some basic checking: systemctl -l and service name (ex systemctl -l docker) returns more infos systemctl show and service name (ex systemctl show docker) returns other infos (ex ExecStart to check what docker runs on startup)
The Rockstor release/version I’m using is 3.8.16-1 stable as stated in the heading of this thread.
A few minutes ago (before I’ve seen your reply) I thought about trying the latest testing version in order to see if there is any difference - no, no improvments. System is still on 3.8.16-8 now.
Another thing I’ve noted, but also somehow clear with all the troubles we see on my machine…also the bootstrap service is showing up being disabled and can’t be turned on, like Rock-ons.
thanks for your support - no problem for missing arguments…
systemctl status -l rockstor-bootstrap
● rockstor-bootstrap.service - Rockstor bootstrapping tasks
Loaded: loaded (/etc/systemd/system/rockstor-bootstrap.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-01-20 11:00:10 CET; 1h 25min ago
Process: 15353 ExecStart=/opt/rockstor/bin/bootstrap (code=exited, status=1/FAILURE)
Main PID: 15353 (code=exited, status=1/FAILURE)
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: 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']
Jan 20 11:00:10 rockstor bootstrap[15353]: Max attempts(15) reached. Connection errors persist. Failed to bootstrap. Error: ['Internal Server Error: No JSON object could be decoded']
Ok,
this doesn’t give us more info, but we can debug it: boostrap service runs scripts/bootstrap.py and your boostrap fails after 15 attempts, so we’re failing here:
My idea, considering bootstrap.pytry...except code
I assume APIWrapper call to network is ok and commands/bootstrap failing, with bootstrap command. Can you provide rockstor logs with cat /opt/rockstor/var/log/rockstor.log ? fortunately bootstrap under commands view has lot of logging helping us