From troels at arvin.dk Wed Feb 17 16:44:44 2016 From: troels at arvin.dk (Troels Arvin) Date: Wed, 17 Feb 2016 16:44:44 +0000 (UTC) Subject: [rhelv6-list] THP: Why are they on by default? Message-ID: I've just had a situation with an RHEL 7 server where transparent hugepages (THP) might have contributed to a problem. And there are many projects/products which recommend turning THP off, eg: https://docs.oracle.com/database/121/UNXAR/appi_vlm.htm http://www.cloudera.com/documentation/enterprise/latest/topics/ cdh_admin_performance.html https://docs.mongodb.org/manual/tutorial/transparent-huge-pages/ http://www.chriscalender.com/disabling-transparent-hugepages-for-tokudb/ http://www-01.ibm.com/support/docview.wss?uid=swg21677458 I have also seen reports about THP ruining the performance on workstations. So which workloads actually benefit significantly from THP? Does someone know if Red Hat has considered turning them off by default? (There doesn't seem to be a mailing list for RHEL 7, so I'm using this mailing list instead. Which should be OK, as I believe there isn't much difference WRT THP between RHEL 6 and 7.) -- Troels Arvin From solarflow99 at gmail.com Wed Feb 17 17:59:49 2016 From: solarflow99 at gmail.com (solarflow99) Date: Wed, 17 Feb 2016 09:59:49 -0800 Subject: [rhelv6-list] THP: Why are they on by default? In-Reply-To: References: Message-ID: I really miss the mailing lists, I wish they had a way of gating them with the lousy web forums. On Feb 17, 2016 8:57 AM, "Troels Arvin" wrote: > I've just had a situation with an RHEL 7 server where transparent > hugepages (THP) might have contributed to a problem. And there are many > projects/products which recommend turning THP off, eg: > > https://docs.oracle.com/database/121/UNXAR/appi_vlm.htm > http://www.cloudera.com/documentation/enterprise/latest/topics/ > cdh_admin_performance.html > https://docs.mongodb.org/manual/tutorial/transparent-huge-pages/ > http://www.chriscalender.com/disabling-transparent-hugepages-for-tokudb/ > http://www-01.ibm.com/support/docview.wss?uid=swg21677458 > > I have also seen reports about THP ruining the performance on > workstations. > > So which workloads actually benefit significantly from THP? > > Does someone know if Red Hat has considered turning them off by default? > > (There doesn't seem to be a mailing list for RHEL 7, so I'm using this > mailing list instead. Which should be OK, as I believe there isn't much > difference WRT THP between RHEL 6 and 7.) > > > -- > Troels Arvin > > > _______________________________________________ > rhelv6-list mailing list > rhelv6-list at redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.j.smith at ieee.org Wed Feb 17 19:11:55 2016 From: b.j.smith at ieee.org (Bryan J Smith) Date: Wed, 17 Feb 2016 14:11:55 -0500 Subject: [rhelv6-list] THP: Why are they on by default? In-Reply-To: References: Message-ID: solarflow99 wrote: > I really miss the mailing lists, I wish they had a way of gating them with > the lousy web forums. That used to be possible ... before the days of GMail and users being ignorant of Message-ID threading in NNTP/SMTP. There is reddit, which I also think is lousy. But in all honesty, the Red Hat Access Portal does allow one to search issues a lot better than one could a mailing list ... Or even Google for that matter. I.e., I used to put in site:redhat.com on Google to make sure I didn't get "enthusiast" answers instead of RHEL ones, but now I just use the Portal. It's pretty good at concentrating a lot of knowledge, which is then marked verified, unverified, etc... with comments and additives, ratings, etc... Yes, I miss the days of NNTP/SMTP integrated web forums. But those are now gone. Again, GMail generation ignorant of Message-ID tracking. -- bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith From b.j.smith at ieee.org Wed Feb 17 19:19:06 2016 From: b.j.smith at ieee.org (Bryan J Smith) Date: Wed, 17 Feb 2016 14:19:06 -0500 Subject: [rhelv6-list] THP: Why are they on by default? In-Reply-To: References: Message-ID: Troels Arvin wrote: > I've just had a situation with an RHEL 7 server where transparent > hugepages (THP) might have contributed to a problem. There are many cases of THP causing issues, this is why Red Hat used to turn it off. But with the memory sizes of average servers today, sticking with 4KiB pages in the age of kernel 3+ is just not a remotely viable default. I.e., anything "certified" for RHEL7 _should_ have an installer, tuned profile, etc... that _disables_ them included. If not, that's on your ISV, not Red Hat. ;) > I have also seen reports about THP ruining the performance on > workstations. Er, um, what? Can you give a scenario where that is the case? I would tend to think it is the opposite, with large mallocs only _benefiting_ from THP. I cannot think of a case where they would not. I would think there would be general 32-bit malloc issues that have nothing to do with THP that might come up from time-to-time. I can think of a lot of cases of 32-bit issues on x86-64, but so little that are really impacted by THP. > So which workloads actually benefit significantly from THP? Things with large mallocs, which is very typical these days with all sorts of x86-64 services. And that's even before we look to virtualization. ;) > Does someone know if Red Hat has considered turning them off > by default? Red Hat _used_ to do this, because of select ISVs. But with RHEL7, ISVs have long been warned that it was going to change, and they needed to include installer changes, tools, etc... to address it. ISVs that did not do such during the long, extensive, high-touch Alpha and Beta periods really only have themselves to blame, especially if the application is certified on RHEL7. > (There doesn't seem to be a mailing list for RHEL 7, so I'm using this > mailing list instead. Which should be OK, as I believe there isn't much > difference WRT THP between RHEL 6 and 7.) Red Hat has tried to concentrate everything into its Portal for far more searchable reference, especially since Google tends to not always give a "RHEL preferable answer" -- at least that has long been my experience. There are other, independent lists and sites, from reddit to even CentOS (even if much of CentOS et al. is Red Hat hosted/sponsored these days). Otherwise, just create a login at the Portal and try searching there. -- bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith From larry.martell at gmail.com Tue Feb 23 03:17:51 2016 From: larry.martell at gmail.com (Larry Martell) Date: Mon, 22 Feb 2016 22:17:51 -0500 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 Message-ID: I am trying to get django 1.9 running in RHEL 6. I have installed python2.7 and when I try to install MySQLdb, I get the errors shown below. I have googled and googled and tried many different things, all with no success. Can anyone please let me know how I can get this going? # /usr/local/bin/pip2.7 install MySQL-python Collecting MySQL-python Downloading MySQL-python-1.2.5.zip (108kB) 100% |????????????????????????????????| 110kB 3.2MB/s Installing collected packages: MySQL-python Running setup.py install for MySQL-python ... error Complete output from command /usr/local/bin/python2.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-SPMNQU/MySQL-python/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-QrpP1S-record/install-record.txt --single-version-externally-managed --compile: running install running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying _mysql_exceptions.py -> build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/converters.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/connections.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/cursors.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/release.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/times.py -> build/lib.linux-x86_64-2.7/MySQLdb creating build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/CR.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/FIELD_TYPE.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/ER.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/FLAG.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/REFRESH.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/CLIENT.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants running build_ext building '_mysql' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,5,'final',1) -D__version__=1.2.5 -I/usr/include/mysql -I/usr/local/include/python2.7 -c _mysql.c -o build/temp.linux-x86_64-2.7/_mysql.o -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv -fPIC -fPIC -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -DMY_PTHREAD_FASTMUTEX=1 _mysql.c:44:23: error: my_config.h: No such file or directory _mysql.c:46:19: error: mysql.h: No such file or directory _mysql.c:47:26: error: mysqld_error.h: No such file or directory _mysql.c:48:20: error: errmsg.h: No such file or directory _mysql.c:88: error: expected specifier-qualifier-list before ?MYSQL? _mysql.c:102: error: expected specifier-qualifier-list before ?MYSQL_RES? _mysql.c: In function ?_mysql_Exception?: _mysql.c:146: warning: implicit declaration of function ?mysql_errno? _mysql.c:146: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:149: error: ?CR_MAX_ERROR? undeclared (first use in this function) _mysql.c:149: error: (Each undeclared identifier is reported only once _mysql.c:149: error: for each function it appears in.) _mysql.c:161: error: ?CR_COMMANDS_OUT_OF_SYNC? undeclared (first use in this function) _mysql.c:162: error: ?ER_DB_CREATE_EXISTS? undeclared (first use in this function) _mysql.c:163: error: ?ER_SYNTAX_ERROR? undeclared (first use in this function) _mysql.c:164: error: ?ER_PARSE_ERROR? undeclared (first use in this function) _mysql.c:165: error: ?ER_NO_SUCH_TABLE? undeclared (first use in this function) _mysql.c:166: error: ?ER_WRONG_DB_NAME? undeclared (first use in this function) _mysql.c:167: error: ?ER_WRONG_TABLE_NAME? undeclared (first use in this function) _mysql.c:168: error: ?ER_FIELD_SPECIFIED_TWICE? undeclared (first use in this function) _mysql.c:169: error: ?ER_INVALID_GROUP_FUNC_USE? undeclared (first use in this function) _mysql.c:170: error: ?ER_UNSUPPORTED_EXTENSION? undeclared (first use in this function) _mysql.c:171: error: ?ER_TABLE_MUST_HAVE_COLUMNS? undeclared (first use in this function) _mysql.c:200: error: ?ER_DUP_ENTRY? undeclared (first use in this function) _mysql.c:246: warning: implicit declaration of function ?mysql_error? _mysql.c:246: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c: In function ?_mysql_server_init?: _mysql.c:351: warning: label ?finish? defined but not used _mysql.c:268: warning: unused variable ?item? _mysql.c:267: warning: unused variable ?groupc? _mysql.c:267: warning: unused variable ?i? _mysql.c:267: warning: unused variable ?cmd_argc? _mysql.c:266: warning: unused variable ?s? _mysql.c: In function ?_mysql_ResultObject_Initialize?: _mysql.c:406: error: ?MYSQL_RES? undeclared (first use in this function) _mysql.c:406: error: ?result? undeclared (first use in this function) _mysql.c:411: error: ?MYSQL_FIELD? undeclared (first use in this function) _mysql.c:411: error: ?fields? undeclared (first use in this function) _mysql.c:425: error: ?_mysql_ResultObject? has no member named ?use? _mysql.c:428: warning: implicit declaration of function ?mysql_use_result? _mysql.c:428: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:430: warning: implicit declaration of function ?mysql_store_result? _mysql.c:430: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:431: error: ?_mysql_ResultObject? has no member named ?result? _mysql.c:434: warning: implicit declaration of function ?mysql_field_count? _mysql.c:434: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:438: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:442: warning: implicit declaration of function ?mysql_num_fields? _mysql.c:443: error: ?_mysql_ResultObject? has no member named ?nfields? _mysql.c:444: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:448: warning: implicit declaration of function ?mysql_fetch_fields? _mysql.c:489: error: ?BINARY_FLAG? undeclared (first use in this function) _mysql.c:512: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ResultObject_traverse?: _mysql.c:526: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:527: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ResultObject_clear?: _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:539: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ConnectionObject_Initialize?: _mysql.c:551: error: ?MYSQL? undeclared (first use in this function) _mysql.c:551: error: ?conn? undeclared (first use in this function) _mysql.c:584: error: ?_mysql_ConnectionObject? has no member named ?converter? _mysql.c:585: error: ?_mysql_ConnectionObject? has no member named ?open? _mysql.c:636: warning: implicit declaration of function ?mysql_init? _mysql.c:636: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:639: warning: implicit declaration of function ?mysql_options? _mysql.c:639: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:639: error: ?MYSQL_OPT_CONNECT_TIMEOUT? undeclared (first use in this function Tried installing mysql-devel, and that also failed: # yum install mysql-devel Loaded plugins: dellsysid, product-id, refresh-packagekit, security, subscription-manager Setting up Install Process Package mysql-devel is obsoleted by mysql-community-devel, trying to install mysql-community-devel-5.7.11-1.el6.x86_64 instead Resolving Dependencies --> Running transaction check ---> Package mysql-community-devel.x86_64 0:5.7.11-1.el6 will be installed --> Processing Dependency: mysql-community-libs(x86-64) = 5.7.11-1.el6 for package: mysql-community-devel-5.7.11-1.el6.x86_64 --> Processing Dependency: libmysqlclient.so.20()(64bit) for package: mysql-community-devel-5.7.11-1.el6.x86_64 --> Running transaction check ---> Package mysql-community-libs.x86_64 0:5.7.11-1.el6 will be obsoleting --> Processing Dependency: mysql-community-common(x86-64) = 5.7.11-1.el6 for package: mysql-community-libs-5.7.11-1.el6.x86_64 ---> Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be obsoleted --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi for package: mysql-server-5.5.44-1.el6.remi.x86_64 --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi for package: mysql-5.5.44-1.el6.remi.x86_64 --> Running transaction check ---> Package mysql.x86_64 0:5.5.44-1.el6.remi will be obsoleted ---> Package mysql-community-client.x86_64 0:5.7.11-1.el6 will be obsoleting ---> Package mysql-community-common.x86_64 0:5.7.11-1.el6 will be installed ---> Package mysql-community-server.x86_64 0:5.7.11-1.el6 will be obsoleting ---> Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be obsoleted --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 ---> Package mysql-server.x86_64 0:5.5.44-1.el6.remi will be obsoleted --> Finished Dependency Resolution Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18(libmysqlclient_16)(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18()(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18()(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18(libmysqlclient_18)(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18(libmysqlclient_18)(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest From gcraciun at transfond.ro Tue Feb 23 08:48:10 2016 From: gcraciun at transfond.ro (Gabriel S. Craciun) Date: Tue, 23 Feb 2016 08:48:10 +0000 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: References: Message-ID: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Do ypu have some custom repos enabled? ...like http://rpms.famillecollet.com/enterprise/6/remi/x86_64/ ? ..where from you installed those.remi. packages? -----Original Message----- From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of Larry Martell Sent: 23 februarie 2016 05:18 To: rhelv6-list at redhat.com Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 I am trying to get django 1.9 running in RHEL 6. I have installed python2.7 and when I try to install MySQLdb, I get the errors shown below. I have googled and googled and tried many different things, all with no success. Can anyone please let me know how I can get this going? # /usr/local/bin/pip2.7 install MySQL-python Collecting MySQL-python Downloading MySQL-python-1.2.5.zip (108kB) 100% |????????????????????????????????| 110kB 3.2MB/s Installing collected packages: MySQL-python Running setup.py install for MySQL-python ... error Complete output from command /usr/local/bin/python2.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-SPMNQU/MySQL-python/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-QrpP1S-record/install-record.txt --single-version-externally-managed --compile: running install running build running build_py creating build creating build/lib.linux-x86_64-2.7 copying _mysql_exceptions.py -> build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/converters.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/connections.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/cursors.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/release.py -> build/lib.linux-x86_64-2.7/MySQLdb copying MySQLdb/times.py -> build/lib.linux-x86_64-2.7/MySQLdb creating build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/CR.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/FIELD_TYPE.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/ER.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/FLAG.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/REFRESH.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants copying MySQLdb/constants/CLIENT.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants running build_ext building '_mysql' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,5,'final',1) -D__version__=1.2.5 -I/usr/include/mysql -I/usr/local/include/python2.7 -c _mysql.c -o build/temp.linux-x86_64-2.7/_mysql.o -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv -fPIC -fPIC -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -DMY_PTHREAD_FASTMUTEX=1 _mysql.c:44:23: error: my_config.h: No such file or directory _mysql.c:46:19: error: mysql.h: No such file or directory _mysql.c:47:26: error: mysqld_error.h: No such file or directory _mysql.c:48:20: error: errmsg.h: No such file or directory _mysql.c:88: error: expected specifier-qualifier-list before ?MYSQL? _mysql.c:102: error: expected specifier-qualifier-list before ?MYSQL_RES? _mysql.c: In function ?_mysql_Exception?: _mysql.c:146: warning: implicit declaration of function ?mysql_errno? _mysql.c:146: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:149: error: ?CR_MAX_ERROR? undeclared (first use in this function) _mysql.c:149: error: (Each undeclared identifier is reported only once _mysql.c:149: error: for each function it appears in.) _mysql.c:161: error: ?CR_COMMANDS_OUT_OF_SYNC? undeclared (first use in this function) _mysql.c:162: error: ?ER_DB_CREATE_EXISTS? undeclared (first use in this function) _mysql.c:163: error: ?ER_SYNTAX_ERROR? undeclared (first use in this function) _mysql.c:164: error: ?ER_PARSE_ERROR? undeclared (first use in this function) _mysql.c:165: error: ?ER_NO_SUCH_TABLE? undeclared (first use in this function) _mysql.c:166: error: ?ER_WRONG_DB_NAME? undeclared (first use in this function) _mysql.c:167: error: ?ER_WRONG_TABLE_NAME? undeclared (first use in this function) _mysql.c:168: error: ?ER_FIELD_SPECIFIED_TWICE? undeclared (first use in this function) _mysql.c:169: error: ?ER_INVALID_GROUP_FUNC_USE? undeclared (first use in this function) _mysql.c:170: error: ?ER_UNSUPPORTED_EXTENSION? undeclared (first use in this function) _mysql.c:171: error: ?ER_TABLE_MUST_HAVE_COLUMNS? undeclared (first use in this function) _mysql.c:200: error: ?ER_DUP_ENTRY? undeclared (first use in this function) _mysql.c:246: warning: implicit declaration of function ?mysql_error? _mysql.c:246: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c: In function ?_mysql_server_init?: _mysql.c:351: warning: label ?finish? defined but not used _mysql.c:268: warning: unused variable ?item? _mysql.c:267: warning: unused variable ?groupc? _mysql.c:267: warning: unused variable ?i? _mysql.c:267: warning: unused variable ?cmd_argc? _mysql.c:266: warning: unused variable ?s? _mysql.c: In function ?_mysql_ResultObject_Initialize?: _mysql.c:406: error: ?MYSQL_RES? undeclared (first use in this function) _mysql.c:406: error: ?result? undeclared (first use in this function) _mysql.c:411: error: ?MYSQL_FIELD? undeclared (first use in this function) _mysql.c:411: error: ?fields? undeclared (first use in this function) _mysql.c:425: error: ?_mysql_ResultObject? has no member named ?use? _mysql.c:428: warning: implicit declaration of function ?mysql_use_result? _mysql.c:428: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:430: warning: implicit declaration of function ?mysql_store_result? _mysql.c:430: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:431: error: ?_mysql_ResultObject? has no member named ?result? _mysql.c:434: warning: implicit declaration of function ?mysql_field_count? _mysql.c:434: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:438: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:442: warning: implicit declaration of function ?mysql_num_fields? _mysql.c:443: error: ?_mysql_ResultObject? has no member named ?nfields? _mysql.c:444: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:448: warning: implicit declaration of function ?mysql_fetch_fields? _mysql.c:489: error: ?BINARY_FLAG? undeclared (first use in this function) _mysql.c:512: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ResultObject_traverse?: _mysql.c:526: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:527: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ResultObject_clear?: _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c:539: error: ?_mysql_ResultObject? has no member named ?converter? _mysql.c: In function ?_mysql_ConnectionObject_Initialize?: _mysql.c:551: error: ?MYSQL? undeclared (first use in this function) _mysql.c:551: error: ?conn? undeclared (first use in this function) _mysql.c:584: error: ?_mysql_ConnectionObject? has no member named ?converter? _mysql.c:585: error: ?_mysql_ConnectionObject? has no member named ?open? _mysql.c:636: warning: implicit declaration of function ?mysql_init? _mysql.c:636: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:639: warning: implicit declaration of function ?mysql_options? _mysql.c:639: error: ?_mysql_ConnectionObject? has no member named ?connection? _mysql.c:639: error: ?MYSQL_OPT_CONNECT_TIMEOUT? undeclared (first use in this function Tried installing mysql-devel, and that also failed: # yum install mysql-devel Loaded plugins: dellsysid, product-id, refresh-packagekit, security, subscription-manager Setting up Install Process Package mysql-devel is obsoleted by mysql-community-devel, trying to install mysql-community-devel-5.7.11-1.el6.x86_64 instead Resolving Dependencies --> Running transaction check ---> Package mysql-community-devel.x86_64 0:5.7.11-1.el6 will be ---> installed --> Processing Dependency: mysql-community-libs(x86-64) = 5.7.11-1.el6 for package: mysql-community-devel-5.7.11-1.el6.x86_64 --> Processing Dependency: libmysqlclient.so.20()(64bit) for package: mysql-community-devel-5.7.11-1.el6.x86_64 --> Running transaction check ---> Package mysql-community-libs.x86_64 0:5.7.11-1.el6 will be ---> obsoleting --> Processing Dependency: mysql-community-common(x86-64) = 5.7.11-1.el6 for package: mysql-community-libs-5.7.11-1.el6.x86_64 ---> Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be obsoleted --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi for package: mysql-server-5.5.44-1.el6.remi.x86_64 --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi for package: mysql-5.5.44-1.el6.remi.x86_64 --> Running transaction check ---> Package mysql.x86_64 0:5.5.44-1.el6.remi will be obsoleted Package ---> mysql-community-client.x86_64 0:5.7.11-1.el6 will be obsoleting ---> Package mysql-community-common.x86_64 0:5.7.11-1.el6 will be ---> installed Package mysql-community-server.x86_64 0:5.7.11-1.el6 will ---> be obsoleting Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be ---> obsoleted --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 --> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: php-mysql-5.4.43-1.el6.remi.x86_64 ---> Package mysql-server.x86_64 0:5.5.44-1.el6.remi will be obsoleted --> Finished Dependency Resolution Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18(libmysqlclient_16)(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18()(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18()(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) Requires: libmysqlclient.so.18(libmysqlclient_18)(64bit) Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) libmysqlclient.so.18(libmysqlclient_18)(64bit) Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 (mysql57-community) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest _______________________________________________ rhelv6-list mailing list rhelv6-list at redhat.com https://www.redhat.com/mailman/listinfo/rhelv6-list -------------------------------- NOTICE OF CONFIDENTIALITY This E-mail message and its attachments (if any) are intended solely for the use of the addressees hereof. In addition, this message and the attachments (if any) may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. If you have received this message in error, please promptly notify the sender by reply E-mail and immediately delete this message from your system. From larry.martell at gmail.com Tue Feb 23 12:24:43 2016 From: larry.martell at gmail.com (Larry Martell) Date: Tue, 23 Feb 2016 07:24:43 -0500 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> References: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Message-ID: On Tue, Feb 23, 2016 at 3:48 AM, Gabriel S. Craciun wrote: > Do ypu have some custom repos enabled? ...like http://rpms.famillecollet.com/enterprise/6/remi/x86_64/ ? ..where from you installed those.remi. packages? This is a machine I just inherited and I really know nothing about it. It was running a Semantic Media Wiki (which uses MySQL and PHP), and I have broken that and now am frantically trying to fix it. I did this: # yum shell --enablerepo=remi > remove php-mysql > install php-mysqlnd > run Followed by this: yum install mysql-devel /usr/local/bin/pip2.7 install MySQL-python Now the MySQL server is down and will not come up. It fails with this: Fatal error: mysql.user table is damaged. Please run mysql_upgrade Looks like 5.7 is now installed whereas before it was running 5.5 (Server version: 5.5.44 MySQL Community Server (GPL) by Remi') It fails on start up with Fatal error: mysql.user table is damaged. Please run mysql_upgrade But how can I run mysql_upgrade if I can't start the server? > -----Original Message----- > From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of Larry Martell > Sent: 23 februarie 2016 05:18 > To: rhelv6-list at redhat.com > Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 > > I am trying to get django 1.9 running in RHEL 6. I have installed > python2.7 and when I try to install MySQLdb, I get the errors shown below. I have googled and googled and tried many different things, all with no success. Can anyone please let me know how I can get this going? > > # /usr/local/bin/pip2.7 install MySQL-python Collecting MySQL-python > Downloading MySQL-python-1.2.5.zip (108kB) > 100% |????????????????????????????????| 110kB 3.2MB/s Installing collected packages: MySQL-python > Running setup.py install for MySQL-python ... error > Complete output from command /usr/local/bin/python2.7 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-SPMNQU/MySQL-python/setup.py';exec(compile(getattr(tokenize, > 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-QrpP1S-record/install-record.txt > --single-version-externally-managed --compile: > running install > running build > running build_py > creating build > creating build/lib.linux-x86_64-2.7 > copying _mysql_exceptions.py -> build/lib.linux-x86_64-2.7 > creating build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/converters.py -> build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/connections.py -> build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/cursors.py -> build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/release.py -> build/lib.linux-x86_64-2.7/MySQLdb > copying MySQLdb/times.py -> build/lib.linux-x86_64-2.7/MySQLdb > creating build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/__init__.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/CR.py -> > build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/FIELD_TYPE.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/ER.py -> > build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/FLAG.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/REFRESH.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants > copying MySQLdb/constants/CLIENT.py -> build/lib.linux-x86_64-2.7/MySQLdb/constants > running build_ext > building '_mysql' extension > creating build/temp.linux-x86_64-2.7 > gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Dversion_info=(1,2,5,'final',1) > -D__version__=1.2.5 -I/usr/include/mysql > -I/usr/local/include/python2.7 -c _mysql.c -o build/temp.linux-x86_64-2.7/_mysql.o -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv -fPIC -fPIC -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -DMY_PTHREAD_FASTMUTEX=1 > _mysql.c:44:23: error: my_config.h: No such file or directory > _mysql.c:46:19: error: mysql.h: No such file or directory > _mysql.c:47:26: error: mysqld_error.h: No such file or directory > _mysql.c:48:20: error: errmsg.h: No such file or directory > _mysql.c:88: error: expected specifier-qualifier-list before ?MYSQL? > _mysql.c:102: error: expected specifier-qualifier-list before ?MYSQL_RES? > _mysql.c: In function ?_mysql_Exception?: > _mysql.c:146: warning: implicit declaration of function ?mysql_errno? > _mysql.c:146: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:149: error: ?CR_MAX_ERROR? undeclared (first use in this function) > _mysql.c:149: error: (Each undeclared identifier is reported only once > _mysql.c:149: error: for each function it appears in.) > _mysql.c:161: error: ?CR_COMMANDS_OUT_OF_SYNC? undeclared (first use in this function) > _mysql.c:162: error: ?ER_DB_CREATE_EXISTS? undeclared (first use in this function) > _mysql.c:163: error: ?ER_SYNTAX_ERROR? undeclared (first use in this function) > _mysql.c:164: error: ?ER_PARSE_ERROR? undeclared (first use in this function) > _mysql.c:165: error: ?ER_NO_SUCH_TABLE? undeclared (first use in this function) > _mysql.c:166: error: ?ER_WRONG_DB_NAME? undeclared (first use in this function) > _mysql.c:167: error: ?ER_WRONG_TABLE_NAME? undeclared (first use in this function) > _mysql.c:168: error: ?ER_FIELD_SPECIFIED_TWICE? undeclared (first use in this function) > _mysql.c:169: error: ?ER_INVALID_GROUP_FUNC_USE? undeclared (first use in this function) > _mysql.c:170: error: ?ER_UNSUPPORTED_EXTENSION? undeclared (first use in this function) > _mysql.c:171: error: ?ER_TABLE_MUST_HAVE_COLUMNS? undeclared (first use in this function) > _mysql.c:200: error: ?ER_DUP_ENTRY? undeclared (first use in this function) > _mysql.c:246: warning: implicit declaration of function ?mysql_error? > _mysql.c:246: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c: In function ?_mysql_server_init?: > _mysql.c:351: warning: label ?finish? defined but not used > _mysql.c:268: warning: unused variable ?item? > _mysql.c:267: warning: unused variable ?groupc? > _mysql.c:267: warning: unused variable ?i? > _mysql.c:267: warning: unused variable ?cmd_argc? > _mysql.c:266: warning: unused variable ?s? > _mysql.c: In function ?_mysql_ResultObject_Initialize?: > _mysql.c:406: error: ?MYSQL_RES? undeclared (first use in this function) > _mysql.c:406: error: ?result? undeclared (first use in this function) > _mysql.c:411: error: ?MYSQL_FIELD? undeclared (first use in this function) > _mysql.c:411: error: ?fields? undeclared (first use in this function) > _mysql.c:425: error: ?_mysql_ResultObject? has no member named ?use? > _mysql.c:428: warning: implicit declaration of function ?mysql_use_result? > _mysql.c:428: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:430: warning: implicit declaration of function ?mysql_store_result? > _mysql.c:430: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:431: error: ?_mysql_ResultObject? has no member named ?result? > _mysql.c:434: warning: implicit declaration of function ?mysql_field_count? > _mysql.c:434: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:438: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:442: warning: implicit declaration of function ?mysql_num_fields? > _mysql.c:443: error: ?_mysql_ResultObject? has no member named ?nfields? > _mysql.c:444: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:448: warning: implicit declaration of function ?mysql_fetch_fields? > _mysql.c:489: error: ?BINARY_FLAG? undeclared (first use in this function) > _mysql.c:512: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c: In function ?_mysql_ResultObject_traverse?: > _mysql.c:526: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:527: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c: In function ?_mysql_ResultObject_clear?: > _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:538: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c:539: error: ?_mysql_ResultObject? has no member named ?converter? > _mysql.c: In function ?_mysql_ConnectionObject_Initialize?: > _mysql.c:551: error: ?MYSQL? undeclared (first use in this function) > _mysql.c:551: error: ?conn? undeclared (first use in this function) > _mysql.c:584: error: ?_mysql_ConnectionObject? has no member named ?converter? > _mysql.c:585: error: ?_mysql_ConnectionObject? has no member named ?open? > _mysql.c:636: warning: implicit declaration of function ?mysql_init? > _mysql.c:636: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:639: warning: implicit declaration of function ?mysql_options? > _mysql.c:639: error: ?_mysql_ConnectionObject? has no member named ?connection? > _mysql.c:639: error: ?MYSQL_OPT_CONNECT_TIMEOUT? undeclared (first use in this function > > Tried installing mysql-devel, and that also failed: > > # yum install mysql-devel > Loaded plugins: dellsysid, product-id, refresh-packagekit, security, subscription-manager Setting up Install Process Package mysql-devel is obsoleted by mysql-community-devel, trying to install mysql-community-devel-5.7.11-1.el6.x86_64 instead Resolving Dependencies > --> Running transaction check > ---> Package mysql-community-devel.x86_64 0:5.7.11-1.el6 will be > ---> installed > --> Processing Dependency: mysql-community-libs(x86-64) = 5.7.11-1.el6 > for package: mysql-community-devel-5.7.11-1.el6.x86_64 > --> Processing Dependency: libmysqlclient.so.20()(64bit) for package: > mysql-community-devel-5.7.11-1.el6.x86_64 > --> Running transaction check > ---> Package mysql-community-libs.x86_64 0:5.7.11-1.el6 will be > ---> obsoleting > --> Processing Dependency: mysql-community-common(x86-64) = > 5.7.11-1.el6 for package: mysql-community-libs-5.7.11-1.el6.x86_64 > ---> Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be obsoleted > --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > --> Processing Dependency: > libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > --> Processing Dependency: > libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi > for package: mysql-server-5.5.44-1.el6.remi.x86_64 > --> Processing Dependency: real-mysql-libs(x86-64) = 5.5.44-1.el6.remi > for package: mysql-5.5.44-1.el6.remi.x86_64 > --> Running transaction check > ---> Package mysql.x86_64 0:5.5.44-1.el6.remi will be obsoleted Package > ---> mysql-community-client.x86_64 0:5.7.11-1.el6 will be obsoleting > ---> Package mysql-community-common.x86_64 0:5.7.11-1.el6 will be > ---> installed Package mysql-community-server.x86_64 0:5.7.11-1.el6 will > ---> be obsoleting Package mysql-libs.x86_64 0:5.5.44-1.el6.remi will be > ---> obsoleted > --> Processing Dependency: libmysqlclient.so.18()(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > --> Processing Dependency: > libmysqlclient.so.18(libmysqlclient_16)(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > --> Processing Dependency: > libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: > php-mysql-5.4.43-1.el6.remi.x86_64 > ---> Package mysql-server.x86_64 0:5.5.44-1.el6.remi will be obsoleted > --> Finished Dependency Resolution > Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) > Requires: libmysqlclient.so.18(libmysqlclient_16)(64bit) > Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) > libmysqlclient.so.18(libmysqlclient_16)(64bit) > Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 > (mysql57-community) > Not found > Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) > Requires: libmysqlclient.so.18()(64bit) > Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) > libmysqlclient.so.18()(64bit) > Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 > (mysql57-community) > Not found > Error: Package: php-mysql-5.4.43-1.el6.remi.x86_64 (@remi) > Requires: libmysqlclient.so.18(libmysqlclient_18)(64bit) > Removing: mysql-libs-5.5.44-1.el6.remi.x86_64 (@remi) > libmysqlclient.so.18(libmysqlclient_18)(64bit) > Obsoleted By: mysql-community-libs-5.7.11-1.el6.x86_64 > (mysql57-community) > Not found > You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest From hugh-brown at uiowa.edu Tue Feb 23 16:40:57 2016 From: hugh-brown at uiowa.edu (Brown, Hugh M) Date: Tue, 23 Feb 2016 16:40:57 +0000 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: References: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Message-ID: -----Original Message----- From: rhelv6-list-bounces at redhat.com [mailto:rhelv6-list-bounces at redhat.com] On Behalf Of Larry Martell Sent: Tuesday, February 23, 2016 6:25 AM To: Red Hat Enterprise Linux 6 (Santiago) discussion mailing-list Subject: Re: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 On Tue, Feb 23, 2016 at 3:48 AM, Gabriel S. Craciun wrote: > Do ypu have some custom repos enabled? ...like http://rpms.famillecollet.com/enterprise/6/remi/x86_64/ ? ..where from you installed those.remi. packages? This is a machine I just inherited and I really know nothing about it. It was running a Semantic Media Wiki (which uses MySQL and PHP), and I have broken that and now am frantically trying to fix it. I did this: # yum shell --enablerepo=remi > remove php-mysql > install php-mysqlnd > run Followed by this: yum install mysql-devel /usr/local/bin/pip2.7 install MySQL-python Now the MySQL server is down and will not come up. It fails with this: Fatal error: mysql.user table is damaged. Please run mysql_upgrade Looks like 5.7 is now installed whereas before it was running 5.5 (Server version: 5.5.44 MySQL Community Server (GPL) by Remi') It fails on start up with Fatal error: mysql.user table is damaged. Please run mysql_upgrade But how can I run mysql_upgrade if I can't start the server? I've got a stock RHEL6 system and mysql is at version 5.1 on that system. The mysql-community packages aren't from RedHat. It sounds like you have a variety of channels and custom repos enabled with a lot of conflicts. If you can, I'd reinstall the versions of mysql that were there, run a backup of the mysql db and the whole system. I'd then install the mysql-devel package from the same source as the remi packages you had before. This should allow your MySQL-python to be installed. Once you are back up and running, I'd probably build a new system that's a little cleaner. It looks like you have multiple repos providing mysql and the current system is a bit of a mess. Hugh From b.j.smith at ieee.org Tue Feb 23 17:27:31 2016 From: b.j.smith at ieee.org (Bryan J Smith) Date: Tue, 23 Feb 2016 12:27:31 -0500 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: References: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Message-ID: Any reason you guys aren't using [Red Hat] Software Collections ([RH]SCL) [1a] or Downstream (e.g., CentOS) [1b]? Related Red Hat Solution Article. [2] Understand you're attempting to load newer, Upstream software on older, sustained RHEL releases. That's rarely ideal, and you're going to be upgrading and breaking things. Instead, use what Red Hat came up with ... Red Hat came up with Software Collections so one can run newer database (e.g., MariaDB), scripting language (e.g., PHP, Python, etc...) and other versions, on older RHEL releases, like RHEL6. And Red Hat then maintains them (i.e., security backports) for 3+ years. [3] All supported, without all of the hacking and mess of trying to replace the core RHEL packages. They are installed under /opt and enabled using a set of fully supported Red Hat tools and procedures. E.g., the list of versions included with [RH]SCL 2.1, most supported through 2018, are in the 2.1 Release Notes, Section 1.2 [4], and include ... - PHP 5.6.5 (w/Pear 1.9.5), among earlier (5.5 and 5.4) versions - Python 2.7.8 and Python 3.4.2 - MariaDB 10.0.17 and MySQL 5.6.24 ... among others Again, Software Collections is by Red Hat and designed to co-exist with core scripting languages included with RHEL, while still sustained for 3+ years from release, with Red Hat regularly releasing newer Software Collection versions (about every 18-24 months or so). -- bjs [1a] https://access.redhat.com/documentation/en/red-hat-software-collections/ [1b] https://www.softwarecollections.org/en/ [2] https://access.redhat.com/solutions/472793 [3] https://access.redhat.com/support/policy/updates/rhscl [4] https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/2/html/2.1_Release_Notes/chap-RHSCL.html#sect-RHSCL-Features -- Bryan J Smith - http://www.linkedin.com/in/bjsmith From larry.martell at gmail.com Tue Feb 23 18:18:51 2016 From: larry.martell at gmail.com (Larry Martell) Date: Tue, 23 Feb 2016 13:18:51 -0500 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: References: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Message-ID: On Tue, Feb 23, 2016 at 12:27 PM, Bryan J Smith wrote: > Any reason you guys aren't using [Red Hat] Software Collections > ([RH]SCL) [1a] or Downstream (e.g., CentOS) [1b]? Related Red Hat > Solution Article. [2] > > Understand you're attempting to load newer, Upstream software on > older, sustained RHEL releases. That's rarely ideal, and you're going > to be upgrading and breaking things. > > Instead, use what Red Hat came up with ... > > Red Hat came up with Software Collections so one can run newer > database (e.g., MariaDB), scripting language (e.g., PHP, Python, > etc...) and other versions, on older RHEL releases, like RHEL6. And > Red Hat then maintains them (i.e., security backports) for 3+ years. > [3] > > All supported, without all of the hacking and mess of trying to > replace the core RHEL packages. They are installed under /opt and > enabled using a set of fully supported Red Hat tools and procedures. > > E.g., the list of versions included with [RH]SCL 2.1, most supported > through 2018, are in the 2.1 Release Notes, Section 1.2 [4], and > include ... > - PHP 5.6.5 (w/Pear 1.9.5), among earlier (5.5 and 5.4) versions > - Python 2.7.8 and Python 3.4.2 > - MariaDB 10.0.17 and MySQL 5.6.24 > ... among others > > Again, Software Collections is by Red Hat and designed to co-exist > with core scripting languages included with RHEL, while still > sustained for 3+ years from release, with Red Hat regularly releasing > newer Software Collection versions (about every 18-24 months or so). > > -- bjs > > [1a] https://access.redhat.com/documentation/en/red-hat-software-collections/ > [1b] https://www.softwarecollections.org/en/ > > [2] https://access.redhat.com/solutions/472793 > > [3] https://access.redhat.com/support/policy/updates/rhscl > > [4] https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/2/html/2.1_Release_Notes/chap-RHSCL.html#sect-RHSCL-Features Thanks to everyone for the help. I finally got this going. As for your questions, this is a new client I just started working for the other day. Some key people have quit and no one really knows anything about their environment. There is no sys admin (and I am developer and don't want to be a sysadmin). I was asked to come in and build a django app, so that I what I am working on. It's not in the scope of my job to redo their entire set up. All I can recommend is that they hire an experienced admin to do that. From b.j.smith at ieee.org Tue Feb 23 19:01:12 2016 From: b.j.smith at ieee.org (Bryan J Smith) Date: Tue, 23 Feb 2016 14:01:12 -0500 Subject: [rhelv6-list] Installing MySQLdb for python2.7 in RHEL 6 In-Reply-To: References: <18ACE6C30FF1454D93B4C039FB62EA762AEEF11D@SPO-MAIL.stfd.ro> Message-ID: Larry Martell wrote: > Thanks to everyone for the help. I finally got this going. Going is one thing. Working 1 year from now with security updates, is another. Just trying to point out what Red Hat offers. Otherwise, why run RHEL6? Just use any, Upstream distribution instead. > As for your questions, this is a new client I just started working for > the other day. Some key people have quit and no one really knows > anything about their environment. There is no sys admin (and I am > developer and don't want to be a sysadmin). > I was asked to come in and build a django app, so that I what I am > working on. It's not in the scope of my job to redo their entire set > up. All I can recommend is that they hire an experienced admin to do > that. Agreed. Until then, be aware of Red Hat Software Collections. It was designed by developers, to make it easier for sysadmins to ensure software compliance and so security updates don't break things. -- bjs