Tag Info

New answers tagged

0

Solution: I actually got it to work, and i found out that it mcrypt was causing all the problems, not mysql as i first thought. This is how i managed to solve it: Mcrypt extension is missing in 14.04 server for mysql Thanks for helping me out! :)


0

The key clue is probably this line in the output: dpkg: dependency problems prevent configuration of mysql-server: mysql-server depends on mysql-server-5.5; however: Package mysql-server-5.5 is not configured yet. Make sure mysql is entirely removed/purged sudo apt-get remove --purge mysql-server mysql-client mysql-common sudo apt-get remove --purge ...


0

You can try to download all the packages manually and try. this type of installation you dont get 'unable to locate somePackage' go to this link (assuming you want to install latest mysql version) Then select your platform as "Ubuntu Linux". And download all the packages according to Ubuntu version and whether your computer is 64bit or 32bit. (dont ...


0

It's not an issue. The listing in the first link is for the contents of the Ubuntu 14.04.1 ISO, and doesn't have anything to do with the contents of a mirror (the second link).


0

I solve it! Before the appearance of problem I've update the Ubuntu base. So the solution is dead simple: reboot the system! :)


1

It seems that the mysql-server was installed but not configured. This can happen when apt ist interrupted, for example by Ctrl-C. You can finish configuration of installed packages by issuing sudo dpkg --configure -a and then install all the missing packages by issuing sudo apt-get -f install. If you are running into problems doing that, I'd suggest ...


0

I think you have forgot your user name for mySQL. so please enter the correct user name and password when you type mysql command. for eg $mysql -u root -p $Enter Password: Note: Default user name and password is ------ root


1

The default path to served files in Ubuntu 14.04 has changed from /var/www to /var/www/html, mainly for security reasons. The packaging has been overhauled quite significantly. /etc/apache2/conf.d/ is now /etc/apache2/conf-available/ and /etc/apache2/conf-enabled/, to match the existing sites-enabled/ and mods-enabled/ mechanisms. The simplest way to ...


0

I think you're going at it the wrong way. You are having dependency issues trying to install MySQL Workbench 6.0.9, when you could easily install MySQL Workbench 6.0.8 in Ubuntu 14.04 from the Ubuntu Software Center or from the terminal using the command: sudo apt-get install mysql-workbench


0

It seems that each of apt-get and pip installed their own version of the library. Try removing system mysql with sudo apt-get remove python-mysqldb, and you should have something like this: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: python-mysqldb 0 upgraded, 0 newly ...


0

have you tried this sudo apt-get update --fix-missing sudo apt-get build-dep mysql-client5.5 mysql-server5.5 sudo apt-get -f install Try that and let me know how it foes for you..


-1

You need to completely remove mysql. Beleive me, I tryied. dpkg will not do this alone. See http://stackoverflow.com/questions/10853004/removing-mysql-5-5-completely If you are in a hurry sudo service mysql stop #or mysqld sudo killall -9 mysql sudo killall -9 mysqld sudo apt-get remove --purge mysql-server mysql-client mysql-common sudo apt-get ...


0

From comments in the mariadb documentation: To fix the "libmysqlclient18:amd64 5.5.34+maria-1~saucy (Multi-Arch: no) is not co-installable with libmysqlclient18 which has multiple installed instances" problem: The problem is that libmysqlclient18:i386 was not fully removed by the automated install. Rather than "messing" with /var/lib/dpkg/status, my ...


0

Try Below command it should stop the mysql service at your end : sudo service mysql stop Let me know if it doesn't, I can brief ahead if you have difficulties.


0

It looks to me like library versions mismatch - you build on newer system (14.04) linking to one version of library and start it on a bit older (12.04), using different version of the library.


0

I too had this problem on Debian Wheezy. All I could do was to kill the mysql process manually, run my apt-get update, and that worked fine.


2

Yes, that approach is as save as any normal use of sudo. When you use sudo, the password is cached, in the default configuration. And you use a dummy command to put the password into that standard cache, by a command doing nothing, as root - which is certainly not dangerous. sudoonly Because your example uses mysqldump, which also uses a password, I'd ...


1

Create a symbolic link sudo ln -s /usr/lib/i386-linux-gnu/libgnome-keyring.so.0 /usr/lib/libgnome-keyring.so.0 sudo ln -s /usr/lib/i386-linux-gnu/libgnome-keyring.so.0.2.0 /usr/lib/libgnome-keyring.so.0.2.0



Top 50 recent answers are included