Openbsd Error Logs
Contents |
Nginx PHP OpenLDAP MySQL, MariaDB Roundcube webmail Amavisd Main
Roundcube Log File
config files Log files SpamAssassin Fail2ban SOGo Groupware iredmail logs iRedAPD iRedAdmin Cluebringer SSL certificate The self-signed SSL certificate generated during iRedMail installation: dovecot log file on RHEL/CentOS: /etc/pki/tls/certs/iRedMail.crt Private key: /etc/pki/tls/private/iRedMail.key on Debian/Ubuntu: /etc/ssl/certs/iRedMail.crt Private key: /etc/ssl/private/iRedMail.key on FreeBSD: /etc/ssl/certs/iRedMail.crt Private key: /etc/ssl/private/iRedMail.key on OpenBSD: /etc/ssl/iRedMail.crt
Iredmail Configuration
Private key: /etc/ssl/iRedMail.key Postfix on Linux and OpenBSD, Postfix config files are placed under /etc/postfix/. on FreeBSD, Postfix config files are placed under /usr/local/etc/postfix/. Main config files: main.cf: contains most configurations. master.cf: contains transport related settings. aliases: aliases for system accounts. helo_access.pcre:
Roundcube Error Log Cpanel
PCRE regular expressions of HELO check rules. ldap/*.cf: used to query mail accounts. LDAP backends only. mysql/*.cf: used to query mail accounts. MySQL/MariaDB backends only. pgsql/*.cf: used to query mail accounts. PostgreSQL backend only. Log files on RHEL/CentOS, FreeBSD, OpenBSD, it's /var/log/maillog. on Debian, Ubuntu, it's /var/log/mail.log. Dovecot on Linux and OpenBSD, Dovecot config files are placed under /etc/dovecot/. on FreeBSD, Dovecot config files are placed under /usr/local/etc/dovecot/. Config files Main config file is dovecot.conf. It contains most configurations. Additional config files under /etc/dovecot/: dovecot-ldap.conf: used to query mail users and passwords. LDAP backends only. dovecot-mysql.conf: used to query mail users and passwords. MySQL/MariaDB backends only. dovecot-pgsql.conf: used to query mail users and passwords. PostgreSQL backend only. dovecot-used-quota.conf: used to store and query real-tim
- Kernel Developer's Manual All Architectures amd64 alpha iredmail disable greylisting armv7 hppa i386 landisk loongson luna88k macppc mips64 octeon sgi
Iredmail Admin Url
socppc sparc64 amiga arc armish arm32 atari aviion beagle cats hppa64 hp300 ia64 mac68k mvme68k iredmail centos 7 mvme88k mvmeppc palm pc532 pegasos pmax powerpc solbourne sparc sun3 vax wgrisc x68k zaurus OpenBSD-current OpenBSD-6.0 OpenBSD-5.9 POSIX-2013 4.4BSD-Lite2 UNIX-7 FreeBSD-10.3 DragonFly-4.6.0 NetBSD-7.0.1 Linux-4.05 OpenBSD-5.8 OpenBSD-5.7 http://www.iredmail.org/docs/file.locations.html OpenBSD-5.6 OpenBSD-5.5 OpenBSD-5.4 OpenBSD-5.3 OpenBSD-5.2 OpenBSD-5.1 OpenBSD-5.0 OpenBSD-4.9 OpenBSD-4.8 OpenBSD-4.7 OpenBSD-4.6 OpenBSD-4.5 OpenBSD-4.4 OpenBSD-4.3 OpenBSD-4.2 OpenBSD-4.1 OpenBSD-4.0 OpenBSD-3.9 OpenBSD-3.8 OpenBSD-3.7 OpenBSD-3.6 OpenBSD-3.5 OpenBSD-3.4 OpenBSD-3.3 OpenBSD-3.2 OpenBSD-3.1 OpenBSD-3.0 OpenBSD-2.9 OpenBSD-2.8 OpenBSD-2.7 OpenBSD-2.6 OpenBSD-2.5 OpenBSD-2.4 OpenBSD-2.3 OpenBSD-2.2 FreeBSD-10.2 FreeBSD-10.0 DragonFly-4.4.2 DragonFly-3.8.2 NetBSD-7.0 NetBSD-6.1.5 HTTPD.CONF(5) File Formats Manual HTTPD.CONF(5) NAME httpd.conf -- HTTP daemon configuration http://man.openbsd.org/httpd.conf.5 file DESCRIPTION httpd.conf is the configuration file for the HTTP daemon, httpd(8). SECTIONS httpd.conf is divided into four main sections: Macros User-defined variables may be defined and used later, simplifying the configuration file. Global Configuration Global settings for httpd(8). Servers Listening HTTP web servers. Types Media types and extensions. Within the sections, a host address can be specified by IPv4 address, IPv6 address, interface name, interface group, or DNS hostname. If the address is an interface name, httpd(8) will look up the first IPv4 address and any other IPv4 and IPv6 addresses of the specified network interface. If ‘*' is given as an address, it will be used as an alias for 0.0.0.0 to listen on all IPv4 addresses. Likewise, ‘::' can be used to listen on all IPv6 addresses. A port can be specified by number or name. The port name to number mappings are found in the file /etc/services; see serv
Guides Programming Security Software User Groups This is the BSDA Study Guide Book written http://www.bsdnewsletter.com/bsda-book/Configure_system_logging.html via a wiki collaboration. This is a work in progress. http://www.cyberciti.biz/faq/error_log-defines-file-where-script-errors-logged/ You may contribute to or discuss this specific page at http://bsdwiki.reedmedia.net/wiki/Configure_system_logging.html. Configure system logging Concept Understand that the system automatically handles logging and has many different logs. Recognize the syslog configuration and be able to add or change a logging entry. Be able log file to configure the syslog server to not listen to network. Understand logging facilities and priorities. Introduction Many programs use a standard interface called syslog for recording system activity details, debugging messages, server accesses, and other transactions. These logs are useful for verifying system behavior, checking software status, and diagnosing problems. Analyzing and viewing openbsd error logs log files is discussed in section Review log files to troubleshoot and monitor system behavior. The actual logging is handled by the syslogd daemon (also known as the syslogger or the system message logger) which is started by default. Applications that use the syslog(3) library interface communicate with the syslogger. In addition to appending messages to log files, this daemon can also send messages to the console, pipe the message through another program, write the message to logged in users, or forward to other network logging servers. TODO: show a couple log message examples Configuration The syslogd configuration file is located at /etc/syslog.conf. Comments can be placed on lines that start with a hash mark (#). Tabs are used as field separators. TODO: do all BSDs allow spaces also? (Some versions of syslogd also allow spaces as field separators.) At the simplest, the format is the selector and the action: facility.level /var/log/logfilename The facilities are: auth, auth
Friends,Security,Suse,TroubleshootingI‘m running CentOS 5.x server with Apache 2.2 + PHP 5.x server. Can you tell me exact location for php error log file?Generally, on all production web servers displaying error to end users via a web browser is turned off using php.ini file settings. Open /etc/php.ini file and find out line that read as follows:
error_logOR use the grep command as follows:grep error_log /etc/php.ini grep ^error_log /etc/php.iniSample outputs:error_log = /var/log/httpd/php_error_logThe error_log directive defines the name of the file where script errors should be logged. The file should be writable by the web server's user. If the special value syslog is used, the errors are sent to the system logger instead. On Unix, this means syslogd and on Windows NT it means the event log. The system logger is not supported on Windows 95. If this directive is not set, errors are sent to the SAPI error logger. For example, it is an error log in Apache (/var/log/httpd/error_log file) or stderr in command line (CLI).This line define exact location for each php instance. If error_log set to syslog, open /var/log/messages file to view log. For example if error_log is set to /var/log/apache/php.errors, type the following to display error log:$ tail -f /var/log/apache/php.errors$ grep something /var/log/apache/php.errors
$ vi /var/log/apache/php.errorsSee also:PHP Log All Errors to a Log File to Get Detailed Information php.ini directivesShare this tutorial on:TwitterFacebookGoogle+Download PDF version Found an error/typo on this page?About the author: Vivek Gite is a seasoned sysadmin and a trainer for the Linux/Unix & shell scripting. Follow him on Twitter. OR read more like this:Apache Log FilesHow do I find out syntax errors in my Apache web server configuration file?Apache 2: Reload HTTPD Conf