-
-
Notifications
You must be signed in to change notification settings - Fork 557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot understand migration error reasons #1530
Comments
The start of the stacktrace seems to be missing, and the error message. |
Oops.... I think i found reason, it's my carelessness. df -h I'm sorry. |
Please explain what it might look like? I will posting more full report in future. |
Ah, you may notice that the lines you showed start with |
Many thanks! ) |
Damn, another error... Couldn't write to #<SB-SYS:FD-STREAM for "socket, peer: /var/lib/mysql/mysql.sock" {1028B0ADA3}>: Will try to use TCP instead of unix sockets |
Damn, another error ( From console: ` Welcome to LDB, a low-level debugger for the Lisp runtime environment. No errors in pgloader.log file. Last records:
I don't understand what i need to do to fix it... Can anybody assist to make this problem more... clear? Thank you! |
Found: #962 Will try to use "with prefetch rows = 10000" |
Hello!
After ~24h of migration (source DB size ~ 200Gb, not so quick RAID solution) i got error. I can't understand reasons of erorr, please assist (if possible) to understand it.
Thank you!
OS: Rocky Linux 8.8 (Green Obsidian)
postgres (PostgreSQL) 15.4 (dnf, https://download.postgresql.org/pub/repos)
MariaDB: 10.11.5-MariaDB
pgloader version "3.6.7~devel" (dnf)
compiled with SBCL 2.2.10-1.rhel8
Goal of migration: transfer the Zabbix 6.0.21 LTS partitioned DB from MariaDB to PostgreSQL (without TimescaleDB ATM) via Unix sockets (single host enviroment). This is TEST server, no zabbix-server daemon is running.
DS size (on disk) on failure time.
Source (mariadb): ~172Gb
Destination (postgresql): ~210Gb
No
Yes but it too complicated without reasons understanding.
What i did:
sudo -u postgres pgloader zabbix_migrate.load
Content of "zabbix_migrate.load":
Result (console):
Result (pgloader.log):
The "systemctl status" shows both servers in alive state ATM.
The text was updated successfully, but these errors were encountered: