Octoprint Daemon issues


#1

Hi
I have followed the instructions to setup OctoPrint as a Linux Service Daemon.
Seems to work well. I can start, stop and restart the daemon, no problems.

However when I try to connect to OctoPrint, I can't. I get site down or something similar.

Note:
When I stop the service daemon, then start OctoPrint from the Linux command line manually
(no Daemon), I can connect without any problems.

Any ideas? ACL problem maybe?
Michael B


#2

No way to tell really without logs :wink:


#3

Logs? Need more information. Which logs do I need to locate and upload?


#4

See here


#5

Thanks Gina.
Now we're getting somewhere.
I truncated the log file and started the service daemon.
Nothing was logged, even though on the command line, it looked like it worked.
I shutdown the service daemon, again nothing was logged. Again the command line looked Okay.
I started octoprint manually (which works) and it's entire startup was logged.
I can only conclude that the service daemon is in fact not working.
Now I know that, I just need to figure out why.
Michael B.


#6

Hi Gina
The /etc/init.d/octoprint file is a straight copy of octoprint.init
I don't know if that's kosher for Knoppix 8.1 I would have thought it was.
The /etc/default/octoprint file is as per below:
Maybe the problem is in the defaults, although I'm not seeing it.

# Configuration for /etc/init.d/octoprint

# The init.d script will only run if this variable non-empty.
OCTOPRINT_USER=knoppix

# base directory to use
BASEDIR=/home/knoppix/.octoprint

# configuration file to use
CONFIGFILE=/home/knoppix/.octoprint/config.yaml

# On what port to run daemon, default is 5000
PORT=5000

# Path to the OctoPrint executable, you need to set this to match your installation!
DAEMON=/home/knoppix/octoprint/venv/bin/octoprint

# What arguments to pass to octoprint, usually no need to touch this
DAEMON_ARGS=serve

# Umask of files octoprint generates, Change this to 000 if running octoprint as its own, separate user
UMASK=022

# Process priority, 0 here will result in a priority 20 process.
# -2 ensures Octoprint has a slight priority over user processes.
NICELEVEL=-2

# Should we run at startup?
START=yes

#7

https://github.com/foosel/OctoPrint/blob/master/scripts/octoprint.default#L19 your DAEMON_ARGS appears to be different to what's in OctoPrint's own init config.

also octoprint.init is totally different to what you've posted https://github.com/foosel/OctoPrint/blob/master/scripts/octoprint.init what you've posted seems to be the contents of octoprint.default

edit: oops I misread your post, ignore my second comment, first comment still stands though, I think you're passing the wrong DAEMON_ARGS parameters.


#8

I'm sorry, I have no idea of Knoppix (it must be close to 15 years now since I last used it), so I'm really not qualified to help here I fear. All I can tell you is that stuff works fine under Debian and Raspbian.


#9

Hi Gina.
That's OK.
Before this month, the last time I used Linux, was back in the mid 1990s on Slackware 3.
My brain is somewhat rusty, but picking things up.
Michael B.
p,s. Knoppix is based on Debian.


#10

Thanks.
Good pick up.
I'll play around with that tonight.
Michael B.


#11

Thanks PythonAteMyPearl
The Daemon Args were the problem. Great pickup.
The Daemon now works
Michael B.