Discuss

discuss@lists.centos.org

34729 discussions

Table *** is marked as crashed and should be repaired
by Александр Кириллов 03 Dec '20

03 Dec '20

Hi, I've started migrating my sites to mariadb which is supposed to be a drop-in replacement of mysql. Both run on the same C6 box. DB folders were moved to a new location after both DB servers were stopped and properly upgraded. There were no reboots or power failures. Nevertheless I see these error messages in the logs: # cat /var/opt/rh/rh-mariadb102/log/mariadb/mariadb.log ... 2020-11-29 16:38:23 139882501732320 [Note] /opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: '10.2.22-MariaDB' socket: '/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock' port: 3307 MariaDB Server 2020-11-29 16:38:23 139882394105600 [Warning] Access denied for user 'UNKNOWN_MYSQL_USER'@'localhost' (using password: NO) 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table 'wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table 'wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [Warning] Checking table: './wordpress@002dstorefront/wp_wc_customer_lookup' ... 2020-11-29 17:16:17 140059421116384 [Note] /opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: '10.2.22-MariaDB' socket: '/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock' port: 3307 MariaDB Server 2020-11-29 17:16:18 140059356550912 [Warning] Access denied for user 'UNKNOWN_MYSQL_USER'@'localhost' (using password: NO) 2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_options' is marked as crashed and should be repaired 2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table 'wp_options' is marked as crashed and should be repaired 2020-11-29 17:20:01 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_options' 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_posts' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table 'wp_posts' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_posts' 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_actionscheduler_claims' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table 'wp_actionscheduler_claims' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_actionscheduler_claims' 2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_usermeta' is marked as crashed and should be repaired 2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table 'wp_usermeta' is marked as crashed and should be repaired 2020-11-29 17:22:28 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_usermeta' 2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table 'wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table 'wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_woocommerce_sessions' ... Note that after the crashed table was repaired mariadb reported multiple crashed tables in the same DB after restart. Any pointers? Never had such problems with mysqld. Is mariadb reliable and stable at all? # cat /etc/centos-release CentOS release 6.10 (Final) # rpm -qa '*maria*' rh-mariadb102-mariadb-server-utils-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-common-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-server-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-config-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-errmsg-10.2.22-1.el6.x86_64 rh-mariadb102-runtime-3.0-5.el6.x86_64 TIA, AK

1 1

Thunderbird 78
by Gerhard Schneider 03 Dec '20

03 Dec '20

The upstream provider decided to remove OpenGPG support in its thunderbird-78 packages, see https://bugzilla.redhat.com/show_bug.cgi?id=1886962 https://bugzilla.redhat.com/show_bug.cgi?id=1886958 https://bugzilla.redhat.com/show_bug.cgi?id=1837512 recommending to either use Mozilla binaries, use Flatpak or switch to Evolution Is there any plan to provide thunderbird-78-full packages in e.g. EPEL, ELRepo or somewhere else (like firefox-esr in Ubuntu) or should we use Mozilla binaries? Thank you in advance! Gerhard Schneider -- Gerhard Schneider Institute of Lightweight Design and e-Mail: gs(a)ilsb.tuwien.ac.at Structural Biomechanics (E317) Tel.: +43 1 58801 31716 TU Wien / Vienna / Austria Fax: +43 1 58801 31799 A-1060 Wien, Gumpendorfer Straße 7 http://www.ilsb.tuwien.ac.at/~gs/

2 1

firewall-cmd - bug or bad design
by Jon LaBadie 03 Dec '20

03 Dec '20

In my firewall I use an ipset as a geographical blacklist. A single addresses can be entered into the blacklist using CIDR notation or not, i.e. 111.222.111.222/32 OR 111.222.111.222 while a block of IP addresses can be entered using CIDR notation: 111.222.111.0/24 Both the ipset and firewall-cmd commands have ways to ask if an address has already been entered into the blacklist. The basic syntax is ipset test <blacklist> <ip_addr> firewall-cmd --ipset=<blacklist> --query-entry=<ip_addr> With ipset I can test a single address using CIDR or not regardless of how it was entered. If the entry was a block of addresses, any address within the block is reported as "in the ipset". firewall-cmd responds differently. If I entered "111.222.111.222/32" (i.e. using CIDR) into the list, firewall-cmd reports the address as "NOT entered" if I query the simple form "111.222.111.222" even though they are the same single address. Conversely, if the original entry was simple, the CIDR form is reported as "NOT entered". With block entries like 111.222.111.0/24, any address within the block is reported as "NOT entered"! Only the actual string entered, 111.222.111.0/24, is considered "entered". I use these types of queries to decided whether an ip address is already being blocked. Clearly relying the firewall-cmd query would lead to unnecessary entries. What do you think, Should I consider this simply a poor design decision or a reportable "bug"? -- Jon H. LaBadie jcu(a)labadie.us

1 0

Reminder: CentOS 6 EOL on 30 November 2020
by Johnny Hughes 02 Dec '20

02 Dec '20

All, This is a friendly reminder. CentOS 6.10 will EOL at the end of November 2020. During the first week in December 2020, the 6.10 directory will move to vault.centos.org Packages will still be available at: http://vault.centos.org/centos/6.10/ However, once moved, there will be no more updates pushed to vault.centos.org. Therefore, security issues will no longer be fixed, etc. You should take the rest of the month to either move to a newer versoin of CentOS Linux ... or to procure Extended el6 support from Red Hat (EUS RHEL 6). Thanks, Johnny Hughes

3 2

[rdo][centos8][repos] CentOS8 RDO-USSURI repo missing openvswitch2.13
by Ruslanas Gžibovskis 02 Dec '20

02 Dec '20

Hi all, I have an issue, in CentOS8 repos for RDO. It is refering to openvswitch2.13 name, but in the repos I can see openvswitch packages with version in version field, looks like in dependency field it is missing dash (-) or smth... here is a paste of repos and error message [0]. Or any other way how this could be fixed? thanks. and packages I can see [1] here. [0] http://paste.openstack.org/show/xEalilL1rRJSDTzNCGt1/ [1] http://paste.openstack.org/show/VLWrNFpRLatwq5qXP2kD/ -- Ruslanas Gžibovskis +370 6030 7030

1 0

Firefox, C-7, and... reboot?
by mark 02 Dec '20

02 Dec '20

Last night, for the second or third time since I upgraded from C6 to c7 this summer, I did something on firefox - I think it was reload a page, and my system rebooted. Yes, I have a ton of tabs open. I see nothing suspicious in /var/log/messages, or in /var/log/dmesg.old. I saw a mention of boltd? I think, but nothing more. Has anyone else had this problem? mark

1 0

Problem upgrading from 8.0 to 8.1
by Michael Schwartzkopff 02 Dec '20

02 Dec '20

Hi, I want to upgrade from 8.0 to 8.1 but yum update does not work. Still 8.0 Probably the cause is that I compiled DRBD myself because it was not available for 8.0 when I set up the machine. Now yum update says: Error: Problem 1: cannot install the best update candidate for package drbd-pacemaker-9.11.0-1.el8.x86_64 - nothing provides pacemaker needed by drbd-pacemaker-9.13.1-1.el8.x86_64 Problem 2: cannot install both drbd-utils-9.13.1-1.el8.x86_64 and drbd-utils-9.11.0-1.el8.x86_64 - package drbd-heartbeat-9.11.0-1.el8.x86_64 requires drbd-utils = 9.11.0-1.el8, but none of the providers can be installed - cannot install the best update candidate for package drbd-utils-9.11.0-1.el8.x86_64 - problem with installed package drbd-heartbeat-9.11.0-1.el8.x86_64 Problem 3: cannot install both drbd-utils-9.13.1-1.el8.x86_64 and drbd-utils-9.11.0-1.el8.x86_64 - package drbd-pacemaker-9.11.0-1.el8.x86_64 requires drbd-utils = 9.11.0-1.el8, but none of the providers can be installed - package drbd-9.13.1-1.el8.x86_64 requires drbd-utils = 9.13.1, but none of the providers can be installed - problem with installed package drbd-pacemaker-9.11.0-1.el8.x86_64 - cannot install the best update candidate for package drbd-9.11.0-1.el8.x86_64 - nothing provides pacemaker needed by drbd-pacemaker-9.13.1-1.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) with --nobest yum update runs through without doing anything and I sill have kernel 4.18.0-80.11.2.el8_0.x86_64 Any ideas how to update my server? Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 1

CentOS 7, as a 6in4 server
by Walter H. 02 Dec '20

02 Dec '20

Hello, I have a VPS at a hoster where I got 3 /64 ipv6 prefixes/subnets, that are routed; one for the VPS itself - let us call this srvprefix one for the tunnel, only ::1 (server side) and ::2 (home side) are used - let us call this tunnelprefix and one for my network at home - let us call this homeprefix now I'm just in test state, a CentOS VM is the other end of the tunnel; (when the server runs well, my CentOS ZBOX will become the other end of the tunnel) at the server the eth0 device has serverprefix::1, the sit1 device has tunnelprefix::1 the routing is set with /etc/sysconfig/network-scripts/route6-sit1 tunnelprefix::2 dev sit1 homeprefix::/64 via tunnelprefix::2 dev sit1 in sysctl.conf these are set net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 now I have to do these ip -6 neigh add proxy homeprefix::1 dev eth0 ip -6 neigh add proxy homeprefix::### dev eth0 the question, can I do something to avoid these "ip -6 neigh ..."? if yes, what? and how? can the hoster do something? if yes, what? Thanks, Walter my ISP told me that he won't deploy IPv6 within the next 5 years;

2 3

Re: [CentOS] Reminder: CentOS 6 EOL on 30 November 2020
by Fabian Arrotin 02 Dec '20

02 Dec '20

On 30/11/2020 13:39, Fabian Arrotin wrote: > On 30/11/2020 11:18, Manuel Wolfshant wrote: >> On 11/30/20 10:25 AM, Fabian Arrotin wrote: >>> On 09/11/2020 14:24, Johnny Hughes wrote: >>>> All, >>>> >>>> This is a friendly reminder. >>>> >>>> CentOS 6.10 will EOL at the end of November 2020. >>>> >>>> During the first week in December 2020, the 6.10 directory will move to >>>> vault.centos.org >>>> >>>> Packages will still be available at: >>>> >>>> http://vault.centos.org/centos/6.10/ >>>> >>>> However, once moved, there will be no more updates pushed to >>>> vault.centos.org. Therefore, security issues will no longer be fixed, >>>> etc. >>>> >>>> You should take the rest of the month to either move to a newer versoin >>>> of CentOS Linux ... or to procure Extended el6 support from Red Hat (EUS >>>> RHEL 6). >>>> >>>> Thanks, >>>> Johnny Hughes >>>> >>> As announced multiple times (on list[s], twitter, glog.centos.org and >>> even https://c6eol.centos.org) , CentOs 6 is now EOL and so is being >>> retired from mirror network. >>> It's currently being moved to (capped and limited bandwidth) >>> vault.centos.org and will be removed from mirror.centos.org (and so >>> external mirrors in the next hours/days). >>> mirrorlist.centos.org will also (like we do for all >>> outdated/unmaintained and unsecured releases) start answering "invalid >>> release" >>> >>> Kind Regards, >> >> Just to let you all know that starting from today, mirrorlist.centos.org nodes answer "Invalid release/repo/arch combination" and also that content was removed from mirrors. Johnny pushed the last updates yesterday, that went out to external mirrors . These mirrors will also delete all that content so if your *really* need to find such content, https://vault.centos.org is the only way to to go, but due to reduced bandwidth, capacity, we encourage you to use one of the external mirrors listed on vault.centos.org, with probably more resources/bandwidth that we currently have. Some of these mirrors also continue to offer rsync access. Cheers, and time to have a drink and celebrate 10 years of CentOS 6 : you served us all well ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Upgrade OpenSSH version to the latest stable version on CentOS Linux release 7.9.2009 (Core).
by Kaushal Shriyan 01 Dec '20

01 Dec '20

Hi, I am running CentOS Linux release 7.9.2009 (Core). Is there a way to upgrade OpenSSH version openssh-7.4p1-21.el7.x86_64 to the latest stable version openssh-server 8.4 using yum repositories or rpm binaries? Best Regards, Kaushal

4 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss