cPanel and Plesk log path

Some log path information in cPanel/WHM server and Plesk server:


cPanel, WHM & Webmail

    Login Attempts to cpsrvd /usr/local/cpanel/logs/login_log
    Account Transfers & Misc. Logs /var/cpanel/logs
    Per-Account Bandwidth History Human Readable /var/cpanel/bandwidth/(USERNAME)
    Per-Account Bandwidth History – Cached /var/cpanel/bandwidth.cache/(USERNAME)
    Service Status Logs /var/log/chkservd.log
    Error Log for cpsrvd /usr/local/cpanel/logs/error_log
    Panic Log for cpsrvd /usr/local/cpanel/logs/panic_log
    Backup Logs /usr/local/cpanel/logs/cpbackup
    Update (UPCP) Log /var/cpanel/updatelogs/update-(TIMESTAMP).log
    Mailman Logs /usr/local/cpanel/3rdparty/mailman/logs
    Auditing Log (Account Creations, Deletions, etc.) /var/cpanel/accounting.log
    Access Log & User Actions in cpsrvd /usr/local/cpanel/logs/access_log
    Website Statistics Logs /usr/local/cpanel/logs/stats_log
    Logs for Specific Webmail Applications
        SquirrelMail /var/cpanel/squirrelmail
        RoundCube /var/cpanel/roundcube/log
        Horde /var/cpanel/horde/log
    License Updates & Errors /usr/local/cpanel/logs/license_log
    Brute Force Protection (cPHulkD) Log /usr/local/cpanel/logs/cphulkd.log
    WebDisk (cpdavd) Log /usr/local/cpanel/logs/cpdavd_error_log
    Tailwatch Driver (tailwatchd) Log /usr/local/cpanel/logs/tailwatch_log
    EasyApache Build Logs /usr/local/cpanel/logs/easy/apache/
    Installation Log /var/log/cpanel*install*

MySQL

    General Information & Errors /var/lib/mysql/(HOSTNAME).err or
    /val/log/mysqld.log

FTP (Pure-FTPD, Pro-FTPD)

    Login Attempts & General Info /var/log/messages
    FTP Transfer Log /var/log/xferlog is a symbolic link to /usr/local/apache/domlogs/

Mail Retrieval & Spam Protection (Courier, Dovecot, SpamAssassin)

    IMAP, POP Login Attempts, Transactions, Fatal Errors & Spam Scoring /var/log/maillog and /var/log/messages

Mail Delivery (Exim)

    Unexpected/Fatal Error Log /var/log/exim_paniclog (Linux)
    /var/log/exim/paniclog (FreeBSD)
    Incoming Mail Queue /var/spool/exim/input
    Log of Messages Rejected Based on ACLs or Other Policies /var/log/exim_rejectlog (Linux) /var/log/exim/rejectlog (FreeBSD)
    Delivery & Receipt Log /var/log/exim_mainlog (Linux) /var/log/exim/mainlog (FreeBSD)

Named (BIND)

    Log /var/log/messages

NSD

    Log /var/log/messages

SSHD

    SSH Log /var/log/messages

Web Server (Apache/httpd)

    Domain Access Logs /usr/local/apache/domlogs/(DOMAIN)
    Web Server & CGI Application Error Log /usr/local/apache/logs/error_log
    SuExec Audit Log /usr/local/apache/logs/suexec_log
    SuPHP Audit Log /usr/local/apache/logs/suphp_log

Top Memory & CPU Consumers (dcpumon)

    Top Processes Consuming CPU & Memory /var/log/dcpumon/(YEAR)/(MONTH)/(DAY)

Plesk Logs:

Plesk (sw-cp-serverd)

    Access Log /usr/local/psa/admin/logs/httpsd_access_log
    Backups Log /var/lib/dumps/domain.tld/backup_restore.log and
    /var/lib/dumps/domain.tld/backup_restore.err_log
    Error Log /var/log/sw-cp-server/error_log
    Watchdog
    Migration Log /usr/local/psa/PMM/logs/migration.log
    Mailman Log /var/log/mailman/error
    Horde Webmail /var/local/psa-horde/psa-horde.log

FTP (Pro-FTPD)

    Login Attempts & General Info /var/log/messages
    FTP Transaction Log /usr/local/psa/var/log/xferlog

Mail Retrieval & Spam Protection

    IMAP, POP Login Attempts, Transactions, Fatal Errors & Spam Scoring /usr/local/psa/var/log/maillog/var/log/messages

Mail Delivery (Qmail)

    Transactions, Errors /usr/local/psa/var/log/maillog
    Queued Mail /usr/local/pas/var/log/smtp_pendings.log

SSHD

    SSH Log /var/log/messages

Named (BIND)

    Log /var/log/messages

Web Server (Apache / httpd)

    Access & Error Logs /var/log/httpd/access_log and /var/log/httpd/error_log
    Domain Access & Error Logs /var/www/vhosts/domain.tld/statistics/logs/access.log and /var/www/vhosts/domain.tld/statistics/logs/error_log

MySQL

    General Information & Errors /var/log/mysqld.log

The Tech Bench is an ongoing blog series featuring the answers to common questions the ServInt MST fields everyday. You can also find more great tech tips in the ServInt KnowledgeBase.

Comments

Post a Comment

Popular posts from this blog

Resolved: DOCKER: Error response from daemon: Could not attach to network / rpc error: code = 7 desc = network not manually attachable.

Image
I got this error: 'docker: Error response from daemon: Could not attach to network <nw-name>: rpc error: code = 7 desc = network <nw-name> not manually attachable.' when i try to create the container on the overlay network on swarm mode enabled, In docker 1.12 with swarm mode enabled, "Swarm" scoped networks (see the "SCOPE" column) cannot be used for docker run, only for services and now it has been rectified. I'm using updated version of docker, but still why i'm experiencing the error ? because the network just created but not manually attachable. To fix the issue we gonna use --attachable flag while creating network. [ --attachable             Enable manual container attachment ] (Need to create service on the overlay network, so that the overlay network will available / list on the worker node) docker inspect attnw (attnw is our test network)should show your own c
Read more

yum failed 6 times. Cannot continue!

Error while cPanel installation: (ERROR): - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored) (DEBUG): - ssystem [END] (FATAL): yum failed 6 times. Cannot continue! fix: It looks like you have some name resolution issues on the server. Just run the following commands on your server and it will resolve the name resolution issues. #echo "nameserver 8.8.8.8" >> /etc/resolv.conf #echo "nameserver 8.8.4.4" >> /etc/resolv.conf if it is not working properly still facing same error, then here we go, # rpm -e --nodeps bind-chroot # rpm -e --nodeps bind # yum install bind
Read more

unexpectedly shrunk window (repaired) in dmesg log - TCP Peer

Don't Panic, This normally occurs when a client decides to reduce its TCP window size, without the server expecting it. This can be the case when fragmentation is an issue, or when the client is using an embedded device with very little NIC buffer memory. This is a completely normal behaviour, and you’re likely to see quite a few such packets in your log. The messages are informational only, and are used to debug networking issues. I’d be worried if you saw hundreds of thousands of these packets, since there are attacks that involve packet fragmentation and small window sizes, but otherwise it’s just the normal sort of noise you should expect to see on any internet-facing network. In fact, the “repaired” part of your message is showing that your network driver fixed the issue, which is usually done by concatenating the payloads of two fragmented packets together. Shouldn’t be an issue at all. … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … 
Read more