Project

General

Profile

Actions

Bug #5125

closed

Migration script 'rudder-upgrade-database' displays unwanted logs

Added by Nicolas PERRON over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

The use of the script will display these lines, containing unwanted messages from psql:

server:/var/rudder/configuration-repository # /opt/rudder/bin/rudder-upgrade-database
Upgrade script for Rudder database.

This script updates the format of all the id used, from Integer to BigInt
Please note that it will stop the Rudder web interface temporarily at the beginning of the migration, for a few seconds
Checking the database...The ruddersysevents IDs need migrating. Let's go!
   77723 lines used, approximately 0% of total available, you may migrate later.
Please note that this script will stop the Rudder Web Interface for several seconds during the first part of the migration
Do you want to migrate now? (y/n)y
Stopping the Rudder web interface... Done.
Renaming the old tables, and recreating new ones with proper id format...psql:/opt/rudder/share/upgrade-tools/dbMigration-change-ids-in-tables.sql:67: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "ruddersysevents_pkey1" for table "ruddersysevents" 
psql:/opt/rudder/share/upgrade-tools/dbMigration-change-ids-in-tables.sql:99: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "archivedruddersysevents_pkey1" for table "archivedruddersysevents" 
 Done
Restarting the Rudder web interface...2014-06-24 17:55:24.735:INFO::Redirecting stderr/stdout to /var/log/rudder/webapp/2014_06_24.stderrout.log
 Done.
Checking the number of entries to migrate... Done
[...]


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4831: Reports cannot be inserted into postgresql due to a limit on idsReleasedFrançois ARMAND2014-05-07Actions
Actions

Also available in: Atom PDF