How to fix "Error occurred when calling system catalog"

43 views
Skip to first unread message

Kladizkov theone

unread,
Jul 14, 2023, 9:05:31 AM7/14/23
to MariaDB ColumnStore
Hi there,

When we run queries, at certain time we receive this eror.

ERROR 1815 (HY000) at line 1: Internal error: MCS-2033: Error occurred when calling system catalog.

How can we fix this error? Is this due to any limitations of NFS that we use? I believe the system catalog is stored in the /var/lib/columnstore in NFS.

Please help.

pantonis

unread,
Jul 15, 2023, 4:12:05 AM7/15/23
to MariaDB ColumnStore
I have exactly the same issue.

I dont know how to resolve it. I keep restarting server and it goes away but it happens all the time.

before restarting I run 
service mariadb status and I always observe the following output which is I don't know if it is related

 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>
Jul 15 10:07:54 vm.mcs.net mariadbd[215620]: ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc>

Kladizkov theone

unread,
Jul 17, 2023, 3:54:24 AM7/17/23
to MariaDB ColumnStore
The error "ERROR 1815 (HY000) at line 1: Internal error: MCS-2033: Error occurred when calling system catalog." is most received when the queries are more frequent. As if the NFS read operation cannot keep up. I don't have to restart the server as the issue is more sporadic. I'm still not 100% sure if its related to NFS performance.

pantonis

unread,
Jul 20, 2023, 1:43:23 AM7/20/23
to MariaDB ColumnStore
We observed this during times where we have no activity at all. Just one simple query every 5 mins for 30 minutes.

drrtuy

unread,
Jul 22, 2023, 11:20:02 AM7/22/23
to MariaDB ColumnStore
Hi!

Sorry to hear that. Are you both talking MCS 23.02.4 that is shipped with MDB 11.1.1 or not?
If not I suggest to upgrade to this version.

@Kladizkov theone syscat is spread b/w multiple files in /var/lib/columnstore/data1/.

The error message suggest me your system periodically can't resolve the hostname that is used in ExeMgr1 section in /etc/columnstore/Columnstore.xml.
`ClientRotator caught exception: InetStreamSocket::connect: connect() error: Cannot assign requested address to: InetStreamSoc`

Regards,
Roman


четверг, 20 июля 2023 г. в 08:43:23 UTC+3, pantonis:

pantonis

unread,
Aug 1, 2023, 1:30:18 AM8/1/23
to MariaDB ColumnStore
I have upgraded to  11.0.2
Still getting the same error.

pantonis

unread,
Aug 1, 2023, 1:34:41 AM8/1/23
to MariaDB ColumnStore
this is what I have in Columnstore.xml 

        <ExeMgr1>
                <IPAddr>127.0.0.1</IPAddr>
                <Port>8601</Port>
                <Module>unassigned</Module>
        </ExeMgr1>

How is it possible not to resolve 127.0.0.1?



On Saturday, 22 July 2023 at 18:20:02 UTC+3 drrtuy wrote:

drrtuy

unread,
Aug 8, 2023, 9:25:22 AM8/8/23
to MariaDB ColumnStore
JFYI 11.0.2 still uses the same 6.4.8.


вторник, 1 августа 2023 г. в 08:30:18 UTC+3, pantonis:

drrtuy

unread,
Aug 8, 2023, 9:27:45 AM8/8/23
to MariaDB ColumnStore
There is no resolution for IP addresses but can you confirm the author has it set to IP and not to a hostname?

Regards,
Roman

вторник, 1 августа 2023 г. в 08:34:41 UTC+3, pantonis:

pantonis

unread,
Sep 25, 2023, 1:19:20 PM9/25/23
to MariaDB ColumnStore
Im having this issue in SkySql. The most worrying part is that the support just restarts the service without even trying to resolve the issue.

drrtuy

unread,
Oct 19, 2023, 1:42:22 PM10/19/23
to MariaDB ColumnStore

Sky used to have an outdated version of MCS + some limitations with their maintenance routines. They still have corner cases which can manifest themselves this way.

Regards,
Roman

понедельник, 25 сентября 2023 г. в 20:19:20 UTC+3, pantonis:
Reply all
Reply to author
Forward
0 new messages