Skip to main content

phpMyAdmin export failing

keat63
I'm trying to export part of a table and I'm being prompted with the following error. File not found.

Comments

10 comments

Date Votes
  • cPanelLauren
    Hi @keat63 Is anything else noted in the MySQL or cPanel error logs in reference to this? The error here is kind of vague.
    0
  • keat63
    Good point. Here are the contents for var/lib/server.err, although I'm not sure what i'm looking at. 150104 10:46:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150104 10:46:32 [Note] Plugin 'FEDERATED' is disabled. 150104 10:46:32 InnoDB: The InnoDB memory heap is disabled 150104 10:46:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150104 10:46:32 InnoDB: Compressed tables use zlib 1.2.3 150104 10:46:32 InnoDB: Using Linux native AIO 150104 10:46:32 InnoDB: Initializing buffer pool, size = 128.0M 150104 10:46:32 InnoDB: Completed initialization of buffer pool 150104 10:46:32 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 150104 10:46:32 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 150104 10:46:33 InnoDB: Waiting for the background threads to start 150104 10:46:34 InnoDB: 5.5.40 started; log sequence number 4603927 150104 10:46:34 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 150104 10:46:34 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 150104 10:46:34 [Note] Server socket created on IP: '0.0.0.0'. 150104 10:46:34 [Note] Event Scheduler: Loaded 0 events 150104 10:46:34 [Note] /usr/sbin/mysqld: ready for connections.
    And cpanel error log [2019-01-25 10:46:10 +0000] info [xml-api] Successfully verified signature for cpanel (key types: release). mmap() failed: [12] Cannot allocate memory mmap() failed: [12] Cannot allocate memory PHP Fatal error: Out of memory (allocated 561332224) (tried to allocate 276471808 bytes) in /usr/local/cpanel/base/3rdparty/phpMyAdmin/libraries/classes/Response.php on line 279 [2019-01-25 10:46:59 +0000] warn [whostmgrd] The subprocess (php) exited with an error: The subprocess reported error number 255 when it ended. at /usr/local/cpanel/Cpanel/Server/Handlers/SubProcess.pm line 251. Cpanel::Server::Handlers::SubProcess::_report_subprocess_errors(Cpanel::Server::Handlers::SubProcess=HASH(0x39b0008)) called at /usr/local/cpanel/Cpanel/Server/Handlers/SubProcess.pm line 109 Cpanel::Server::Handlers::SubProcess::handler(Cpanel::Server::Handlers::SubProcess=HASH(0x39b0008), "subprocess_name", "php", "subprocess_pid_to_reap", 31397, "subprocess_read_handle", GLOB(0x39470a0), "subprocess_write_handle", ...) called at cpsrvd.pl line 6910 cpanel::cpsrvd::cgiHandler(__CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, 1, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__) called at cpsrvd.pl line 6687 cpanel::cpsrvd::phpHandler(__CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, 1, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__) called at cpsrvd.pl line 6344 cpanel::cpsrvd::dodoc_whostmgrd() called at cpsrvd.pl line 1835 cpanel::cpsrvd::dodoc(HASH(0x1377d78)) called at cpsrvd.pl line 1580 cpanel::cpsrvd::handle_one_connection(14) called at cpsrvd.pl line 991 cpanel::cpsrvd::script() called at cpsrvd.pl line 339
    Possibly an out of memory error ?
    0
  • cPanelLauren
    Hi @keat63 The first looks like potential tablespace issues in InnoDB but potentially not related to this. The second one looks like you've exhausted internal php memory. The only problem with this is it's phpmyadmin's php memory limit that is being exhausted. If you only want to increase the memory limit for phpMyAdmin, you need to change the memory_limit value in both /usr/local/cpanel/3rdparty/etc/php.ini and/usr/local/cpanel/3rdparty/etc/phpmyadmin/php.ini. This defaults right now to 128mb, the catch is that the changes you make won't be preserved.The easiest solution in this case would be to use mysqldump to create a backup of the database. Thanks!
    0
  • Benjamin D.
    Same. I recently upgraded to WHM 76.0.X and phpMyAdmin now fails to export database tables whereas before it had no problem at all. WHM 76 introduced phpMyAdmin version 4.8.3 which has this known bug. Any plans on integrating a newer phpMyAdmin version soon cPanel??? phpMyAdmin no longer streams the export data " Issue #14478 " phpmyadmin/phpmyadmin
    0
  • shaun
    You may want to try changing "Max cPanel process memory" in tweak settings in the WHM to a higher value also. How big is the database your trying to export?
    0
  • cPanelLauren
    Hi @Benjamin D.
    Any plans on integrating a newer phpMyAdmin version soon cPanel???

    Yes, as a matter of fact, we have planned an update to phpmyadmin for v80 of cPanel
    0
  • Benjamin D.
    Hey @shaun thanks for your interest in working around this issue. In my case, it's set on default value (768 MB). Do you think making it 2GB will solve the issue? The DB I noticed this phpMyAdmin export blank page crash is about 180MB. It used to work perfectly fine before I upgrade. Upgrading anything nowadays just breaks functionality. I need to stop upgrading. It's just too much anxiety for me. Thanks Lauren. Looking forward to it, but as I see it, it's not gonna be offered to the "stable" (this word made me giggle a lot for some reason) branch before maybe mid summer or even later. That's bad, really bad.
    0
  • shaun
    @Benjamin D. You can give it a go. I saw this issue with client and raising that value solved the problem. It's not ideal to raise the limit, it is meant to keep cPanel from eating all of your memory but if your server has a decent chunk of ram in it you should be able to without too much worry.
    0
  • Benjamin D.
    @Benjamin D. You can give it a go. I saw this issue with client and raising that value solved the problem. It's not ideal to raise the limit, it is meant to keep cPanel from eating all of your memory but if your server has a decent chunk of ram in it you should be able to without too much worry.

    Got 64GB, barely using 5GB out of it at any given time. I have it set to 2048 MB now. I am pleased to report that your suggestion actually seems to make it work adequately now! So basically, if the DB grows some more and the issue comes back, all I should theorically have to do is to pump up the cPanel max RAM allocation in TWEAK SETTINGS and it should work again, I guess. Thanks!
    0
  • keat63
    Maybe updating to V76 caused the issue at my end.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post