[request-tracker-maintainers] Bug#781833: Bug#781833: upgrade from 4.0.13 to 4.2.8 failed
Max Kosmach
max at tcen.ru
Mon Apr 6 16:38:39 UTC 2015
Hi, Dominic
Problem replicated, log below
Steps to reproduce:
1 - first attempt to upgrade via dbconfig fail
(my primary RT - RT update innvocation fail because my RT modifications
my dev RT - dbcondig can't backup 4.0.13 DB because lack of disk space)
2 - continue with upgrade after fixing problem
3 - upgrade fail with "DBD::Pg::st execute failed: ERROR: column
"disabled" of relation "scrips" already exists"
log from dpkg:
> Настраивается пакет request-tracker4 (4.2.8-3) …
Configuring package (in russian)
> **WARNING**
> **WARNING** If you are using mod_perl or any form of persistent perl
> **WARNING** process such as FastCGI, you will need to restart your
> **WARNING** web server and any persistent processes now.
> **WARNING**
> **WARNING** For mod_perl this means
> **WARNING**
> **WARNING** invoke-rc.d apache2 stop && invoke-rc.d apache2 start
> **WARNING**
> **WARNING**
> **WARNING** If you are using mod_perl or any form of persistent perl
> **WARNING** process such as FastCGI, you will need to restart your
> **WARNING** web server and any persistent processes now.
> **WARNING**
> **WARNING** For mod_perl this means
> **WARNING**
> **WARNING** invoke-rc.d apache2 stop && invoke-rc.d apache2 start
> **WARNING**
> dbconfig-common: writing config to /etc/dbconfig-common/request-tracker4.conf
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.13-1.pgsql.
> error encountered backing up the old database:
> pg_dump: [архиватор] could not write to output file: На устройстве не осталось свободного места
no free space on device (russian)
> dbconfig-common: request-tracker4 configure: retrying.
> dbconfig-common: writing config to /etc/dbconfig-common/request-tracker4.conf
> creating database backup in /var/cache/dbconfig-common/backups/request-tracker4_4.0.13-1.pgsql.
> applying upgrade script for 4.0.13-1 -> 4.0.19.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Now inserting data.
> Done inserting data.
> Done.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Now inserting data.
> Done inserting data.
> Done.
> applying upgrade script for 4.0.13-1 -> 4.2.3.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Enter RT version you're upgrading from:
> Going to apply following upgrades:
> * 4.1.0
> * 4.1.1
> * 4.1.4
> * 4.1.5
> * 4.1.6
> * 4.1.7
> * 4.1.8
> * 4.1.9
> * 4.1.10
> * 4.1.11
> * 4.1.12
> * 4.1.13
> * 4.1.14
> * 4.1.15
> * 4.1.16
> * 4.1.17
> * 4.1.18
> * 4.1.19
> * 4.1.20
> * 4.1.21
> * 4.1.22
> * 4.1.23
> * 4.2.1
> * 4.2.2
> * 4.2.4
> * 4.2.6
> * 4.2.7
> * 4.2.8
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if you want apply above upgrades:
> Going to apply following upgrades:
> * 4.1.0
> * 4.1.1
> * 4.1.4
> * 4.1.5
> * 4.1.6
> * 4.1.7
> * 4.1.8
> * 4.1.9
> * 4.1.10
> * 4.1.11
> * 4.1.12
> * 4.1.13
> * 4.1.14
> * 4.1.15
> * 4.1.16
> * 4.1.17
> * 4.1.18
> * 4.1.19
> * 4.1.20
> * 4.1.21
> * 4.1.22
> * 4.1.23
> * 4.2.1
> * 4.2.2
> Processing 4.1.0
> Now inserting data.
> Processing 4.1.1
> Now populating database schema.
> Now inserting database ACLs.
> Now inserting data.
> Processing 4.1.4
> Now populating database schema.
> Now inserting data.
> Processing 4.1.5
> Now populating database schema.
> Now inserting data.
> Processing 4.1.6
> Now inserting data.
> Processing 4.1.7
> Now populating database schema.
> Processing 4.1.8
> Now populating database schema.
> Processing 4.1.9
> Now inserting data.
> Processing 4.1.10
> Now populating database schema.
> Processing 4.1.11
> Now populating database schema.
> Processing 4.1.12
> Now inserting data.
> Processing 4.1.13
> Now populating database schema.
> Processing 4.1.14
> Now populating database schema.
> Processing 4.1.15
> Now inserting data.
> Processing 4.1.16
> Now inserting data.
> Processing 4.1.17
> Now inserting data.
> Processing 4.1.18
> Now inserting data.
> Processing 4.1.19
> Now populating database schema.
> Processing 4.1.20
> Now inserting data.
> Processing 4.1.21
> Now inserting data.
> Processing 4.1.22
> Now populating database schema.
> Now inserting data.
> [13319] [Mon Apr 6 15:41:58 2015] [info]: Going to delete all SMIMEKeyNotAfter attributes (/usr/share/request-tracker4/etc/upgrade/4.1.22/content:61)
> Processing 4.1.23
> Now inserting database indexes.
> Processing 4.2.1
> Now inserting data.
> Processing 4.2.2
> Now inserting data.
> Done.
> applying upgrade script for 4.0.13-1 -> 4.2.4.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Enter RT version you're upgrading from:
> Going to apply following upgrades:
> * 4.2.4
> * 4.2.6
> * 4.2.7
> * 4.2.8
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if you want apply above upgrades:
> Going to apply following upgrades:
> * 4.2.4
> Processing 4.2.4
> Now inserting data.
> Done.
> applying upgrade script for 4.0.13-1 -> 4.2.6.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Enter RT version you're upgrading from:
> Going to apply following upgrades:
> * 4.2.6
> * 4.2.7
> * 4.2.8
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if you want apply above upgrades:
> Going to apply following upgrades:
> * 4.2.6
> Processing 4.2.6
> Now inserting data.
> Done.
> applying upgrade script for 4.0.13-1 -> 4.2.7.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Enter RT version you're upgrading from:
> Going to apply following upgrades:
> * 4.2.7
> * 4.2.8
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if you want apply above upgrades:
> Going to apply following upgrades:
> * 4.2.7
> Processing 4.2.7
> Now inserting data.
> Done.
> dbconfig-common: flushing administrative password
> applying upgrade script for 4.0.13-1 -> 4.0.19.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Now inserting data.
> Done inserting data.
> Done.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Now inserting data.
> Done inserting data.
> Done.
> applying upgrade script for 4.0.13-1 -> 4.2.3.
> Working with:
> Type: Pg
> Host: localhost
> Port:
> Name: requesttracker4
> User: requesttracker4
> DBA: requesttracker4 (No DBA)
> Enter RT version you're upgrading from:
> Going to apply following upgrades:
> * 4.1.0
> * 4.1.1
> * 4.1.4
> * 4.1.5
> * 4.1.6
> * 4.1.7
> * 4.1.8
> * 4.1.9
> * 4.1.10
> * 4.1.11
> * 4.1.12
> * 4.1.13
> * 4.1.14
> * 4.1.15
> * 4.1.16
> * 4.1.17
> * 4.1.18
> * 4.1.19
> * 4.1.20
> * 4.1.21
> * 4.1.22
> * 4.1.23
> * 4.2.1
> * 4.2.2
> * 4.2.4
> * 4.2.6
> * 4.2.7
> * 4.2.8
>
> Enter RT version if you want to stop upgrade at some point,
> or leave it blank if you want apply above upgrades:
> Going to apply following upgrades:
> * 4.1.0
> * 4.1.1
> * 4.1.4
> * 4.1.5
> * 4.1.6
> * 4.1.7
> * 4.1.8
> * 4.1.9
> * 4.1.10
> * 4.1.11
> * 4.1.12
> * 4.1.13
> * 4.1.14
> * 4.1.15
> * 4.1.16
> * 4.1.17
> * 4.1.18
> * 4.1.19
> * 4.1.20
> * 4.1.21
> * 4.1.22
> * 4.1.23
> * 4.2.1
> * 4.2.2
> Processing 4.1.0
> Now inserting data.
> Processing 4.1.1
> Now populating database schema.
> [13426] [Mon Apr 6 15:42:14 2015] [critical]: DBD::Pg::st execute failed: ERROR: column "disabled" of relation "scrips" already exists at /usr/share/request-tracker4/lib/RT/Handle.pm line 528. (/usr/share/request-tracker4/lib/RT.pm:390)
> DBD::Pg::st execute failed: ERROR: column "disabled" of relation "scrips" already exists at /usr/share/request-tracker4/lib/RT/Handle.pm line 528.
> error encountered processing /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3:
> /usr/share/dbconfig-common/scripts/request-tracker4/upgrade/pgsql/4.2.3 exited with non-zero status
06.04.2015 17:42, Max Kosmach пишет:
> Hi, Dominic
>
> I'm sorry, but I can't reproduce problem on dev instance of RT4.
> So I try to reproduce on copy of production VM as soon as I can make new
> instance from backups.
>
>
> 06.04.2015 14:01, Max Kosmach пишет:
>> Hi, Dominic
>>
>> 05.04.2015 19:04, Dominic Hargreaves пишет:
>>> On Fri, Apr 03, 2015 at 05:55:32PM +0300, Max Kosmach wrote:
>>>> Package: request-tracker4
>>>> Version: 4.2.8-3
>>>> Severity: important
>>>>
>>>>
>>>> Upgrade from 4.0.13-1 to 4.2.8-3 failed on one of my instance of RT4
>>>> Upgrade from 4.0.19 to 4.2.8-1 - worked.
>>>>
>>>> I don't know where I can find full upgrade logs.
>>>> In RT admin page in RT upgrade history I see:
>>>
>>> They are output to the dpkg session (ie to STDOUT). I assume you didn't
>>> manage to capture those?
>>
>> Yes, dpkg output was overwritten by other messages.
>>
>>> The only way I can see that a given database
>>> upgrade would have been attempted several times is if there was some
>>> sort
>>> of error during the initial upgrade (dbconfig-common, which the RT
>>> packages
>>> use to manage the database upgrades, may offer to retry actions in
>>> some cases). Without seeing a transcript of the dpkg run it's going
>>> to be quite difficult to work out what happened here in order to be able
>>> to fix anything. Do you have any more recollections of what happened?
>>>
>>> What is the current state of your system? Does RT work? And does
>>> dpkg think the package is configured?
>>
>> RT is working now, but i don't know if internal db structure fully
>> correct or not.
>> dpkg thinks that package is fully configured because I refuse upgrading
>> via dbconfig after error.
>>
>> I'll try to make temporary VM with archive db and 4.0.13 RT and try to
>> reproduce this problem.
>>
>> PS. I have another very similar RT instance (cloned from main) with
>> other uprgade path: 4.0.13->4.0.19->4.2.8
>> I have no problem with upgrade at this instance.
>>
>
>
--
With best wishes
Max
More information about the pkg-request-tracker-maintainers
mailing list