There was no crash that I know of. # su postgres $ cd /var/lib/pgsql/data $ cat postmaster.pid 14877 /var/lib/pgsql/data 5432001 393216 $ pg_ctl stop -D ./ waiting for postmaster to shut down......done $ rm postmaster.pid rm: imposível remover `postmaster.pid': Arquivo ou diretório não encontrado #(means file not found) $ postmaster -D /var/lib/pgsql/data > logfile 2>&1 & [1] 19256
Now as user cpn: $ pg_dump -Fc KakaoStats > KakaoStats.dump pg_dump: conector (socket) não está aberto #(means not open) pg_dump: Comando SQL para copiar o conteúdo da tabela "usuarios" falhou: PQendcopy() falhou. #(means failed) pg_dump: Mensagem de erro do servidor: conector (socket) não está aberto #(not open) pg_dump: O comando foi: COPY public.usuarios (usuario, data, n_time, wus, pontos) TO stdout; After reboot this was the log file: (forgot to get it before) # cat logfile LOG: database system was shut down at 2004-07-17 05:41:04 BRT LOG: checkpoint record is at 7/C63CFA44 LOG: redo record is at 7/C63CFA44; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 7704; next OID: 426301 LOG: database system is ready LOG: server process (PID 19261) was terminated by signal 11 LOG: terminating any other active server processes LOG: all server processes terminated; reinitializing LOG: database system was interrupted at 2004-07-17 05:45:22 BRT LOG: checkpoint record is at 7/C63CFA44 LOG: redo record is at 7/C63CFA44; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 7704; next OID: 426301 LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 7/C63CFA84 LOG: redo is not required LOG: database system is ready LOG: received fast shutdown request LOG: shutting down LOG: database system is shut down After reboot it worked OK. CPN --- mike g <[EMAIL PROTECTED]> escreveu: > It seems that postgresql crashed recently, tried to restart > automatically, and has not succesfully restarted. > > You will need to stop the postmaster daemon manually, probably delete > the postmaster.pid file, and restart the postmaster daemon. > > Chances are that anyone trying to query the database is not able > to.... > > HTH > > > On Fri, 2004-07-16 at 21:05, Clodoaldo Pinto Neto wrote: > > Hi all, > > > > Errors running a psql batch that has worked for weeks without a > > problem: > > $ uname -a > > Linux s1 2.6.6-1.435.2.3 #1 Thu Jul 1 08:25:29 EDT 2004 i686 athlon > > i386 GNU/Linux > > $ rpm -q postgresql > > postgresql-7.4.2-1 > > $ psql KakaoStats > > Bem-vindo ao psql 7.4.2, o terminal iterativo do PostgreSQL. > > > > > > select insert_usuarios_producao(); > > psql:/KakaoStats/scripts/sql/kakaoStats.sql:92: server closed the > > connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > psql:/KakaoStats/scripts/sql/kakaoStats.sql:92: connection to > server > > was lost > > > > select deleta_antigos() > > server closed the connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > > > vacuum KakaoStats > > psql: FATAL: the database system is starting up > > > > These commands are some of the last of a script which runs normaly > > until then. > > > > Regards > > Clodoaldo Pinto > > > > > > > > > > > > > > > > _______________________________________________________ > > Yahoo! Mail agora com 100MB, anti-spam e antivÃrus grátis! > > http://br.info.mail.yahoo.com/ > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 6: Have you searched our list archives? > > > > http://archives.postgresql.org > _______________________________________________________ Yahoo! Mail agora com 100MB, anti-spam e antivírus grátis! http://br.info.mail.yahoo.com/ ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
