Hi,
On 11/17/2016 06:02 PM, Jean Louis wrote:
I am sorry, that I filed bug in the wrong package, it was
unintentional mistake. It should be in mysql-server. And I know all
about specifics.
In my case, there is nothing that I have changed in my Mysql
configuration from the plain install. That is why I filed the
bug. Otherwise I would look first on my side.
And I was surprised it did not work, as I was used to the stability
and certainty when upgrading.
I could not find the solution
I was reading other bugs and I found:
[mysqld]
secure_file_priv = /var/lib/mysql
So I have put it in /etc/mysql/conf.d and now I got it working. Even I
don't even know what is it about, as being so lazy to read the
documentation. Sorry.
Still I think it should not be like that, the upgrade should go
smooth, especially for databases. Nothing angers me, thank you for
putting attention. I am supporter of free software and use Debian on
remote servers.
Jean Louis
Hi,
In this case, the server defaults to
secure_file_priv=/var/lib/mysql-files, and will require this directory
to be created.
This is a big change to make in a stable release, but the old behavior
was a potential security risk, so we felt it was justified. The upgrade
_should_ have created this directory automatically, so if it failed for
you then there's probably something with your environment we didn't
account for. If you have any console logs or mysql error logs from the
update it would be good if you can attach them to the bug.
One important note, however:
The solution you note, setting secure_file_priv=/var/lib/mysql (the data
directory) is not a good one. You should either set it to NULL or to a
separate, empty directory owned by the mysql user.
The secure_file_priv setting determines where the server is allowed to
read and write files using import/export operations. Setting it to the
same location as the database will mean that any user of your database
can get full access.
--
Lars
On Tue, Nov 15, 2016 at 12:10:10PM +0000, Robie Basak wrote:
Hi Jean,
On Tue, Nov 15, 2016 at 12:08:18PM +0100, Jean Louis wrote:
sudo apt-get update
sudo apt-get upgrad
* What exactly did you do (or not do) that was effective (or
ineffective)?
Starting or configuring mysql-server-5.5 hangs forever. System is broken.
* What was the outcome of this action?
It hangs forever.
Unfortunately I think this isn't enough for anyone to understand what
happened in your case. This is a problem statement, not a bug report.
Clearly a simple upgrade on a fresh install of jessie works; otherwise
we would have thousands of bug reports. Something must be different on
your system, but we do not know what that is. Please provide full steps
to reproduce your problem so that we may figure that out.
I see that several bugs have been filed and marked as RESOLVED, how
they can be resolved when it is happening over and over again.
Because they are different bugs with different root causes. This
particular issue was determined to be something that needs to be fixed
in akonadi packaging and is now being tracked in bug 843534. Presumably
though you have a different issue as you did not mention akonadi in your
bug report.
Please understand that your report cannot be addressed because you have
not provided enough information. If this angers you, try reading
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html which is a great
essay that explains this problem well.
Please file a new bug report with full steps on how to reproduce your
bug. If it turns out to have a common root cause, we can always mark it
as a duplicate later.
Robie
_______________________________________________
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
