Gerald,
Thank you for your answer.
Double checking my self, sry. This is my understanding of shut down process, is
this ok?
# Stop cron job.
root@myserver:/# /etc/init.d/cron stop
# Check cron job status.
root@myserver:/# /etc/init.d/cron status
[FAIL] cron is not running ... failed!
# Stop OTRS Scheduler.
root@myserver:/# /opt/otrs/bin/otrs.Scheduler.pl -a stop
# Check OTRS status.
root@myserver:/# /opt/otrs/bin/otrs.Scheduler.pl -a status
Not Running!
# Stop Apache Web server.
root@myserver:/# service apache2 graceful-stop
[ ok ] Stopping web server: apache2.
# Check Apache Web server status.
root@myserver:/# service apache2 status
Apache2 is NOT running.
# Stop MySQL.
root@myserver:/# service mysql stop
[ ok ] Stopping MySQL database server: mysqld.
# Check MySQL status.
root@myserver:/# service mysql status
[info] MySQL is stopped..
# Proceed with Debian shut down or restart.
Pošiljatelj: Gerald Young
Poslano: utorak, 25. studenog 2014. 19:20
Primatelj: otrs@otrs.org
It's not really a case of proper order of shutdown as much as properly shutting
down.
In theory, you'll want to stop or allow to complete any email fetching that is
ongoing, and stop all cron jobs, and OTRS scheduler, then apache, then MySQL
(if you really must stop MySQL or apache).
It's a web app, so much of what is happening happens within a few seconds, as
transactions to the SQL database and web lookups. Since MySQL is the most
important part of the data equation, but doesn't *generally* need to ever shut
down, aside from upgrades/reboot, you'll simply find that the app won't work if
mysql and apache aren't working, and apache may not work (well) if mysql isn't
working/on. The OTRS scheduler and scripts are not constantly running, so they
can be stopped or started at whim, and they themselves don't stop or start
their components when they are reloaded. (That is, a mail fetch will happen as
scheduled and will continue to finish, if it's already started, even if the
cron job is deleted. The mail fetch won't happen again until the cron job's
criteria is met.)
On Tue, Nov 25, 2014 at 12:10 PM, <amatija...@gmail.com> wrote:
Hi,
What is the proper way to shut down/start OTRS 3.3.x system (installed from
source) on Debian 7.
Example of what I am trying to accomplish:
"
linux:~ # rcotrs restart-force
Shutting down OTRS
Disable /opt/otrs/bin/otrs.PostMaster.pl ... done.
no crontab for otrs
Shutting down cronjobs ... failed!
Shutting down OTRS (completely)
Shutting down Apache ... done.
Shutting down MySQL ... done.
done
Starting OTRS (completely)
Starting Apache ... done.
Starting MySQL ... done.
Starting OTRS
Checking Apache ... done.
Checking MySQL ... done.
Checking database connect... (It looks Ok!).
Enable /opt/otrs/bin/otrs.PostMaster.pl ... done.
Checking otrs spool dir... done.
Creating cronjobs (source /opt/otrs/var/cron/*) ... done.
-->> http://linux.example.com/otrs/index.pl <<--
done
done
linux:~ #
"
Thank you.
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
