Re: upgrade from 2.18 to 2.2 fails with DBD::mysql::db do failed: Table 'bug_status' already exists at Bugzilla/DB.pm line 502 & more

Uh oh seg fault:
../checksetup.pl

Checking perl modules ...
Checking for       AppConfig (v1.52)   ok: found v1.56
Checking for             CGI (v2.93)   ok: found v3.05
Checking for    Data::Dumper (any)     ok: found v2.121
Checking for    Date::Format (v2.21)   ok: found v2.22
Checking for             DBI (v1.38)   ok: found v1.48
Checking for      File::Spec (v0.84)   ok: found v0.87
Checking for      File::Temp (any)     ok: found v0.14
Checking for        Template (v2.08)   ok: found v2.13
Checking for      Text::Wrap (v2001.0131) ok: found v2001.09291
Checking for    Mail::Mailer (v1.65)   ok: found v1.67
Checking for        Storable (any)     ok: found v2.09

The following Perl modules are optional:
Checking for              GD (v1.20)   ok: found v2.12
Checking for     Chart::Base (v1.0)    ok: found v2.3
Checking for     XML::Parser (any)     ok: found v2.34
Checking for       GD::Graph (any)     ok: found v1.43
Checking for GD::Text::Align (any)     ok: found v1.18
Checking for     PatchReader (v0.9.4)  ok: found v0.9.5

Checking user setup ...

The following settings in your localconfig file are no longer used:
  @severities, @priorities, @opsys, @platforms
This data is now controlled through the Bugzilla administrative interface.
We recommend you remove these settings from localconfig after checksetup
runs successfully.
Removing existing compiled templates ...
Precompiling templates ...
Checking for      DBD::mysql (v2.9003) ok: found v3.0000
Checking for           MySQL (v3.23.41) ok: found v4.1.12-standard

Renaming indexes...
Removing index 'creator_2' from the series table...
Renaming index bug_id to attachments_bug_id_idx...
Renaming index creation_ts to attachments_creation_ts_idx...
Renaming index bug_id to bug_group_map_bug_id_idx...
Renaming index group_id to bug_group_map_group_id_idx...
Renaming index priority to bugs_priority_idx...
Renaming index reporter to bugs_reporter_idx...
Renaming index product_id to bugs_product_id_idx...
Renaming index creation_ts to bugs_creation_ts_idx...
Renaming index assigned_to to bugs_assigned_to_idx...
Renaming index qa_contact to bugs_qa_contact_idx...
Renaming index short_desc to bugs_short_desc_idx...
Renaming index votes to bugs_votes_idx...
Renaming index bug_severity to bugs_bug_severity_idx...
Renaming index bug_status to bugs_bug_status_idx...
Renaming index delta_ts to bugs_delta_ts_idx...
Renaming index version to bugs_version_idx...
Renaming index component_id to bugs_component_id_idx...
Renaming index resolution to bugs_resolution_idx...
Renaming index target_milestone to bugs_target_milestone_idx...
Renaming index alias to bugs_alias_idx...
Renaming index op_sys to bugs_op_sys_idx...
Renaming index bug_id to bugs_activity_bug_id_idx...
Renaming index bug_when to bugs_activity_bug_when_idx...
Renaming index fieldid to bugs_activity_fieldid_idx...
Renaming index category_id to category_group_map_category_id_idx...
Renaming index bug_id to cc_bug_id_idx...
Renaming index who to cc_who_idx...
Renaming index product_id to components_product_id_idx...
Renaming index name to components_name_idx...
Renaming index blocked to dependencies_blocked_idx...
Renaming index dependson to dependencies_dependson_idx...
Renaming index sortkey to fielddefs_sortkey_idx...
Renaming index name to fielddefs_name_idx...
Renaming index type_id to flagexclusions_type_id_idx...
Renaming index type_id to flaginclusions_type_id_idx...
Renaming index bug_id to flags_bug_id_idx...
Renaming index setter_id to flags_setter_id_idx...
Renaming index requestee_id to flags_requestee_id_idx...
Renaming index product_id to group_control_map_product_id_idx...
Renaming index group_id to group_control_map_group_id_idx...
Renaming index member_id to group_group_map_member_id_idx...
Renaming index name to groups_name_idx...
Renaming index name to keyworddefs_name_idx...
Renaming index keywordid to keywords_keywordid_idx...
Renaming index bug_id to keywords_bug_id_idx...
Renaming index lastused to logincookies_lastused_idx...
Renaming index bug_id to longdescs_bug_id_idx...
Renaming index bug_when to longdescs_bug_when_idx...
Renaming index who to longdescs_who_idx...
Renaming index thetext to longdescs_thetext_idx...
Renaming index product_id to milestones_product_id_idx...
Renaming index userid to namedqueries_userid_idx...
Renaming index name to products_name_idx...
Renaming index login_name to profiles_login_name_idx...
Renaming index userid to profiles_activity_userid_idx...
Renaming index profiles_when to profiles_activity_profiles_when_idx...
Renaming index fieldid to profiles_activity_fieldid_idx...
Renaming index creator to series_creator_idx...
Renaming index name to series_categories_name_idx...
Renaming index series_id to series_data_series_id_idx...
Renaming index userid to tokens_userid_idx...
Renaming index user_id to user_group_map_user_id_idx...
Renaming index bug_id to votes_bug_id_idx...
Renaming index who to votes_who_idx...
Renaming index watcher to watch_watcher_idx...
Renaming index watched to watch_watched_idx...
Building Schema object from database...
Adding new table bz_schema ...
Initializing the new Schema storage...
Segmentation fault


> On Fri, 2005-10-14 at 16:10 -0400, Rob Kudyba wrote:
>> Adding new table bug_status ...
>> DBD::mysql::db do failed: Table 'bug_status' already exists at
>> Bugzilla/DB.pm line 502
>
> 	1) Drop the entire Bugzilla database. (DROP DATABASE bugs)
> 	2) Restore your back up of the 2.18 database.
> 	3) Run checksetup.
>
> 	It's #1 that's the most important, here, that you must do before you do
> #2.
>
> 	-Max
> --
> http://www.everythingsolved.com/
> Competent, Friendly Bugzilla Services. And Everything Else, too.
>
> _______________________________________________
> mozilla-webtools mailing list
> mozilla-webtools@mozilla.org
> http://mail.mozilla.org/listinfo/mozilla-webtools
>




0
rkudyba
10/14/2005 11:23:15 PM
netscape.mozilla.webtools 4144 articles. 0 followers. Follow

0 Replies
1000 Views

Similar Articles

[PageSpeed] 59
Get it on Google Play
Get it on Apple App Store

Reply:

Similar Artilces:

upgrade from 2.18 to 2.2 fails with DBD::mysql::db do failed: Table 'bug_status' already exists at Bugzilla/DB.pm line 502 & more
Tried this with the full package and via CVS...same error both ways. ./checksetup.pl Checking perl modules ... Checking for AppConfig (v1.52) ok: found v1.56 Checking for CGI (v2.93) ok: found v3.05 Checking for Data::Dumper (any) ok: found v2.121 Checking for Date::Format (v2.21) ok: found v2.22 Checking for DBI (v1.38) ok: found v1.48 Checking for File::Spec (v0.84) ok: found v0.87 Checking for File::Temp (any) ok: found v0.14 Checking for Template (v2.08) ok: found v2.13 Checking for Text::Wrap (v2...

RE: DBD::mysql::db do failed: BLOB/TEXT column 'status_whiteboard'can't have a default value at Bugzilla/DB.pm line 513
Hi, You need to use version 4 of mysql not version 5. I hope this helps, Benson Technical Support =09 DISCLAIMER This e-mail is confidential and intended solely for the use of the = individual to whom it is addressed. Any views or opinions presented are = solely those of the sender and should not be taken as representing the = view of Sentinel Products Ltd. If you are not the intended recipient, be = advised that you have received this e-mail in error and that any use, = dissemination, forwarding, printing, or copying of this e-mail is = strictly prohibited. If you have r...

DBD::mysql::db do failed: BLOB/TEXT column 'status_whiteboard' can't have a default value at Bugzilla/DB.pm line 513
Using: Windows bugzilla-2.22.1.tar.gz perl v5.8.8 DB-mysql v2.9004 ( I tried using v3.002 as well) mysql Ver 14.12 Distrib 5.0.26, for Win32 (ia32) While running perl checksetup.pl, I got errors like this: Building Schema object from database... Adding new table bz_schema ... Initializing the new Schema storage... Adding new table attach_data ... Adding new table attachments ... Adding new table bug_group_map ... Adding new table bug_severity ... Adding new table bug_status ... Adding new table bugs ... DBD::mysql::db do failed: ...

DBD::mysql::db do failed: Access denied for user: 'bugs@localhost' to database 'bugs' at Bugzilla/Series.pm line 173
While installing bugzilla I am getting the following error: Checking user setup ... Removing existing compiled templates ... Precompiling templates ... Checking for MySQL Server (v3.23.41) ok: found v4.0.17-nt Populating duplicates table... Migrating old chart data into database ... DBD::mysql::db do failed: Access denied for user: 'bugs@localhost' to database 'bugs' at Bugzilla/Series.pm line 173 Bugzilla::Series::writeToDatabase('Bugzilla::Series=HASH(0x2f4e660)') called at D:\bz\checksetup.pl line 3876 and then it is terminated. Can you tell...

Upgrading from 3.0.6 to 4.2.1 failed, Converting table bugs... DBD::mysql::db do failed
Hi, I'm trying to upgrade my bugzilla from 3.0.6 to 4.2.1 During ./checksetup.pl I get: Checking for DBD-mysql (v4.001) ok: found v4.005 Checking for MySQL (v5.0.15) ok: found v5.0.77 Removing index 'longdescs_thetext_idx' from the longdescs table... Bugzilla now uses the InnoDB storage engine in MySQL for most tables. Converting tables to InnoDB: Converting table attach_data... done. Converting table attachments... done. Converting table bug_group_map... done. Converting table bug_severity... done. Converting table bug_status......

DBD::mysql::db do failed: The user specified as a definer (''@'') does not exist
Hello, I' trying to update bugzilla, but I wanted to test it first on a clone of t= he virtual machine that runs bugzilla. Unfortunately, even before that I to= uch anything about the upgrade I cannot file a new bug with my clone machin= e, I got the following message: Software error: DBD::mysql::db do failed: The user specified as a definer (''@'') does not = exist [for Statement "INSERT INTO bugs (priority, reporter, bug_file_loc, p= roduct_id, rep_platform, assigned_to, qa_contact, cf_build, short_desc, eve= rconfirmed, cf_milestone, status_whiteboard, ...

Upgrade 2.18 --> 2.20: Can't find param named keywords at Bugzilla/Config.pm line 151.
Hello all! I just upgraded our testing installation of Bugzilla 2.18 to 2.20 (by downloading the new tarball (the way described in the docs), not via CVS), and now, after every attemt to edit an existing or create a new bug, I get the following error message: Can't find param named keywords at Bugzilla/Config.pm line 151. I had the german localization package GermZilla installed, I don't know if that's important. Thanks in advance, any help appreciated. Cheers, Philipp ...

Bugzilla 2.22 DBD::mysql::db failure (Duplicate entry 'A' for key 4)
Hi there, I just upgraded our office bugzilla to version 2.22 from 2.20. When we = update some bugs, I'm getting errors similar to the following. Can = anyone help? The sanity check doesn't return any errors either. ------ Software error: DBD::mysql::db do failed: Duplicate entry 'A' for key 4 at = Bugzilla/Bug.pm line 733 Bugzilla::Bug::AppendComment(6629, 1, 'Additionally, I\'ve followed the = following URL and checked th...', 'undef', '2006-05-08 20:45:59', = 'undef') called at /var/www/bugzilla-2.22/process_bug.cgi l...

Trying to upgrade from 3.0.6 to 4.2.1, but gets Converting table bugs... DBD::mysql::db do failed
During an upgrade from 3.0.6 to 4.2.1 I get while running checksetup.pl: Removing index 'longdescs_thetext_idx' from the longdescs table... Bugzilla now uses the InnoDB storage engine in MySQL for most tables. Converting tables to InnoDB: Converting table attach_data... done. Converting table attachments... done. Converting table bug_group_map... done. Converting table bug_severity... done. Converting table bug_status... done. Converting table bugs... DBD::mysql::db do failed: The used table type doesn't support FULLTEXT indexes [for Statement "ALTER TABLE bugs ENGI...

Migrating from Bugzilla 2.14 to Bugzilla 2.18 and new MySql DB
Hi, I would like to migrate/upgrade our Bugzilla 2.14 installation to Bugzilla 2.18 that would use different MySql DB (4.x). We are using MySql 4.x for Roller blogs hosting, and it would be good idea to use the same MySql DB for both, Roller blogs and Buzilla (that is the reason for DB mighration); currently we are running two instances of MySql, 3.x for Bugzilla, 4.x for Roller blog. What is the best way to export/import, move, migrate a Bugzilla bug DB to the new DB? Is XML export/import way to go, or DB dump or ?? Thanks, Lubos Lubos Pochman wrote: > I would like to m...

IManager fails after upgrade from 2.5.2 to 2.7.2
Attempted to upgrade IManager per readme from 2.5.2 to 2.7.2. Done for windows 7 iprint support. After upgrade when IManager launches, login screen is fine, but on initial screen all roles are listed down the left side but no icons across top (Home, configure, etc). Instead this appears com.novell.emframe.dev.eMFrameFactory.getMContext(Ljavax/servlet/http/HttpServletRequest;)Lcom/novell/emframe/dev/MContext; aA similar message appears when you attempt to manage a printer or anything else. ersion still says 2.5.2. Help please, how to uninstall, reinstall, whatever it take...

Smoke [5.15.2] v5.15.2-254-ge6c60e7 FAIL(M) linux 2.6.39-2-686-pae [debian] (i686/2 cpu)
Automated smoke report for 5.15.2 patch e6c60e7001deecc8d42edb12b568bc8b6463aa58 v5.15.2-254-ge6c60e7 gateway.bandsman.co.uk: AMD Athlon(tm) Dual Core Processor 4850e (AuthenticAMD 2511MHz) (i686/2 cpu) on linux - 2.6.39-2-686-pae [debian] using cc version 4.6.1 smoketime 3 minutes 28 seconds (average 3 minutes 28 seconds) Summary: FAIL(M) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m ...

DBD::mysql::db selectrow_hashref failed: Unknown column 'profiles.is_enabled' in 'field list'
Hi All, Error that i am facing is given below, please share your thoughts on how to resolve this issue Thank you very much, Versions: #Bugzilla 4.2.3 #perl 5.8.8 #mysql --version mysql Ver 14.12 Distrib 5.0.26, for suse-linux (x86_64) using readline 5.1 # mysqld --version mysqld Ver 5.0.26 for suse-linux on x86_64 (SUSE MySQL RPM) 1)Error that i am facing Software error: DBD::mysql::db selectrow_hashref failed: Unknown column 'profiles.is_enabled' in 'field list' [for Statement "SELECT profiles.userid,profiles.login_name,profiles.realn...

Bugzilla 2.18.4 upgrade to 2.20 failing on windows
I am attempting to upgrade my installation to the latest 2.20 release on Windows. I can get everything updated though CVS, but when I run checksetup.pl I get the following errors: Bareword "Bugzilla::Constants::DEFAULT_EMAIL_SETTINGS" not allowed while "strict subs" in use at checksetup.pl line 4387. Bareword "Bugzilla::Constants::DEFAULT_EMAIL_SETTINGS" not allowed while "strict subs" in use at checksetup.pl line 4512. Bareword "Bugzilla::Constants::DEFAULT_FLAG_EMAIL_SETTINGS" not allowed while "s trict subs" in us...

Web resources about - Re: upgrade from 2.18 to 2.2 fails with DBD::mysql::db do failed: Table 'bug_status' already exists at Bugzilla/DB.pm line 502 & more - netscape.mozilla.webtools

Resources last updated: 12/6/2015 8:56:54 PM