Почему постгрес сервер работает нестабильно?

Question

[x67]

Есть сервер ubuntu 16.04 на vps. На нем по кронтабу запускается парсер, который сохраняет данные в БД постгрес. Интервал достаточно большой, навряд ли дело в нагрузке. Уже второй раз за 2 недели сервер бд зависает. После первого раза подумал, что возможно стоит перезагружать сервер каждый день и проблема исчезнет, но нет. Процесс есть, но на любое подключение извне или локально выдает

could not connect to server: Connection refused
        Is the server running on host xhostx and accepting
        TCP/IP connections on port xportx?

Из настроек только базовые + доступ из интернета по определенному порту пользователям. Что может быть и как искать проблему?
UPD: Парсер запускается каждые десять минут, однако судя по логам последний удачный запуск был в 13:10, а следующий запуск произошел только в 13:37 и тогда сервер БД не коннектился. Может дело в vps?

Comments

[Антон Уланов]

что в процессах висит из пг? я щас сам его кручу на предмет оптимизации под 1с

[Евгений Вольф]

Может дело в vps?

Дело может быть в чем угодно, но меньше всего вероятны проблемы с самим PG, если Вы там ничего не накрутили лишнего (что впрочем, мало вероятно, т.к. успешные подключения всё же бывают).

По хорошему бы нужно:
1. Посмотреть список открытых портов на сервере (ссылку даю первую попавшуюся, Вы можете найти таких ещё миллион, самостоятельно)
2. Посмотреть список процессов, как Вам порекомендовал предыдущий комментатор
3. Посмотреть нагрузку на процессор и сеть, а ещё лучше логировать её (и посмотреть потом логи)

*или Завести какой-то другой сервер, например, поднять веб-сервер там же, оставить на нем дефолтную страничку и повесить на него автоматический мониторинг (так Вы убедитесь, что проблема либо с самой сетью/севером, либо именно с БД, это как наиболее простой вариант)

*или Добавить на мониторинг пинг сервера, и проверять таким образом сеть, чуть менее эффективный вариант, и не совсем "точный" в некоторых случаях, но самый простой

P.S. Бесплатные серверы мониторинга, делающие проверку каждые 5 минут - Вы найдете без труда.

[x67]

Антон Уланов:
Евгений Вольф
service status показывает это

● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2017-05-24 00:22:35 MSK; 30min ago
  Process: 3550 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
  Process: 3038 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 3038 (code=exited, status=0/SUCCESS)
    Tasks: 0
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/postgresql.service

May 24 00:22:35 ubuntu systemd[1]: Stopped PostgreSQL RDBMS.
May 24 00:22:35 ubuntu systemd[1]: Stopping PostgreSQL RDBMS...
May 24 00:22:35 ubuntu systemd[1]: Starting PostgreSQL RDBMS...
May 24 00:22:35 ubuntu systemd[1]: Started PostgreSQL RDBMS.
May 24 00:33:50 ubuntu systemd[1]: Started PostgreSQL RDBMS.
May 24 00:41:05 ubuntu systemd[1]: Started PostgreSQL RDBMS.
May 24 00:44:42 ubuntu systemd[1]: Reloading PostgreSQL RDBMS.
May 24 00:44:42 ubuntu systemd[1]: Reloaded PostgreSQL RDBMS.

Однако top эти процессы не показывает
не совсем понимаю, в чем проблема

[Антон Уланов]

x67: а в логах? можно не весь а за пару часов где были сбои

[x67]

Антон Уланов: сейчас это все что есть, если речь о systemctl логах.
netstat показывает только слушающий фтп сервер и sshd

servcie --status-all показывает это
[ + ] acpid
[ + ] apparmor
[ + ] apport
[ + ] atd
[ - ] bootmisc.sh
[ - ] checkfs.sh
[ - ] checkroot-bootclean.sh
[ - ] checkroot.sh
[ + ] console-setup
[ + ] cron
[ - ] cryptdisks
[ - ] cryptdisks-early
[ + ] dbus
[ + ] grub-common
[ - ] hostname.sh
[ - ] hwclock.sh
[ + ] irqbalance
[ + ] iscsid
[ + ] keyboard-setup
[ - ] killprocs
[ + ] kmod
[ - ] lvm2
[ + ] lvm2-lvmetad
[ + ] lvm2-lvmpolld
[ + ] lxcfs
[ - ] lxd
[ + ] mdadm
[ - ] mdadm-waitidle
[ - ] mountall-bootclean.sh
[ - ] mountall.sh
[ - ] mountdevsubfs.sh
[ - ] mountkernfs.sh
[ - ] mountnfs-bootclean.sh
[ - ] mountnfs.sh
[ + ] networking
[ + ] ondemand
[ + ] open-iscsi
[ - ] open-vm-tools
[ + ] openbsd-inetd
[ - ] plymouth
[ - ] plymouth-log
[ + ] postgresql
[ + ] procps
[ + ] pure-ftpd
[ + ] rc.local
[ + ] resolvconf
[ - ] rsync
[ + ] rsyslog
[ - ] screen-cleanup
[ - ] sendsigs
[ + ] ssh
[ + ] sysstat
[ + ] udev
[ + ] ufw
[ - ] umountfs
[ - ] umountnfs.sh
[ - ] umountroot
[ - ] unattended-upgrades
[ + ] urandom
[ - ] uuidd

в postgresql.conf listent_addresses='*', то есть если я правильно понимаю, он и локалхост и сетевые должен слушать

[x67]

Антон Уланов: и еще, pg_hba.conf доступен только через судо или учетку постгрес, это может повлиять как-то? (раньше работало и таким вопросом не задавался даже, но мало ли)

[Антон Уланов]

x67: нет. Речь о самом логе пг. /var/log/postgresql/postures.....

[Антон Уланов]

Конфиги обычным смертным не должны быть доступны для редактирования. Это будет грусть и печаль когда юзер по незнанию затрет тот же etc или boot

[x67]

Антон Уланов: там был только postgresql-9.5-main.log и его более старые собратья
вот что там

spoiler

2017-05-23 07:45:29 MSK [6911-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:18:39 MSK [1085-1] [unknown]@[unknown] LOG: incomplete startup packet
2017-05-23 21:18:39 MSK [1084-1] LOG: database system was interrupted; last known up at 2017-05-23 13:10:58 MSK
2017-05-23 21:18:39 MSK [1088-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:40 MSK [1091-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:40 MSK [1094-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:41 MSK [1097-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:41 MSK [1100-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:42 MSK [1084-2] LOG: database system was not properly shut down; automatic recovery in progress
2017-05-23 21:18:42 MSK [1084-3] LOG: redo starts at 0/2534CDF0
2017-05-23 21:18:42 MSK [1103-1] postgres@postgres FATAL: the database system is starting up
2017-05-23 21:18:42 MSK [1084-4] LOG: invalid record length at 0/2535B6B8
2017-05-23 21:18:42 MSK [1084-5] LOG: redo done at 0/2535B690
2017-05-23 21:18:42 MSK [1084-6] LOG: last completed transaction was at log time 2017-05-23 13:13:38.736734+03
2017-05-23 21:18:42 MSK [1084-7] LOG: MultiXact member wraparound protections are now enabled
2017-05-23 21:18:42 MSK [1081-1] LOG: database system is ready to accept connections
2017-05-23 21:18:42 MSK [1107-1] LOG: autovacuum launcher started
2017-05-23 21:18:54 MSK [1129-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:09 MSK [1131-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:23 MSK [1133-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:50 MSK [1211-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:53 MSK [1213-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:54 MSK [1215-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:54 MSK [1217-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:54 MSK [1219-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:54 MSK [1221-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:56 MSK [1223-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:19:57 MSK [1233-1] def_user@main_db LOG: could not receive data from client: Connection reset by peer
2017-05-23 21:20:47 MSK [1251-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:20:48 MSK [1253-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:01 MSK [1257-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:04 MSK [1261-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:08 MSK [1263-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:08 MSK [1265-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:09 MSK [1267-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:09 MSK [1269-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:09 MSK [1271-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:09 MSK [1273-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:21:15 MSK [1278-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:18 MSK [1312-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:19 MSK [1316-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:26 MSK [1318-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:34 MSK [1322-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:47 MSK [1353-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:49 MSK [1355-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:49 MSK [1357-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:50 MSK [1359-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:50 MSK [1361-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:50 MSK [1363-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:23:51 MSK [1365-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:14 MSK [1368-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:15 MSK [1370-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:24 MSK [1372-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:34 MSK [1374-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:50 MSK [1377-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:54 MSK [1379-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:55 MSK [1381-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:56 MSK [1383-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:57 MSK [1385-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:24:59 MSK [1387-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:25:01 MSK [1390-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:25:41 MSK [1395-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:25:42 MSK [1397-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:25:49 MSK [1400-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:25:56 MSK [1402-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:09 MSK [1404-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:11 MSK [1406-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:11 MSK [1408-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:11 MSK [1410-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:12 MSK [1412-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:12 MSK [1414-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:26:13 MSK [1417-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "94.226.217.209", user "aleksey", database "main_db", SSL off
2017-05-23 21:29:24 MSK [1480-1] def_user@main_db LOG: could not receive data from client: Connection reset by peer
2017-05-24 18:16:06 MSK [1133-1] LOG: end-of-line before authentication method
2017-05-24 18:16:06 MSK [1133-2] CONTEXT: line 101 of configuration file "/etc/postgresql/9.5/main/pg_hba.conf"
2017-05-24 18:16:06 MSK [1133-3] FATAL: could not load pg_hba.conf
2017-05-24 19:50:27 MSK [2063-1] LOG: redirecting log output to logging collector process
2017-05-24 19:50:27 MSK [2063-2] HINT: Future log output will appear in directory "pg_log".
2017-05-24 20:01:54 MSK [3015-1] LOG: redirecting log output to logging collector process
2017-05-24 20:01:54 MSK [3015-2] HINT: Future log output will appear in directory "pg_log".

[Антон Уланов]

Во сколько был сбой 3 момента напишите. И куда у вас делся hba? Он лежит на месте?

[x67]

Антон Уланов: pg_hba.conf выглядит сейчас так вот
hostssl all aleksey 0.0.0.0/0 password
host all def_user 127.0.0.1/32
local all all peer
последняя строчка была изначально
local all all trust
это я сегодня уже ее изменил. Причем не принимает он подключения ниоткуда, ни через ssh терминал, ни через интернет от пользователя алексей
Андрей
а postgresql.conf такой

spoiler

# -----------------------------
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form:
#
# name = value
#
# (The "=" is optional.) Whitespace may be used. Comments are introduced with
# "#" anywhere on a line. The complete list of parameter names and allowed
# values can be found in the PostgreSQL documentation.
#
# The commented-out settings shown in this file represent the default values.
# Re-commenting a setting is NOT sufficient to revert it to the default value;
# you need to reload the server.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal. If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pg_ctl reload". Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#
# Any parameter can also be given as a command-line option to the server, e.g.,
# "postgres -c log_connections=on". Some parameters can be changed at run time
# with the "SET" SQL command.
#
# Memory units: kB = kilobytes Time units: ms = milliseconds
# MB = megabytes s = seconds
# GB = gigabytes min = minutes
# TB = terabytes h = hours
# d = days

#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------

# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.

data_directory = '/var/lib/postgresql/9.5/main' # use data in another directory
# (change requires restart)
hba_file = '/etc/postgresql/9.5/main/pg_hba.conf' # host-based authentication file
# (change requires restart)
ident_file = '/etc/postgresql/9.5/main/pg_ident.conf' # ident configuration file
# (change requires restart)

# If external_pid_file is not explicitly set, no extra PID file is written.
external_pid_file = '/var/run/postgresql/9.5-main.pid' # write an extra PID file
# (change requires restart)

#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------

# - Connection Settings -

listen_addresses = '*' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost'; use '*' for all
# (change requires restart)
port = 6665 # (change requires restart)
max_connections = 100 # (change requires restart)
#superuser_reserved_connections = 3 # (change requires restart)
unix_socket_directories = '/var/run/postgresql' # comma-separated list of directories
# (change requires restart)
#unix_socket_group = '' # (change requires restart)
#unix_socket_permissions = 0777 # begin with 0 to use octal notation
# (change requires restart)
#bonjour = off # advertise server via Bonjour
# (change requires restart)
#bonjour_name = '' # defaults to the computer name
# (change requires restart)

# - Security and Authentication -

authentication_timeout = 1min # 1s-600s
ssl = true # (change requires restart)
#ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' # allowed SSL ciphers
# (change requires restart)
#ssl_prefer_server_ciphers = on # (change requires restart)
#ssl_ecdh_curve = 'prime256v1' # (change requires restart)
ssl_cert_file = '/etc/ssl/certs/ssl-cert-snakeoil.pem' # (change requires restart)
ssl_key_file = '/etc/ssl/private/ssl-cert-snakeoil.key' # (change requires restart)
#ssl_ca_file = '' # (change requires restart)
#ssl_crl_file = '' # (change requires restart)
#password_encryption = on
#db_user_namespace = off
#row_security = on

# GSSAPI using Kerberos
#krb_server_keyfile = ''
#krb_caseins_users = off

# - TCP Keepalives -
# see "man 7 tcp" for details

#tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds;
# 0 selects the system default
#tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds;
# 0 selects the system default
#tcp_keepalives_count = 0 # TCP_KEEPCNT;
# 0 selects the system default

#------------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#------------------------------------------------------------------------------

# - Memory -

shared_buffers = 128MB # min 128kB
# (change requires restart)
#huge_pages = try # on, off, or try
# (change requires restart)
#temp_buffers = 8MB # min 800kB
#max_prepared_transactions = 0 # zero disables the feature
# (change requires restart)
# Caution: it is not advisable to set max_prepared_transactions nonzero unless
# you actively intend to use prepared transactions.
#work_mem = 4MB # min 64kB
#maintenance_work_mem = 64MB # min 1MB
#autovacuum_work_mem = -1 # min 1MB, or -1 to use maintenance_work_mem
#max_stack_depth = 2MB # min 100kB
dynamic_shared_memory_type = posix # the default is the first option
# supported by the operating system:
# posix
# sysv
# windows
# mmap
# use none to disable dynamic shared memory

# - Disk -

#temp_file_limit = -1 # limits per-session temp file space
# in kB, or -1 for no limit

# - Kernel Resource Usage -

#max_files_per_process = 1000 # min 25
# (change requires restart)
#shared_preload_libraries = '' # (change requires restart)

# - Cost-Based Vacuum Delay -

#vacuum_cost_delay = 0 # 0-100 milliseconds
#vacuum_cost_page_hit = 1 # 0-10000 credits
#vacuum_cost_page_miss = 10 # 0-10000 credits
#vacuum_cost_page_dirty = 20 # 0-10000 credits
#vacuum_cost_limit = 200 # 1-10000 credits

# - Background Writer -

#bgwriter_delay = 200ms # 10-10000ms between rounds
#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round
#bgwriter_lru_multiplier = 2.0 # 0-10.0 multipler on buffers scanned/round

# - Asynchronous Behavior -

#effective_io_concurrency = 1 # 1-1000; 0 disables prefetching
#max_worker_processes = 8

#------------------------------------------------------------------------------
# WRITE AHEAD LOG
#------------------------------------------------------------------------------

# - Settings -

#wal_level = minimal # minimal, archive, hot_standby, or logical
# (change requires restart)
#fsync = on # turns forced synchronization on or off
#synchronous_commit = on # synchronization level;
# off, local, remote_write, or on
#wal_sync_method = fsync # the default is the first option
# supported by the operating system:
# open_datasync
# fdatasync (default on Linux)
# fsync
# fsync_writethrough
# open_sync
#full_page_writes = on # recover from partial page writes
#wal_compression = off # enable compression of full-page writes
#wal_log_hints = off # also do full page writes of non-critical updates
# (change requires restart)
#wal_buffers = -1 # min 32kB, -1 sets based on shared_buffers
# (change requires restart)
#wal_writer_delay = 200ms # 1-10000 milliseconds

#commit_delay = 0 # range 0-100000, in microseconds
#commit_siblings = 5 # range 1-1000

# - Checkpoints -

#checkpoint_timeout = 5min # range 30s-1h
#max_wal_size = 1GB
#min_wal_size = 80MB
#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
#checkpoint_warning = 30s # 0 disables

# - Archiving -

#archive_mode = off # enables archiving; off, on, or always
# (change requires restart)
#archive_command = '' # command to use to archive a logfile segment
# placeholders: %p = path of file to archive
# %f = file name only
# e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
#archive_timeout = 0 # force a logfile segment switch after this
# number of seconds; 0 disables

#------------------------------------------------------------------------------
# REPLICATION
#------------------------------------------------------------------------------

# - Sending Server(s) -

# Set these on the master and on any standby that will send replication data.

#max_wal_senders = 0 # max number of walsender processes
# (change requires restart)
#wal_keep_segments = 0 # in logfile segments, 16MB each; 0 disables
#wal_sender_timeout = 60s # in milliseconds; 0 disables

#max_replication_slots = 0 # max number of replication slots
# (change requires restart)
#track_commit_timestamp = off # collect timestamp of transaction commit
# (change requires restart)

# - Master Server -

# These settings are ignored on a standby server.

#synchronous_standby_names = '' # standby servers that provide sync rep
# comma-separated list of application_name
# from standby(s); '*' = all
#vacuum_defer_cleanup_age = 0 # number of xacts by which cleanup is delayed

# - Standby Servers -

# These settings are ignored on a master server.

#hot_standby = off # "on" allows queries during recovery
# (change requires restart)
#max_standby_archive_delay = 30s # max delay before canceling queries
# when reading WAL from archive;
# -1 allows indefinite delay
#max_standby_streaming_delay = 30s # max delay before canceling queries
# when reading streaming WAL;
# -1 allows indefinite delay
#wal_receiver_status_interval = 10s # send replies at least this often
# 0 disables
#hot_standby_feedback = off # send info from standby to prevent
# query conflicts
#wal_receiver_timeout = 60s # time that receiver waits for
# communication from master
# in milliseconds; 0 disables
#wal_retrieve_retry_interval = 5s # time to wait before retrying to
# retrieve WAL after a failed attempt

#------------------------------------------------------------------------------
# QUERY TUNING
#------------------------------------------------------------------------------

# - Planner Method Configuration -

#enable_bitmapscan = on
#enable_hashagg = on
#enable_hashjoin = on
#enable_indexscan = on
#enable_indexonlyscan = on
#enable_material = on
#enable_mergejoin = on
#enable_nestloop = on
#enable_seqscan = on
#enable_sort = on
#enable_tidscan = on

# - Planner Cost Constants -

#seq_page_cost = 1.0 # measured on an arbitrary scale
#random_page_cost = 4.0 # same scale as above
#cpu_tuple_cost = 0.01 # same scale as above
#cpu_index_tuple_cost = 0.005 # same scale as above
#cpu_operator_cost = 0.0025 # same scale as above
#effective_cache_size = 4GB

# - Genetic Query Optimizer -

#geqo = on
#geqo_threshold = 12
#geqo_effort = 5 # range 1-10
#geqo_pool_size = 0 # selects default based on effort
#geqo_generations = 0 # selects default based on effort
#geqo_selection_bias = 2.0 # range 1.5-2.0
#geqo_seed = 0.0 # range 0.0-1.0

# - Other Planner Options -

#default_statistics_target = 100 # range 1-10000
#constraint_exclusion = partition # on, off, or partition
#cursor_tuple_fraction = 0.1 # range 0.0-1.0
#from_collapse_limit = 8
#join_collapse_limit = 8 # 1 disables collapsing of explicit
# JOIN clauses

#------------------------------------------------------------------------------
# ERROR REPORTING AND LOGGING
#------------------------------------------------------------------------------

# - Where to Log -

#log_destination = 'stderr' # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform. csvlog
# requires logging_collector to be on.

# This is used when logging to stderr:
logging_collector = on # Enable capturing of stderr and csvlog
# into log files. Required to be on for
# csvlogs.
# (change requires restart)

# These are only used if logging_collector is on:
log_directory = 'pg_log' # directory where log files are written,
# can be absolute or relative to PGDATA
log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
# can include strftime() escapes
log_file_mode = 0600 # creation mode for log files,
# begin with 0 to use octal notation
log_truncate_on_rotation = off # If on, an existing log file with the
# same name as the new log file will be
# truncated rather than appended to.
# But such truncation only occurs on
# time-driven rotation, not on restarts
# or size-driven rotation. Default is
# off, meaning append to existing files
# in all cases.
#log_rotation_age = 1d # Automatic rotation of logfiles will
# happen after that time. 0 disables.
#log_rotation_size = 10MB # Automatic rotation of logfiles will
# happen after that much log output.
# 0 disables.

# These are relevant when logging to syslog:
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'

# This is only relevant when logging to eventlog (win32):
#event_source = 'PostgreSQL'

# - When to Log -

#client_min_messages = notice # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# log
# notice
# warning
# error

#log_min_messages = warning # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# info
# notice
# warning
# error
# log
# fatal
# panic

#log_min_error_statement = error # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# info
# notice
# warning
# error
# log
# fatal
# panic (effectively off)

#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations, > 0 logs only
# statements running at least this number
# of milliseconds

# - What to Log -

#debug_print_parse = off
#debug_print_rewritten = off
#debug_print_plan = off
#debug_pretty_print = on
#log_checkpoints = off
#log_connections = off
#log_disconnections = off
#log_duration = off
#log_error_verbosity = default # terse, default, or verbose messages
#log_hostname = off
log_line_prefix = '%t [%p-%l] %q%u@%d ' # special values:
# %a = application name
# %u = user name
# %d = database name
# %r = remote host and port
# %h = remote host
# %p = process ID
# %t = timestamp without milliseconds
# %m = timestamp with milliseconds
# %i = command tag
# %e = SQL state
# %c = session ID
# %l = session line number
# %s = session start timestamp
# %v = virtual transaction ID
# %x = transaction ID (0 if none)
# %q = stop here in non-session
# processes
# %% = '%'
# e.g. '<%u%%%d> '
#log_lock_waits = off # log lock waits >= deadlock_timeout
#log_statement = 'none' # none, ddl, mod, all
#log_replication_commands = off
#log_temp_files = -1 # log temporary files equal or larger
# than the specified size in kilobytes;
# -1 disables, 0 logs all temp files
log_timezone = 'W-SU'

# - Process Title -

#cluster_name = '' # added to process titles if nonempty
# (change requires restart)
#update_process_title = on

#------------------------------------------------------------------------------
# RUNTIME STATISTICS
#------------------------------------------------------------------------------

# - Query/Index Statistics Collector -

#track_activities = on
#track_counts = on
#track_io_timing = off
#track_functions = none # none, pl, all
#track_activity_query_size = 1024 # (change requires restart)
stats_temp_directory = '/var/run/postgresql/9.5-main.pg_stat_tmp'

# - Statistics Monitoring -

#log_parser_stats = off
#log_planner_stats = off
#log_executor_stats = off
#log_statement_stats = off

#------------------------------------------------------------------------------
# AUTOVACUUM PARAMETERS
#------------------------------------------------------------------------------

#autovacuum = on # Enable autovacuum subprocess? 'on'
# requires track_counts to also be on.
#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
# their durations, > 0 logs only
# actions running at least this number
# of milliseconds.
#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
# (change requires restart)
#autovacuum_naptime = 1min # time between autovacuum runs
#autovacuum_vacuum_threshold = 50 # min number of row updates before
# vacuum
#autovacuum_analyze_threshold = 50 # min number of row updates before
# analyze
#autovacuum_vacuum_scale_factor = 0.2 # fraction of table size before vacuum
#autovacuum_analyze_scale_factor = 0.1 # fraction of table size before analyze
#autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
# (change requires restart)
#autovacuum_multixact_freeze_max_age = 400000000 # maximum multixact age
# before forced vacuum
# (change requires restart)
#autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for
# autovacuum, in milliseconds;
# -1 means use vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
# autovacuum, -1 means use
# vacuum_cost_limit

#------------------------------------------------------------------------------
# CLIENT CONNECTION DEFAULTS
#------------------------------------------------------------------------------

# - Statement Behavior -

#search_path = '"$user", public' # schema names
#default_tablespace = '' # a tablespace name, '' uses the default
#temp_tablespaces = '' # a list of tablespace names, '' uses
# only default tablespace
#check_function_bodies = on
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = off
#default_transaction_deferrable = off
#session_replication_role = 'origin'
#statement_timeout = 0 # in milliseconds, 0 is disabled
#lock_timeout = 0 # in milliseconds, 0 is disabled
#vacuum_freeze_min_age = 50000000
#vacuum_freeze_table_age = 150000000
#vacuum_multixact_freeze_min_age = 5000000
#vacuum_multixact_freeze_table_age = 150000000
#bytea_output = 'hex' # hex, escape
#xmlbinary = 'base64'
#xmloption = 'content'
#gin_fuzzy_search_limit = 0
#gin_pending_list_limit = 4MB

# - Locale and Formatting -

datestyle = 'iso, mdy'
#intervalstyle = 'postgres'
timezone = 'W-SU'
#timezone_abbreviations = 'Default' # Select the set of available time zone
# abbreviations. Currently, there are
# Default
# Australia (historical usage)
# India
# You can create your own file in
# share/timezonesets/.
#extra_float_digits = 0 # min -15, max 3
#client_encoding = sql_ascii # actually, defaults to database
# encoding

# These settings are initialized by initdb, but they can be changed.
lc_messages = 'en_US.UTF-8' # locale for system error message
# strings
lc_monetary = 'en_US.UTF-8' # locale for monetary formatting
lc_numeric = 'en_US.UTF-8' # locale for number formatting
lc_time = 'en_US.UTF-8' # locale for time formatting

# default configuration for text search
default_text_search_config = 'pg_catalog.english'

# - Other Defaults -

#dynamic_library_path = '$libdir'
#local_preload_libraries = ''
#session_preload_libraries = ''

#------------------------------------------------------------------------------
# LOCK MANAGEMENT
#------------------------------------------------------------------------------

#deadlock_timeout = 1s
#max_locks_per_transaction = 64 # min 10
# (change requires restart)
#max_pred_locks_per_transaction = 64 # min 10
# (change requires restart)

#------------------------------------------------------------------------------
# VERSION/PLATFORM COMPATIBILITY
#------------------------------------------------------------------------------

# - Previous PostgreSQL Versions -

#array_nulls = on
#backslash_quote = safe_encoding # on, off, or safe_encoding
#default_with_oids = off
#escape_string_warning = on
#lo_compat_privileges = off
#operator_precedence_warning = off
#quote_all_identifiers = off
#sql_inheritance = on
#standard_conforming_strings = on
#synchronize_seqscans = on

# - Other Platforms and Clients -

#transform_null_equals = off

#------------------------------------------------------------------------------
# ERROR HANDLING
#------------------------------------------------------------------------------

#exit_on_error = off # terminate session on any error?
restart_after_crash = on # reinitialize after backend crash?

#------------------------------------------------------------------------------
# CONFIG FILE INCLUDES
#------------------------------------------------------------------------------

# These options allow settings to be loaded from files other than the
# default postgresql.conf.

#include_dir = 'conf.d' # include files ending in '.conf' from
# directory 'conf.d'
#include_if_exists = 'exists.conf' # include file only if it exists
#include = 'special.conf' # include file

#------------------------------------------------------------------------------
# CUSTOMIZED OPTIONS
#------------------------------------------------------------------------------

# Add settings for extensions here

[Антон Уланов]

Что у вас на 101 строчке в hba?

[x67]

Антон Уланов: Сбой произошел вчера, судя по логам парсера, он запустился в 13:10, отработал штатно. Следующий запуск должен был быть в 13:20, но произошел только в 13:37, в следствие чего делаю вывод, что с сервером было что то не так в этот промежуток времени. В 13:37 постгрес уже не работал. В 20-21 час я заметил проблему, перезапустил сервак и вроде как дело пошло, но потом по неведомым причинам постгрес вообще перестал отвечать.
На 101 строчке включая комментарии находится host all def_user 127.0.0.1/32

[x67]

Антон Уланов: Огромное спасибо, закомментил 101 строку, перезапустил сервис и все заработало. По крайней мере к локалхосту подключается
Ума не приложу, как оно раньше работало и как я умудрился сломать себе ногу 2 недели назад так, что болеть она начала только сегодня :D

[Антон Уланов]

А зачем маска локалхосту в 101 строке? Это ип а не подсеть

[Антон Уланов]

Но чую это у вас еще не все. Очистите лог и перезастите сервис. И сюда лог:)

[Антон Уланов]

Затем выполните задание из крона и снова сюда лог

[Антон Уланов]

Отловим мы ваши ошибки:) тут и не такое решали

[x67]

Антон Уланов:

spoiler

2017-05-24 20:40:43 MSK [3360-1] LOG: database system was interrupted; last known up at 2017-05-23 22:23:45 MSK
2017-05-24 20:40:44 MSK [3361-1] [unknown]@[unknown] LOG: incomplete startup packet
2017-05-24 20:40:44 MSK [3364-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:45 MSK [3367-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:45 MSK [3360-2] LOG: database system was not properly shut down; automatic recovery in progress
2017-05-24 20:40:45 MSK [3360-3] LOG: redo starts at 0/25476FB8
2017-05-24 20:40:46 MSK [3370-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:46 MSK [3360-4] LOG: invalid record length at 0/2549FC28
2017-05-24 20:40:46 MSK [3360-5] LOG: redo done at 0/2549FC00
2017-05-24 20:40:46 MSK [3373-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:46 MSK [3360-6] LOG: last completed transaction was at log time 2017-05-23 22:30:07.095675+03
2017-05-24 20:40:47 MSK [3376-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:47 MSK [3379-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:48 MSK [3382-1] postgres@postgres FATAL: the database system is starting up
2017-05-24 20:40:48 MSK [3360-7] LOG: MultiXact member wraparound protections are now enabled
2017-05-24 20:40:48 MSK [3386-1] LOG: autovacuum launcher started
2017-05-24 20:40:48 MSK [3358-3] LOG: database system is ready to accept connections
2017-05-24 20:41:36 MSK [3428-1] def_user@main_db LOG: could not receive data from client: Connection reset by peer
2017-05-24 20:44:49 MSK [3429-1] def_user@main_db LOG: could not receive data from client: Connection reset by peer
2017-05-24 20:45:37 MSK [3442-1] aleksey@main_db LOG: could not receive data from client: Connection reset by peer
2017-05-24 20:50:45 MSK [3459-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "46.242.9.201", user "aleksey", database "main_db", SSL off
2017-05-24 20:50:51 MSK [3462-1] aleksey@main_db FATAL: no pg_hba.conf entry for host "46.242.9.201", user "aleksey", database "main_db", SSL off

как-то так. Парсер отработал 2 раза в 20:50 и 21:00 и судя по всему никаких ошибок не вызвал. Алексей тут с ошибкой маячит скорее всего из-за неправильной настройки клиента (сначала пытается подключиться без SSL, так как в настройках там выставлено "авто") А вот остальные события выглядят как-то неприятно:
2017-05-24 20:40:43 MSK [3360-1] LOG: database system was interrupted; last known up at 2017-05-23 22:23:45 MSK
2017-05-24 20:40:44 MSK [3361-1] [unknown]@[unknown] LOG: incomplete startup packet
2017-05-24 20:40:46 MSK [3360-4] LOG: invalid record length at 0/2549FC28
Что это могло бы быть?

[Антон Уланов]

LOG: incomplete startup packet у меня такое же сыпится на pgsql от postgrespro
а так вроде все ок, поправеть чтобы авторизация не выдавала ошибки. можно будет посмотреть может вы где что пропустили по логам с ошибками

Answer 1

[Пума Тайланд]

очевидно что у вас поди 512 мб памяти
очевидно что в последних версиях pg настройку кеша подняли с 128мб до 4GB
и вероятно из за отсутствия памяти pg умирает
смотрите dmesg после того как он не доступен становится

Comments

[x67]

то есть мне нужно уменьшить effective_cache_size до обозримых для сервера размеров и проблема должна пропасть?
Сейчас занята только треть памяти, сервер только из перезагрузки, однако постгрес не отвечает. Как его реанимировать?

[Пума Тайланд]

x67: сервис постгрес рестарт Нуи логи посмотреть

[x67]

Пума Тайланд: рестарт не помогает. Уточните пожалуйста, какие логи вас интересуют.

[Пума Тайланд]

x67: меня никакие а вы можете посмотреть все

[Андрей]

x67: логи постгреса в студию, а также конфигурацию постгреса и сервера

[x67]

Пума Тайланд: я неправильно выразился, однако ж мне просмотр логов ничего не дал. Ну и как-то странно советовать человеку, который не знает куда смотреть, смотреть везде.

[Пума Тайланд]

x67: все дороги в вар лог