Author Topic: Error opening qATK on cluster  (Read 564 times)

0 Members and 1 Guest are viewing this topic.

Offline Chandrasekar

  • New QuantumATK user
  • *
  • Posts: 2
  • Country: tw
  • Reputation: 0
    • View Profile
Error opening qATK on cluster
« on: November 27, 2024, 15:08 »
Dear Developers,

We encountered the following error while opening the current version of atkpython (qATK_2024.09) on our laboratory server. The Version qATK_2023.12 works fine. Our license provider is TSRI in Taiwan. 

We use CentOS7 on our server.

Error message:
[joinet@sea101-sever-master ~]$ atkpython

cat: /usr/lib64/libc.so.6: version `GLIBC_2.25' not found (required by /cluster/cad/synopsys/qatk/2024.09/lib/pinned-libs/libstdc++.so.6)

cat: /usr/lib64/libc.so.6: version `GLIBC_2.18' not found (required by /cluster/cad/synopsys/qatk/2024.09/lib/pinned-libs/libstdc++.so.6)

(……)

Is it related to the new version of the qATK or our server OS version?

I really appreciate any help you can provide.

Offline filipr

  • QuantumATK Staff
  • Heavy QuantumATK user
  • *****
  • Posts: 82
  • Country: dk
  • Reputation: 6
  • QuantumATK developer
    • View Profile
Re: Error opening qATK on cluster
« Reply #1 on: November 27, 2024, 16:01 »
CentOS7 is no longer supported in v. 2024.09, see https://docs.quantumatk.com/intro/installation/technical_hardware.html#specific-platform-requirements. Specifically it is because 2024.09 is linked against a newer glibc (fundamental Linux library) that is incompatible with the one that is available on CentOS7.

You either have to continue to use v. 2023.12, see if the cluster has machines with a newer OS and run on those, or ask your cluster admin to install a supported OS on the nodes. Note that CentOS7 had its end-of-life June 30, 2024: https://www.redhat.com/en/topics/linux/centos-linux-eol

Offline Chandrasekar

  • New QuantumATK user
  • *
  • Posts: 2
  • Country: tw
  • Reputation: 0
    • View Profile
Re: Error opening qATK on cluster
« Reply #2 on: November 27, 2024, 16:47 »
Hi Filipr,

Thanks for your response. Noted it. I will convey this message to our system admin and find a way to solve this issue.

Thank you again.