Jump to content

Octoprint server dont run auto start when system open?


Recommended Posts

Posted

Hi i have a Orange pi lite and 3d Printer. i want use this online but i manuel therminal code is Run (~/OctoPrint/venv/bin/octoprint) its very good run but why its not auto run?

Or How i run this code when system is opening?

 

D6603 cihazımdan Tapatalk kullanılarak gönderildi

 

 

Posted

Hello my problem is octoprint server. i setup this server with this pdf document.

my image is Armbian_5.25_Orangepilite_Ubuntu_xenial_default_3.4.113_desktop

i start server manuel Termal with this code (~/OctoPrint/venv/bin/octoprint) its okey good run

why octoprint server dont auto run?

 

octoprint.pdf

Posted
4 hours ago, martinayotte said:

No !

Edit /etc/rc.local and add "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &" before the "exit 0"

 

Hi i repair but not solve . :-(

vvvvı.PNG

Posted
sevval@orangepilite:~$ sudo /etc/init.d/rc.local start
[....] Starting rc.local (via systemctl): rc.local.serviceWarning: rc.local.service changed on disk. Run 'systemctl daemon-reload' to reload units.
. ok
sevval@orangepilite:~$

this error

Posted

I don't know if "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &" for some other reasons, but the /etc/rc.local is for sure working.

 

Just to prove that, you can do "date > /tmp/lastboot.log &", and you will see that this is actually executed.

 

So, check your OctoPrint installation, maybe something wrong there ....

 

Posted
On 23.04.2017 at 5:43 AM, parrotgeek1 said:

add 

/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint &

before the line "exit 0" of /etc/rc.local

İ run This code manuel. but it receiving error.  (RC.local)

 

Hi sorry not know enough english. 

 

Posted

You ran "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint" manually and you got some errors ?

I'm not familiar with OctoPrint, but maybe you can tell here what was the error ...

 

Posted
9 hours ago, martinayotte said:

You ran "/home/YOUR_USERNAME_HERE/OctoPrint/venv/bin/octoprint" manually and you got some errors ?

I'm not familiar with OctoPrint, but maybe you can tell here what was the error ...

 

 

hi thanks but now server some give error so : its connect but not control printer 


2017-04-25 21:34:07,019 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue...
2017-04-25 21:34:07,029 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue
2017-04-25 21:34:07,034 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets...
2017-04-25 21:34:07,056 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache...
2017-04-25 21:34:07,520 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on orangepilite for SSDP
2017-04-25 21:34:07,542 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2017-04-25 21:34:07,673 - octoprint.server - INFO - Listening on http://0.0.0.0:5000
2017-04-25 21:34:07,788 - octoprint.server - INFO - Preemptively caching / (ui _default) for {'query_string': 'l10n=en', 'path': '/', 'base_url': 'http://192.168.0.149:5000/'}
2017-04-25 21:34:27,418 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104
2017-04-25 21:34:38,213 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.104
2017-04-25 21:34:38,834 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104
2017-04-25 21:35:01,705 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.104
2017-04-25 21:35:02,490 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.104

 

Posted

I don't see any errors in the above, although I'm not familiar with what OctoPrint is used to provide as output.

Is the IP address 192.168.0.104 is your printer ?

 

Posted
Just now, martinayotte said:

I don't see any errors in the above, although I'm not familiar with what OctoPrint is used to provide as output.

Is the IP address 192.168.0.104 is your printer ?

 

yes local ip

i connect laptop and phone,  

Posted
Connecting to: /dev/ttyUSB0
Changing monitoring state from 'Offline' to 'Opening serial port'
Connected to: Serial<id=0xafdedf50, open=True>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=60.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from 'Opening serial port' to 'Connecting'
Changing monitoring state from 'Connecting' to 'Offline'
Connecting to: /dev/ttyUSB0
Changing monitoring state from 'Offline' to 'Opening serial port'
Connected to: Serial<id=0xb02054d0, open=True>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=60.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from 'Opening serial port' to 'Connecting'
Recv: 4��1q�1a��\x1fq1�dlqh�9�  ��05p0��1h��W�d ���x4�p011x��R58������
Connection closed, closing down monitor
There was a timeout while trying to connect to the printer
Changing monitoring state from 'Connecting' to 'Offline'
Connection closed, closing down monitor

this octoprint Terminal log

Posted

你需要自己写一个自动启动脚本 或者用我的 

#!/bin/sh

### BEGIN INIT INFO
# Provides:          octoprint
# Required-Start:    $local_fs networking
# Required-Stop:
# Should-Start:
# Should-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: OctoPrint daemon
# Description:       Starts the OctoPrint daemon with the user specified in
#                    /etc/default/octoprint.
### END INIT INFO

# Author: Sami Olmari

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/home/pi/OctoPrint/venv/bin:/home/octoprint/OctoPrint/venv/bin
DESC="Octoprint Daemon"
NAME="Octoprint"
DAEMON=/home/octoprint/OctoPrint/venv/bin/octoprint
PIDFILE=/var/run/$NAME.pid
PKGNAME=octoprint
SCRIPTNAME=/etc/init.d/$PKGNAME
PORT=8080
DAEMON_ARGS="--port=$PORT"
UMASK=022
NICELEVEL=-2
START=yes
OCTOPRINT_USER=octoprint

# Read configuration variable file if it is present
[ -r /etc/default/$PKGNAME ] && . /etc/default/$PKGNAME

# Exit if the octoprint is not installed
[ -x "$DAEMON" ] || exit 0

# Load the VERBOSE setting and other rcS variables
[ -f /etc/default/rcS ] && . /etc/default/rcS

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

if [ -z "$START" -o "$START" != "yes" ]
then
   log_warning_msg "Not starting $PKGNAME, edit /etc/default/$PKGNAME to start it."
   exit 0
fi

if [ -z "$OCTOPRINT_USER" ]
then
    log_warning_msg "Not starting $PKGNAME, OCTOPRINT_USER not set in /etc/default/$PKGNAME."
    exit 0
fi

#
# Function to verify if a pid is alive
#
is_alive()
{
   pid=`cat $1` > /dev/null 2>&1
   kill -0 $pid > /dev/null 2>&1
   return $?
}

#
# Function that starts the daemon/service
#
do_start()
{
   # Return
   #   0 if daemon has been started
   #   1 if daemon was already running
   #   2 if daemon could not be started

   is_alive $PIDFILE
   RETVAL="$?"

   if [ $RETVAL != 0 ]; then
       start-stop-daemon --start --background --quiet --pidfile $PIDFILE --make-pidfile \
       --exec $DAEMON --chuid $OCTOPRINT_USER --user $OCTOPRINT_USER --umask $UMASK --nicelevel=$NICELEVEL \
       -- $DAEMON_ARGS
       RETVAL="$?"
   fi
}

#
# Function that stops the daemon/service
#
do_stop()
{
   # Return
   #   0 if daemon has been stopped
   #   1 if daemon was already stopped
   #   2 if daemon could not be stopped
   #   other if a failure occurred

   start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --user $OCTOPRINT_USER --pidfile $PIDFILE
   RETVAL="$?"
   [ "$RETVAL" = "2" ] && return 2

   rm -f $PIDFILE

   [ "$RETVAL" = "0"  ] && return 0 || return 1
}

case "$1" in
  start)
   [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
   do_start
   case "$?" in
      0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
      2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
   esac
   ;;
  stop)
   [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
   do_stop
   case "$?" in
      0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
      2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
   esac
   ;;
  restart)
   log_daemon_msg "Restarting $DESC" "$NAME"
   do_stop
   case "$?" in
     0|1)
      do_start
      case "$?" in
         0) log_end_msg 0 ;;
         1) log_end_msg 1 ;; # Old process is still running
         *) log_end_msg 1 ;; # Failed to start
      esac
      ;;
     *)
        # Failed to stop
      log_end_msg 1
      ;;
   esac
   ;;
  *)
   echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
   exit 3
   ;;
esac

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines