Unicast Addressing
Unicast delivery requires that a message should be addressed to a specific recipient. This is the most common type of messaging, so this addressing capability is present in almost all protocols.
Broadcast Addressing
Broadcasts are normally implemented via a special address that is reserved for that function. Whenever devices see a message sent to that address, they all interpret it as “This message goes to everyone.”
Multicast Addressing
Multicasts are the most complex type of message because they require a means of identifying a set of specific devices that will receive a message. It is often necessary to create several such groups, which may or may not partially overlap in their membership. Some mechanism is needed to manage which devices are in which groups.
Anycast message
A new type of message-addressing method was defined as part of IP version 6 (IPv6): the anycast message. This term identifies a message that should be sent to the closest member of a group of devices.
When customer tries to see statistics from watchdog, an error message appears
Internal error: failed to adjust system time in accordance with daylight savings time change.
Also Watchdog’s cron job reports the error
ERROR: WDExc
Error occurred while processing database query: ‘MySQL query failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘group by service_id, type, round(unix_timestamp(time) / 7200, 0) having count(va’ at line 3′
To resolve this issue.
Unzip Parallels Plesk Panel version pack-sysstats and replace the file located in /usr/local/psa/libexec/modules/watchdog/cp/
http://kb.parallels.com/Attachments/14807/Attachments/pack-sysstats-for-9.5-10.zip
Unzip Parallels Plesk Panel version stats-graph and replace the file located in /usr/local/psa/admin/htdocs/modules/watchdog/
http://kb.parallels.com/Attachments/14807/Attachments/stats-graph-for-9.zip
Reference: http://parallels.com/
Upcp Error Message for changing host IP to 0.0.0.0
Error Message
The hostname (domain.server.com) resolves to xxx.xxx.xxx.xxx. It should resolve to 0.0.0.0 Please be sure to correct /etc/hosts as well as the ‘A’entry in zone file for the domain. Some are all of these problems can be caused by /etc/resolv.conf being setup incorrectly. Please check this file if you believe everything else is correct.
Issue is due to wrong ethernet interface specified in “WHM >> Basic cPanel/WHM Setup”.
In order to resolve this check the ethernet configuration file for the value “IPADDR” and add this interface in “WHM >> Basic cPanel/WHM Setup”
Now for crosschecking take the option “Add an A Entry for your Hostname” in WHM.
Finally start “ipaliases” (/etc/rc.d/init.d/ipaliases) service for the new interface.
Exim started generating error message in /var/log/exim_mainlog after update.
ACL: ratelimit database not available
The cause for this issue is exim cache database might be corrupted. To fix this error the exim cache database on the server needs to be remove(Exim rebuilds this database again after exim restart)
To fix this run the following command as root to remove the cache database.
rm -fv /var/spool/exim/db/*
Then restart the exim :
Exim Message Reception and Delivery log files
Exim writes three different logs, referred to as the main log, the reject log, and the panic log.
/var/log/exim_mainlog ( Linux )
/var/log/exim/mainlog (FreeBSD)
The main log records the arrival of each message and each delivery in a single line in each case. The format is as compact as possible, in an attempt to keep down the size of log files. Two-character flag sequences make it easy to pick out these lines. A number of other events are recorded in the main log. Some of them are optional, in which case the log_selector option controls whether they are included or not. A Perl script called eximstats, which does simple analysis of main log files, is provided in the Exim distribution.
The above log files receives an entry every time a message is received or delivered.
Rejections based on ACLs/Policies: Receives an entry every time a message is rejected based on either ACLs or other policies (for example, aliases configured to :fail:)
/var/log/exim_rejectlog ( Linux )
/var/log/exim/rejectlog (FreeBSD)
The reject log records information from messages that are rejected as a result of a configuration option (that is, for policy reasons).
