Vous n'êtes pas identifié(e).
Pages : 1
Bonsoir,
Effectivement , c'est un problème de droit à la base , mais aucune manipulation a été faite sur les comptes.
J'ai scruté les log dans tout les sens rien n'en ressort.
Y a t'il une solution à part la réinstallation ?
Merci d'avance.
Bonjour,
Non , je ne l'ai pas supprimé .
Le serveur à juste était redemarré vers 15H
Log d'aujourd'hui , effectivement , problème avec ce fichier.
2010-03-24 12:15:59 LOG: database system was interrupted at 2010-03-23 15:00:54
2010-03-24 12:15:59 LOG: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory
2010-03-24 12:15:59 LOG: invalid primary checkpoint record
2010-03-24 12:15:59 LOG: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory
2010-03-24 12:15:59 LOG: invalid secondary checkpoint record
2010-03-24 12:15:59 PANIC: could not locate a valid checkpoint record
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
2010-03-24 12:15:59 LOG: startup process (PID 1512) exited with exit code 3
2010-03-24 12:15:59 LOG: aborting startup due to startup process failure
2010-03-24 12:16:00 LOG: logger shutting down
Bonjour,
En fait , je pensais que c'était un problème de droit donc j'ai essayé de mettre postgre dans un groupe administrateur mais visiblement ce n'est pas une bonne idée.
J'ai essayé aussi d'augmenter les droits sur les dossiers Postgre et sous dossier mais ce n'est pas non plus une bonne idée .
Voici les log quand il y a eu le crash , suite à un redemarrage du serveur :
2010-03-23 13:11:00 NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "firmwareupdtaskqueue_pkey" for table "firmwareupdtaskqueue"
2010-03-23 13:11:00 NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "firmwareupdlog_pkey" for table "firmwareupdlog"
2010-03-23 13:11:00 NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "backuptask_pkey" for table "backuptask"
2010-03-23 13:11:00 NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "databasemaintenancelog_logid_pkey" for table "databasemaintenancelog"
2010-03-23 13:56:45 NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "grp1278b18ba2e_pkey" for table "grp1278b18ba2e"
2010-03-23 15:12:58 PANIC: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): Permission denied
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
2010-03-23 15:12:58 LOG: autovacuum process (PID 5380) exited with exit code 3
2010-03-23 15:12:58 LOG: terminating any other active server processes
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 WARNING: terminating connection because of crash of another server process
2010-03-23 15:12:58 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.
2010-03-23 15:12:58 HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-23 15:12:58 LOG: all server processes terminated; reinitializing
2010-03-23 15:12:59 LOG: database system was interrupted at 2010-03-23 15:00:54
2010-03-23 15:12:59 LOG: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory
2010-03-23 15:12:59 LOG: invalid primary checkpoint record
2010-03-23 15:12:59 LOG: could not open file "pg_xlog/000000010000000000000000" (log file 0, segment 0): No such file or directory
2010-03-23 15:12:59 LOG: invalid secondary checkpoint record
2010-03-23 15:12:59 PANIC: could not locate a valid checkpoint record
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
2010-03-23 15:12:59 LOG: startup process (PID 4916) exited with exit code 3
2010-03-23 15:12:59 LOG: aborting startup due to startup process failure
2010-03-23 15:12:59 LOG: logger shutting down
Bonjour,
Voici mon problème après 4Heures de bon fonctionnement.
Could not open process token "error code-5"
Impossible de relancer le service apres un redemarrage du serveur.
Windows 2003 entreprise 32 bit serveur membre , 4giga de ram.
postgre 8.2 (obligatoire pour mon appli)
J'ai vérifier shared_buffers =32 MB
Le compte postgre est utilisateur local et n'est pas dans le groupe administrateur.
J'ai tout essayé rien n'a solutionné mon problème.
Dans les log , j'ai vu plusieurs problème , impossible d'ecrire xlog ......; j'ai refait tout les droits sur le dossier Postgre de program files rien à faire .
le service ne démarre pas.
Merci d'avance de votre aide.
Pages : 1
