PANIC: could not flush dirty data: Operation not permitted power8,Redhat Centos - Mailing list pgsql-hackers
| From | reiner peterke |
|---|---|
| Subject | PANIC: could not flush dirty data: Operation not permitted power8,Redhat Centos |
| Date | |
| Msg-id | DAAC4E41-4CE5-4FEA-ACAE-118F0540B92A@drizzle.com Whole thread Raw |
| Responses |
Re: PANIC: could not flush dirty data: Operation not permittedpower8, Redhat Centos
Re: PANIC: could not flush dirty data: Operation not permittedpower8, Redhat Centos |
| List | pgsql-hackers |
Hi All,
We build Postgres on Power and x86 With the latest Postgres 11 release (11.2) we get error on
power8 ppc64le (Redhat and CentOS). No error on SUSE on power8
No error on x86_64 (RH, Centos and SUSE)
from the log file
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv4 address "0.0.0.0", port 5432
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv6 address "::", port 5432
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2019-04-09 12:30:10 UTC pid:204 xid:0 ip: LOG: database system was shut down at 2019-04-09 12:27:09 UTC
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: database system is ready to accept connections
2019-04-09 12:31:46 UTC pid:203 xid:0 ip: LOG: received SIGHUP, reloading configuration files
2019-04-09 12:35:10 UTC pid:205 xid:0 ip: PANIC: could not flush dirty data: Operation not permitted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: checkpointer process (PID 205) was terminated by signal 6: Aborted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: terminating any other active server processes
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: WARNING: terminating connection because of crash of another server process
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: HINT: In a moment you should be able to reconnect to the database and repeat your command.
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: all server processes terminated; reinitializing
2019-04-09 12:35:10 UTC pid:224 xid:0 ip: LOG: database system was interrupted; last known up at 2019-04-09 12:30:10 UTC
2019-04-09 12:35:10 UTC pid:224 xid:0 ip: PANIC: could not flush dirty data: Operation not permitted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: startup process (PID 224) was terminated by signal 6: Aborted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: aborting startup due to startup process failure
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: database system is shut down
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on IPv6 address "::", port 5432
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2019-04-09 12:30:10 UTC pid:204 xid:0 ip: LOG: database system was shut down at 2019-04-09 12:27:09 UTC
2019-04-09 12:30:10 UTC pid:203 xid:0 ip: LOG: database system is ready to accept connections
2019-04-09 12:31:46 UTC pid:203 xid:0 ip: LOG: received SIGHUP, reloading configuration files
2019-04-09 12:35:10 UTC pid:205 xid:0 ip: PANIC: could not flush dirty data: Operation not permitted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: checkpointer process (PID 205) was terminated by signal 6: Aborted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: terminating any other active server processes
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: WARNING: terminating connection because of crash of another server process
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-04-09 12:35:10 UTC pid:208 xid:0 ip: HINT: In a moment you should be able to reconnect to the database and repeat your command.
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: all server processes terminated; reinitializing
2019-04-09 12:35:10 UTC pid:224 xid:0 ip: LOG: database system was interrupted; last known up at 2019-04-09 12:30:10 UTC
2019-04-09 12:35:10 UTC pid:224 xid:0 ip: PANIC: could not flush dirty data: Operation not permitted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: startup process (PID 224) was terminated by signal 6: Aborted
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: aborting startup due to startup process failure
2019-04-09 12:35:10 UTC pid:203 xid:0 ip: LOG: database system is shut down
from pg_config
pg_config output
BINDIR = /usr/local/postgres/11/bin
DOCDIR = /usr/local/postgres/11/share/doc
HTMLDIR = /usr/local/postgres/11/share/doc
INCLUDEDIR = /usr/local/postgres/11/include
PKGINCLUDEDIR = /usr/local/postgres/11/include
INCLUDEDIR-SERVER = /usr/local/postgres/11/include/server
LIBDIR = /usr/local/postgres/11/lib
PKGLIBDIR = /usr/local/postgres/11/lib
LOCALEDIR = /usr/local/postgres/11/share/locale
MANDIR = /usr/local/postgres/11/share/man
SHAREDIR = /usr/local/postgres/11/share
SYSCONFDIR = /usr/local/postgres/etc
PGXS = /usr/local/postgres/11/lib/pgxs/src/makefiles/pgxs.mk
CONFIGURE = '--with-tclconfig=/usr/lib64' '--with-perl' '--with-python' '--with-tcl' '--with-openssl' '--with-pam' '--with-gssapi' '--enable-nls' '--with-libxml' '--with-libxslt' '--with-ldap' '--prefix=/usr/local/postgres/11' 'CFLAGS=-O3 -g -pipe -Wall -D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -m64 -mcpu=power8 -mtune=power8 -DLINUX_OOM_SCORE_ADJ=0' '--with-libs=/usr/lib' '--with-includes=/usr/include' '--with-uuid=e2fs' '--sysconfdir=/usr/local/postgres/etc' '--with-llvm' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig'
CC = gcc
CPPFLAGS = -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include
CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -O3 -g -pipe -Wall -D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -m64 -mcpu=power8 -mtune=power8 -DLINUX_OOM_SCORE_ADJ=0
CFLAGS_SL = -fPIC
LDFLAGS = -L/usr/local/lib -L/usr/lib -Wl,--as-needed -Wl,-rpath,'/usr/local/postgres/11/lib',--enable-new-dtags
LDFLAGS_EX =
LDFLAGS_SL =
LIBS = -lpgcommon -lpgport -lpthread -lxslt -lxml2 -lpam -lssl -lcrypto -lgssapi_krb5 -lz -lreadline -lrt -lcrypt -ldl -lm
VERSION = PostgreSQL 11.2
I get the feeling this is related to the fsync() issue.
why is it happening on Power RH and CentOS, but not on the other platforms?
Let me know if i need to provide any more information.
Reiner
Attachment
pgsql-hackers by date: