Bug #1511158 “package mysql-server-5.6 5.6.27-0ubuntu1 failed to...” : Bugs : mysql-5.6 package : Ubuntu

Revision history for this message

ken78724 (koymkg) wrote on 2015-10-29:

#1

.etc.apparmor.d.usr.sbin.mysqld.txt Edit (973 bytes, text/plain; charset="utf-8")
AptOrdering.txt Edit (666 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.9 KiB, text/plain; charset="utf-8")
Df.txt Edit (627 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (51.4 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (89.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (5.3 KiB, application/x-gzip)
HookError_ubuntu.txt Edit (828 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (20.7 KiB, text/plain; charset="utf-8")
KernLog.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Logs.var.log.mysql.error.log.txt Edit (90.6 KiB, text/plain; charset="utf-8")
MySQLConf.etc.mysql.my.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.cnf.txt Edit (682 bytes, text/plain; charset="utf-8")
MySQLConf.etc.mysql.mysql.conf.d.mysqld.cnf.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Robie Basak (racb) wrote on 2015-10-30:

#2

From log:

2015-10-28 17:30:23 15986 [Note] InnoDB: Completed initialization of buffer pool
2015-10-28 17:30:23 15986 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 640 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!
2015-10-28 17:30:23 15986 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2015-10-28 17:30:23 15986 [ERROR] Plugin 'InnoDB' init function returned error.
2015-10-28 17:30:23 15986 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-10-28 17:30:23 15986 [ERROR] Unknown/unsupported storage engine: InnoDB
2015-10-28 17:30:23 15986 [ERROR] Aborting

2015-10-28 17:30:23 15986 [Note] Binlog end

Revision history for this message

Robie Basak (racb) wrote on 2015-10-30:

#3

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in mysql-5.6 (Ubuntu):
status:	New → Incomplete

Revision history for this message

ken78724 (koymkg) wrote on 2015-11-06:

#4

Please set Bug 1511158 as a new bug and take notice of 10 or 11 crash reports suggesting I'm right. At 7:45 AM ppa:nem/system by the Kedek failed on my Wily Werewolf 15.10.1.

Yes mysqld inhouse 5.6.27-0ubuntu1 Config work arounds alleviated reoccurring grey screen crashes, but I can't solve the Bug,

the Lockring password etc and so far the Bug disallows every new update sent.

do set Bug 1511158 Ubuntu 15.10 mysqld 5.6.27-0ubuntu1 as a new bug. We have not solved the problems, which lets Kedek's ppa perform.

please pool the crash reports sent from my PC.

thanks to Robie, Mary, Brian Murray, and Kedek ppa team! Hurray!!

ken78724

Revision history for this message

ken78724 (koymkg) wrote on 2015-11-06:

#5

just clicked on my sys update, which was accepted. will keep at it from here,

Revision history for this message

Robie Basak (racb) wrote on 2015-12-04:

#6

> Please set Bug 1511158 as a new bug and take notice of 10 or 11 crash reports suggesting I'm right.

I'm sorry, I still don't understand your issue. Please could you read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, provide steps on how to reproduce your issue on a fresh Ubuntu system and then change the bug status back to New? Without this information, we cannot tell whether this is a bug or a local configuration problem.

Revision history for this message

ken78724 (koymkg) wrote on 2015-12-14:

#7

following a terminal sudo apt-get update & sudo apt-get upgrade & then clicking on a update notice my screen fluttered / crashed on facebook; I waded through greyed out screen and tried to get you an image. So far no one on launchpad nor on ubuntuforum has suggested a way to collect info regards either or both bugs. Nor have I come across a work around. Regretably I fly to see my GKids in two days. mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Changed in mysql-5.6 (Ubuntu):
assignee:	nobody → ken78724 (koymkg)

ken78724 (koymkg) on 2015-12-14

Changed in mysql-5.6 (Ubuntu):
assignee:	ken78724 (koymkg) → nobody

Revision history for this message

Robie Basak (racb) wrote on 2015-12-14:

#8

I appreciate the problems you're facing, but unfortunately I can't help you through the bug tracker. Pointers to community support can be found at http://www.ubuntu.com/support/community

I suggest continuing to try to get help on ubuntuforums.org and perhaps askubuntu.com for your specific problem.

I appreciate that there are a large number of "bug reports" for the MySQL packaging with similar failures. This is due to the packaging not being great at handling misconfiguration and this can definitely be improved. I am working on this in the latest MySQL packaging both in Debian and Ubuntu. There are a number of underlying improvements that can be made but unfortunately the automated crash reports do not usually give me enough information to know which underlying causes to focus on or which bugs for the underlying issues to pool them against. So I can only really mark the bugs as Incomplete or Invalid.

In the meantime, I'm marking this issue as Incomplete here on the bug tracker, as without exact steps to independently reproduce the issue this isn't a bug in Ubuntu that a developer can directly fix in its current state. I appreciate that you can reproduce the problem on your system easily enough, but this isn't the same as a developer being able to reproduce the system separately.

Since developers use the bug tracker to plan ongoing work, if I don't mark it like this then this merely hampers Ubuntu development efforts by making the bug tracker less useful to developers.

Revision history for this message

ken78724 (koymkg) wrote on 2015-12-14: Re: [Bug 1511158] Re: package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

#9

Download full text (5.2 KiB)

thx/Seasons Greetings Robie. For now, I don't know which way to turn except
seeing months down the tubes

   1. I acknowledge I'm the who lost a few very valuable work when a bug
   crashed my PC, which I can't fix whatever has caused my fluttering greyed
   out monitor screen, leading to crash after crash, saying for example
   mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess
   installed post-installation script returned error exit status 1
   2. I must set my ailing PC the side, save my files to my cloud; and when
   feasible wipe this new WD 1T HD clean, then I guess, install 15.04 in lieu
   of 15.10
   3. Already, alternatively I bought a new laptop got me Win 8.1
   obsessively wanting to auto-upgrade to Win 10full of advertisements. I
   mean, to get the peace of mind Linux brings, that I must partition that new
   laptop's HD and very carefully select and install an OS having better
   reports

Again, Seasons Greetings!!!!
ken

On Mon, Dec 14, 2015 at 7:37 AM, Robie Basak <email address hidden>
wrote:

> I appreciate the problems you're facing, but unfortunately I can't help
> you through the bug tracker. Pointers to community support can be found
> at http://www.ubuntu.com/support/community
>
> I suggest continuing to try to get help on ubuntuforums.org and perhaps
> askubuntu.com for your specific problem.
>
> I appreciate that there are a large number of "bug reports" for the
> MySQL packaging with similar failures. This is due to the packaging not
> being great at handling misconfiguration and this can definitely be
> improved. I am working on this in the latest MySQL packaging both in
> Debian and Ubuntu. There are a number of underlying improvements that
> can be made but unfortunately the automated crash reports do not usually
> give me enough information to know which underlying causes to focus on
> or which bugs for the underlying issues to pool them against. So I can
> only really mark the bugs as Incomplete or Invalid.
>
> In the meantime, I'm marking this issue as Incomplete here on the bug
> tracker, as without exact steps to independently reproduce the issue
> this isn't a bug in Ubuntu that a developer can directly fix in its
> current state. I appreciate that you can reproduce the problem on your
> system easily enough, but this isn't the same as a developer being able
> to reproduce the system separately.
>
> Since developers use the bug tracker to plan ongoing work, if I don't
> mark it like this then this merely hampers Ubuntu development efforts by
> making the bug tracker less useful to developers.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1511158
>
> Title:
> package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade:
> subprocess installed post-installation script returned error exit
> status 1
>
> Status in mysql-5.6 package in Ubuntu:
> Incomplete
>
> Bug description:
> On my cloned mirus AMED-64 PC housing a maxtor 750g, a maxed out 80g
> and 120 g seagate [disconnected] this week I upgraded Kubuntu 10.04 to
> 15.10, which had a shut down problem followed by Libre Office 5, wh...

thx/Seasons Greetings Robie. For now, I don't know which way to turn except
seeing months down the tubes

1. I acknowledge I'm the who lost a few very valuable work when a bug
   crashed my PC, which I can't fix whatever has caused my fluttering greyed
   out monitor screen, leading to crash after crash, saying for example
   mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess
   installed post-installation script returned error exit status 1
   2. I must set my ailing PC the side, save my files to my cloud; and when
   feasible wipe this new WD 1T HD clean, then I guess, install 15.04 in lieu
   of 15.10
   3. Already, alternatively I bought a new laptop got me Win 8.1
   obsessively wanting to auto-upgrade to Win 10full of advertisements. I
   mean, to get the peace of mind Linux brings, that I must partition that new
   laptop's HD and very carefully select and install an OS having better
   reports

Again, Seasons Greetings!!!!
ken

On Mon, Dec 14, 2015 at 7:37 AM, Robie Basak <1511158@bugs.launchpad.net>
wrote:

> I appreciate the problems you're facing, but unfortunately I can't help
> you through the bug tracker. Pointers to community support can be found
> at http://www.ubuntu.com/support/community
>
> I suggest continuing to try to get help on ubuntuforums.org and perhaps
> askubuntu.com for your specific problem.
>
> I appreciate that there are a large number of "bug reports" for the
> MySQL packaging with similar failures. This is due to the packaging not
> being great at handling misconfiguration and this can definitely be
> improved. I am working on this in the latest MySQL packaging both in
> Debian and Ubuntu. There are a number of underlying improvements that
> can be made but unfortunately the automated crash reports do not usually
> give me enough information to know which underlying causes to focus on
> or which bugs for the underlying issues to pool them against. So I can
> only really mark the bugs as Incomplete or Invalid.
>
> In the meantime, I'm marking this issue as Incomplete here on the bug
> tracker, as without exact steps to independently reproduce the issue
> this isn't a bug in Ubuntu that a developer can directly fix in its
> current state. I appreciate that you can reproduce the problem on your
> system easily enough, but this isn't the same as a developer being able
> to reproduce the system separately.
>
> Since developers use the bug tracker to plan ongoing work, if I don't
> mark it like this then this merely hampers Ubuntu development efforts by
> making the bug tracker less useful to developers.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1511158
>
> Title:
>   package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade:
>   subprocess installed post-installation script returned error exit
>   status 1
>
> Status in mysql-5.6 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   On my cloned mirus AMED-64 PC housing a maxtor 750g, a maxed out 80g
>   and 120 g seagate [disconnected] this week I upgraded Kubuntu 10.04 to
>   15.10, which had a shut down problem followed by Libre Office 5, which
>   would not save documents.
>
>   on about 10-23-15 +/- 6-8 pm, Ubuntu Forum lost my ken78724 upgrade
>   thread which was titled "10.04 to 15.10 ubuntu upgrade shut down
>   problem" Oddly the Forum copy of that thread "Has been lost?"
>
>   This afternoon immediately after doing a terminal "Sudo apt-get
>   update" and Sudo apt-get upgrade, and this several "mysql" terminal
>   commands [which I cannot cite], auto notices did autolaunchpad problem
>   submission. I cannot explain further.
>
>   Thanks for all that you do.
>
>   ken78724 - a 76 yr old activist
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.10
>   Package: mysql-server-5.6 5.6.27-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   ApportVersion: 2.19.1-0ubuntu4
>   Architecture: amd64
>   Date: Wed Oct 28 15:20:12 2015
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
>   InstallationDate: Installed on 2015-10-25 (3 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   Logs.var.log.daemon.log:
>
>   MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
>   MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
>    [mysqldump]
>    quick
>    quote-names
>    max_allowed_packet   = 16M
>   MySQLConf.etc.mysql.mysql.conf.d.mysqld.safe.syslog.cnf:
>    [mysqld_safe]
>    syslog
>   MySQLVarLibDirListing: ['mysql', 'ib_logfile1', 'ibdata1',
> 'debian-5.1.flag', 'debian-5.6.flag', 'ib_logfile0', 'mysql_upgrade_info']
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic
> root=UUID=c3d97030-c966-4676-b2e9-2ad5c108876f ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>    dpkg 1.18.2ubuntu5
>    apt  1.0.10.2ubuntu1
>   SourcePackage: mysql-5.6
>   Title: package mysql-server-5.6 5.6.27-0ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script returned
> error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1511158/+subscriptions
>

Revision history for this message

ken78724 (koymkg) wrote on 2016-01-11:

#10

allow me to withdraw this bug as I've decided to ask for help getting my bios configured; that is set my bios differently so I can copy all files from the maxtor 750g and maxed out 80g and 120 g seagates. I've just acknowledged I may be 76 but I'm a noob as far as how to get my WD 1tbit HD running 15.10 wily configed so it boots allowing me to copy every file from the maxtor 750g, the 80g and 120 g seagates and those on 12 other HDs

This will let me ask you to mark the two bugs identified per ken78724 as solved. the solutions are intellectual at this point as far as I"m concerned

Many thanks for all you do!!!!! Happy New Year !!!!

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-03-12:

#11

[Expired for mysql-5.6 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.6 (Ubuntu):
status:	Incomplete → Expired

Ubuntu
mysql-5.6 package

package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug Description

Duplicates of this bug

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntumysql-5.6 package

package mysql-server-5.6 5.6.27-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug Description

Duplicates of this bug

Other bug subscribers

Related questions

Bug attachments

Remote bug watches

Ubuntu
mysql-5.6 package