This article provides examples of basic logs.
SSH
The SSH log stores information about SSH connections to the VPS and the IP addresses from which the connections were made. Commands entered after connection are not saved in this log.
Log structure:
- date
- time
- server name
- information line
Example 1:
Dec 3 15:17:25 server1 sshd[10656]: error: PAM: Authentication failure for user_name from 88.225.37.34
# Unsuccessful attempt to authorize from the address 88.225.37.34
Example 2:
Dec 30 18:30:50 server1 sshd[27485]: Accepted publickey for user_name from 85.53.115.34 port 51430 ssh2
# Successful authorization using the RSA key from the address 85.53.115.34
FTP
The FTP log contains information about connections to the VPS via FTP and actions with files (via FTP).
Log structure:
- date
- time
- server
- process
- user
- action status
- action
- IP
- additional Information
Example 1:
Dec 30 10:13:39 server1 vsftpd[32618]: [onetwo3] OK LOGIN: Client "::ffff:92.53.115.34"
# Successful connection attempt
Example 2:
Dec 30 10:13:26 server1 vsftpd[2538]: [onetwo3] OK DELETE: Client "::ffff:92.53.115.34", "/php.test.ini"
# File php.test.ini deleted
access_log
Contains records of requests to the Apache web server (requests to static files are handled by Nginx).
Log structure:
- date
- time
- server
- log
- domain
- IP address of the request
- user (for http authorization)
- group (for http authorization)
- date and time
- type of request
- server response code
- response size in bytes
- referrer user-agent
Example:
Dec 30 13:39:28 server1 apache_access: domain.com 82.53.116.19 - - [30/Dec/2020:13:39:28 +0400] "GET / HTTP/1.0" 200 1187 "-" "Mozilla/5.0 (X11; Linux x86_64)"
# GET request to the root of domain.com on server1 via HTTP/1.0 protocol with response code 200 (response received correctly) from user-agent Mozilla / 5.0, response size in bytes - 1187.
Dec 30 13:39:28 server1 apache_access: domain.com 82.53.116.19 - - [30/Dec/2020:13:39:28 +0400] "GET / HTTP/1.0" 200 1187 "-" "Mozilla/5.0 (X11; Linux x86_64)"
# GET request to the root of domain.com on server1 via HTTP/1.0 protocol with response code 200 (response received correctly) from user-agent Mozilla / 5.0, response size in bytes - 1187.
- error_log
Contains the Apache error log.
Log structure:
- date
- time
- server
- log
- error string
Example:
Dec 30 14:21:08 server1 apache_error: [Tue Dec 30 14:21:08 2020] [error] [client 85.53.115.234] File does not exist: /home/u/user/domain.com/public_html/file.ico
# Addressing from IP 85.53.115.234 to a nonexistent file file.ico
If you have any questions, please create a ticket to technical support.