SOLVED WARNING: no shebang line in /usr/bin/cpuset

[nello]

I manually upgraded CrashPlan to ver 4.5 using the directions provided by @mastax

It seems to be working, but I get an error when I start the crashplan service:

Code:

root@crashplan_1:/ # service crashplan start
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Starting CrashPlan Engine ... Using standard startup
OK
root@crashplan_1:/ #

What is this warning trying to tell me and how do I eliminate it?

Thank you.

- nello

 

[Robert Trevellyan]

https://en.wikipedia.org/wiki/Shebang_(Unix)

So the line identifying which interpreter to use is probably missing from the script.

 

[depasseg]

https://forums.freenas.org/index.php?threads/crashplan-plugin.15366/page-5#post-105945

 

[nello]

https://forums.freenas.org/index.php?threads/crashplan-plugin.15366/page-5#post-105945

Thank you for the pointer to @mstinaff 's instructions!

I tried the recommended command and it's throwing an error about an non-existant process:

Code:

root@crashplan_1:/ # service crashplan status
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
crashplan is not running.
root@crashplan_1:/ # /usr/bin/cpuset -l0 /usr/local/share/crashplan/bin/CrashPlanEngine restart
Restarting CrashPlan Engine ... Stopping CrashPlan Engine ... /usr/pbi/crashplan -amd64/share/crashplan/bin/CrashPlanEngine: line 145: kill: (17982) - No such process
OK
Starting CrashPlan Engine ... Using standard startup
OK
root@crashplan_1:/ # ELF binary type "0" not known.

root@crashplan_1:/ # ls /proc
16233 16357 16361 16601 17304 18113 curproc
root@crashplan_1:/ #

Do you have any idea why the CrashPlan service won't start up? It's been running fine for a month since I upgraded it to ver 4.7. In preparation for upgrading to FreeNAS 9.10, I updated several OTHER Jails (but not CrashPlan) with the commands below and rebooted the server. Interestingly, none of my Jails started on their own, but I was able to start the other three and they seem to be working.

Code:

pkg update && pkg upgrade
portsnap fetch update
portupgrade -a

Thank you.

- nello

 

[depasseg]

Sorry, but I've conceded defeat and am patiently waiting for FreeNAS 10 and it's docker capabilities to run a virtualized CrashPlan.

 

[nello]

Sorry, but I've conceded defeat and am patiently waiting for FreeNAS 10 and it's docker capabilities to run a virtualized CrashPlan.

Nevermind. I rebooted the server and now my client can connect to the server. So, all is well ... except that the command line still reports something amiss:

Code:

root@crashplan_1:/ # service crashplan status
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
crashplan is not running.
root@crashplan_1:/ # service crashplan start
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
CrashPlan is already running with pid 5734 5821 6011 6039 6041 6066 6067 6068 60
69 7007 7049 7050 7051 7052 7053 7066 7080 7084 7085 7086 7087 7088 7089 7090 70
91 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7115 71
16 7117 7118 7119 7120 7121 7122 7124 7125 7226 7227 7228 7229 7230 7231 7232 72
37 7247 7248 7249 7250 7264 7265 7266 7407 7409 7580 7582 7603 7604
root@crashplan_1:/ #

Odd that status reports that crashplan is NOT running but start says that it IS running, eh?

The bottom line is that my client connects so I'm satisfied.

Thank you for your quick reply.

- nello