Skip to main content

phpMyAdmin - Error for some user

Comments

7 comments

  • Jcats
    Can you check the log file: /usr/local/cpanel/logs/error_log Does it contain any additional info?
    0
  • morteza3245
    there is lot of logs what kind of logs should see?
    0
  • Jcats
    I would tail it, and then reproduce the issue.. so do:
    # tail -f /usr/local/cpanel/logs/error_log
    hit enter a few times to seperate old logging, then log into phpmyadmin to reproduce the error and paste anything new that displays in ssh
    0
  • morteza3245
    this is error log:
    root@host [~]# tail -f /usr/local/cpanel/logs/error_log eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 92 Try::Tiny::try(CODE(0x73b4ca8), Try::Tiny::Catch=REF(0x72102c0)) called at /usr/local/cpanel/Cpanel/Pkgacct.pm line 149 Cpanel::Pkgacct::perform_component(Cpanel::Pkgacct=HASH(0x428d0c8), "Mysql") called at bin/pkgacct.pl line 984 Script::Pkgacct::script("Script::Pkgacct", "moviedl", "/backup/cpbackup/daily", "backup") called at bin/pkgacct.pl line 134 Script::Pkgacct::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 101 eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/Try/Tiny.pm line 92 Try::Tiny::try(CODE(0x3c6f0d8), Try::Tiny::Catch=REF(0x1a52450)) called at bin/pkgacct.pl line 144 [2017-02-20 07:59:34 +0430] info [cpbackup] Backup::Success Notification => report@ssssss.com***** via EMAIL [eventimportance => Low (3)] Building global cache for cpanel...Done [2017-02-20 12:15:12 +0430] info [autorepair] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:35 +0430] info [xml-api] Loading default httpupdate source [2017-02-20 14:36:35 +0430] info [xml-api] Syncing version information from httpupdate.cpanel.net/cpanelsync/TIERS.json [2017-02-20 14:36:35 +0430] info [xml-api] Syncing version information from httpupdate.cpanel.net/cpanelsync/TIERS.json [2017-02-20 14:36:43 +0430] info [xml-api] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:44 +0430] info [xml-api] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:44 +0430] info [xml-api] Using new TIERS.json version file ^C root@host [~]# tail -f /usr/local/cpanel/logs/error_log Try::Tiny::try(CODE(0x3c6f0d8), Try::Tiny::Catch=REF(0x1a52450)) called at bin/pkgacct.pl line 144 [2017-02-20 07:59:34 +0430] info [cpbackup] Backup::Success Notification => report@ssssss.com***** via EMAIL [eventimportance => Low (3)] Building global cache for cpanel...Done [2017-02-20 12:15:12 +0430] info [autorepair] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:35 +0430] info [xml-api] Loading default httpupdate source [2017-02-20 14:36:35 +0430] info [xml-api] Syncing version information from httpupdate.cpanel.net/cpanelsync/TIERS.json [2017-02-20 14:36:35 +0430] info [xml-api] Syncing version information from httpupdate.cpanel.net/cpanelsync/TIERS.json [2017-02-20 14:36:43 +0430] info [xml-api] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:44 +0430] info [xml-api] Successfully verified signature for cpanel (key types: release). [2017-02-20 14:36:44 +0430] info [xml-api] Using new TIERS.json version file
    0
  • sktest123
    please check phpMyAdmin doesn't start - gives a session error its a old thread but definitely have a work around .
    0
  • Jcats
    He states that its only affecting some users so that thread will more than likely be of no help. However... It looks like phpmyadmin does use /home/user/tmp to sore the session so instead of checking the server root /tmp location, I would check the user accounts home directory. It doesn't require special permissions, just 755 but make sure it actually exists and the ownership is proper.
    # mkdir -p /home/user/tmp # chown user: /home/user/tmp
    Make sure to replace user with the cpanel username, then try and access phpmyadmin again.
    0
  • cPanelMichael
    Hello, It looks like the output from /usr/local/cpanel/logs/error_log relates to the backup process. Could you use a command such as "tail -f /usr/local/cpanel/logs/error_log", but only post the output that appears while attempting to access phpMyAdmin? Thank you.
    0

Please sign in to leave a comment.