ok, so it still sounds like maybe one machine has the BIOS clock set to local time and the other set to Universal. Both boxes still have local time available in Linux but one of them is correcting the system clock and the other does not need to. I only mentioned dual booting windows because that is the most common way the BIOS clock stays as local time. Anyway, I still suggest that COULD be the BASIS for your problem. It even be that the two kinds of reports use a different system call to get the time resulting in the apparent difference.
On 6/24/07, George Toft <george@georgetoft.com> wrote:
Good thought! However, both systems were built the same, and have the
same error messages depending on who is rsync'ing to whom.
More details:
These two servers are in a failover, high-availability cluster, and I
use rsync to keep the file systems in sync. rsync syncs from the active
node to the passive node. (I would have preferred GFS or SAN, but that
was outside of the budget.)
So - whether it's server1 sync'ing to server2, or the other way around,
the log entries look the same.
George Toft, CISSP, MSIS
623-203-1760
Dazed_75 wrote:
>
>
> On 6/24/07, *George Toft* <george@georgetoft.com
> <mailto:george@georgetoft.com>> wrote:
>
> I have an rsync cronjob that syncs up a couple of directories. It works
> fine. The problem is the logs are a combination of MST and UDT:
>
> Jun 24 09:22:01 server2 rsyncd[4670]: rsync to www/ from
> root@server1-rsync (10.0.3.1 <http://10.0.3.1>)
> Jun 24 16:22:01 server2 rsyncd[4670]: skipping non-regular file
> "html/ssl/php/index.php"
> Jun 24 16:22:01 server2 rsyncd[4670]: skipping non-regular file
> "virtual/example.com/html/ssl/php/index.php"
> Jun 24 16:22:01 server2 rsyncd[4670]: wrote 69 bytes read 206942 bytes
> total size 1556092271
> Jun 24 09:22:01 server2 rsyncd[4672]: rsync to share/ from
> root@tos1-rsync (10.0.3.1 <http://10.0.3.1
> )
> Jun 24 16:22:01 server2 rsyncd[4672]: wrote 69 bytes read 123 bytes
> total size 0
>
> I would like to unify the timestamps to MST. Anyone know how to do that
> (didn't see anything in the man page)?
>
>
> Hopefully this is not a stupid response. I notice that the messages
> showing a different clock both state explicitly being from root@xxxxxxxx
> (10.0.3.1
<http://10.0.3.1>) although the other messages do not. Is it
> possible that one of the machines being rsync'd has its system clock set
> to UDT and the other does not (such as a machine that also dual boots
> Windows)?
>
> Side note - anyone know how to sync a symlink? Yes, I know it can be
> bad on systems that do not have the same file structure, but these are
> virtually identical boxes, and I want to be stupid.
> --
> George Toft, CISSP, MSIS
> 623-203-1760
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
> <mailto:PLUG-discuss@lists.plug.phoenix.az.us>
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> <
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss>
>
>
>
>
> --
> Be who you are and say what you feel, because those who mind don't
> matter and those who matter don't mind. - Dr. Seuss
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------
> PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
--
Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seuss