Re: [MASSMAIL]Arranque automático

Sospecho que el problema puede venir por este lado, pero el script que uso
es el del contrib que si inicializa las variables, copio a continuación el
script:

#! /bin/sh

# chkconfig: 2345 98 02
# description: PostgreSQL RDBMS

# This is an example of a start/stop script for SysV-style init, such
# as is used on Linux systems. You should edit some of the variables
# and maybe the 'echo' commands.
#
# Place this file at /etc/init.d/postgresql (or
# /etc/rc.d/init.d/postgresql) and make symlinks to
# /etc/rc.d/rc0.d/K02postgresql
# /etc/rc.d/rc1.d/K02postgresql
# /etc/rc.d/rc2.d/K02postgresql
# /etc/rc.d/rc3.d/S98postgresql
# /etc/rc.d/rc4.d/S98postgresql
# /etc/rc.d/rc5.d/S98postgresql
# Or, if you have chkconfig, simply:
# chkconfig --add postgresql
#
# Proper init scripts on Linux systems normally require setting lock
# and pid files under /var/run as well as reacting to network
# settings, so you should treat this with care.

# Original author: Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net>

# contrib/start-scripts/linux

## EDIT FROM HERE

# Installation prefix
prefix=/usr/local/pgsql

# Data directory
PGDATA="/usr/local/pgsql/data"

# Who to run the postmaster as, usually "postgres". (NOT "root")
PGUSER=postgres

# Where to keep a log file
PGLOG="$PGDATA/serverlog"

# It's often a good idea to protect the postmaster from being killed by the
# OOM killer (which will tend to preferentially kill the postmaster because
# of the way it accounts for shared memory). To do that, uncomment these
# three lines:
#PG_OOM_ADJUST_FILE=/proc/self/oom_score_adj
#PG_MASTER_OOM_SCORE_ADJ=-1000
#PG_CHILD_OOM_SCORE_ADJ=0
# Older Linux kernels may not have /proc/self/oom_score_adj, but instead
# /proc/self/oom_adj, which works similarly except for having a different
# range of scores. For such a system, uncomment these three lines instead:
#PG_OOM_ADJUST_FILE=/proc/self/oom_adj
#PG_MASTER_OOM_SCORE_ADJ=-17
#PG_CHILD_OOM_SCORE_ADJ=0

## STOP EDITING HERE

# The path that is to be used for the script
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# What to use to start up the postmaster. (If you want the script to wait
# until the server has started, you could use "pg_ctl start" here.)
DAEMON="$prefix/bin/postmaster"

# What to use to shut down the postmaster
PGCTL="$prefix/bin/pg_ctl"

set -e

# Only start if we can find the postmaster.
test -x $DAEMON ||
{
echo "$DAEMON not found"
if [ "$1" = "stop" ]
then exit 0
else exit 5
fi
}

# If we want to tell child processes to adjust their OOM scores, set up the
# necessary environment variables. Can't just export them through the "su".
if [ -e "$PG_OOM_ADJUST_FILE" -a -n "$PG_CHILD_OOM_SCORE_ADJ" ]
then
DAEMON_ENV="PG_OOM_ADJUST_FILE=$PG_OOM_ADJUST_FILE
PG_OOM_ADJUST_VALUE=$PG_CHILD_OOM_SCORE_ADJ"
fi

# Parse command line parameters.
case $1 in
start)
echo -n "Starting PostgreSQL: "
test -e "$PG_OOM_ADJUST_FILE" && echo "$PG_MASTER_OOM_SCORE_ADJ" >
"$PG_OOM_ADJUST_FILE"
su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' >>$PGLOG 2>&1 &"
echo "ok"
;;
stop)
echo -n "Stopping PostgreSQL: "
su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s"
echo "ok"
;;
restart)
echo -n "Restarting PostgreSQL: "
su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s"
test -e "$PG_OOM_ADJUST_FILE" && echo "$PG_MASTER_OOM_SCORE_ADJ" >
"$PG_OOM_ADJUST_FILE"
su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' >>$PGLOG 2>&1 &"
echo "ok"
;;
reload)
echo -n "Reload PostgreSQL: "
su - $PGUSER -c "$PGCTL reload -D '$PGDATA' -s"
echo "ok"
;;
status)
su - $PGUSER -c "$PGCTL status -D '$PGDATA'"
;;
*)
# Print help
echo "Usage: $0 {start|stop|restart|reload|status}" 1>&2
exit 1
;;
esac

exit 0

El lun., 9 mar. 2020 a las 12:58, <gilberto(dot)castillo(at)etecsa(dot)cu> escribió:

> El 2020-03-09 11:51, Guillermo E. Villanueva escribió:
> > Gilberto si puse donde corresponde el script de arranque.
>
> ¿Creaste una entrada en /usr/bin?
>
> Serciorate que las variables globales tenga valor.
>
> >
> > El lun., 9 mar. 2020 a las 12:49, <gilberto(dot)castillo(at)etecsa(dot)cu>
> > escribió:
> >
> >> El 2020-03-09 11:42, Guillermo E. Villanueva escribió:
> >>> Buenos días, instalé desde fuentes postgres 12 sobre centos 8
> >>> Copié el script de inicio desde contrib/start-scripts hacia el
> >>> directorio ...init.d
> >>
> >> Como instalas de la fuente tu mismo deber crear la scritp de arraque
> >>
> >> automatico, seguro en la doc, te lo explica como hacerlo.
> >>
> >>> Postgres inicia sin problemas con pg_ctl y también con la línea
> >> de
> >>> comandos
> >>> service postgres start
> >>>
> >>> pero automáticamente no lo hace
> >>>
> >>> El error que encuentro es
> >>> [root(at)centos8 ~]# SYSTEMCTL STATUS POSTGRES
> >>>
> >>> ● postgres.service - SYSV: PostgreSQL RDBMS
> >>> Loaded: loaded (/etc/rc.d/init.d/postgres; generated)
> >>> Active: failed (Result: exit-code) since Mon 2020-03-09
> >> 12:36:46
> >>> -03; 4min 24s ago
> >>> Docs: man:systemd-sysv-generator(8)
> >>> Process: 875 ExecStart=/etc/rc.d/init.d/postgres start
> >> (code=exited,
> >>> status=127)
> >>>
> >>> mar 09 12:36:46 centos8 systemd[1]: Starting SYSV: PostgreSQL
> >> RDBMS...
> >>> mar 09 12:36:46 centos8 postgres[875]: Starting PostgreSQL:
> >>> /etc/rc.d/init.d/postgres: línea 94: su: no se encontró la orden
> >>> mar 09 12:36:46 centos8 systemd[1]: postgres.service: Control
> >> process
> >>> exited, code=exited status=127
> >>> mar 09 12:36:46 centos8 systemd[1]: postgres.service: Failed with
> >>> result 'exit-code'.
> >>> mar 09 12:36:46 centos8 systemd[1]: Failed to start SYSV:
> >> PostgreSQL
> >>> RDBMS.
> >>>
> >>> El código de la línea mencionada en el mensaje de error (línea
> >> 94)
> >>> es:
> >>> su - $PGUSER -c "$DAEMON_ENV $DAEMON -D '$PGDATA' >>$PGLOG 2>&1 &"
> >>>
> >>> Tienen idea que podrá estar pasando?
> >>>
> >>> Desde ya muchas gracias.
> >>>
> >>> Guillermo
>