RE: {bb} LARRD stopped

["McClinton, Rick" <rmcclinton@tmaresources.com>]

1173599988 is a unix epoch time. http://en.wikipedia.org/wiki/Unix_time
http://www.onlineconversion.com/unix_time.htm converts that value to 
Sun, 11 Mar 2007 08:02:23 UTC.

Ergo, someone set the date ahead on the system to check DST issues,
RRD's were updated with that timestamp, and the safety mechanism has
prevented the RRD's from being updated with 'older' timestamps.

Usually, the safety mechanism prevents the file from being updated too
quickly, as can happen when there are multiple processes trying to
update it instead of a single process.

It should be possible to repair the RRD but that is a little above my
head. My system history isn't so critical, I would just delete the
RRD's...

Have a nice day,
Rick



> -----Original Message-----
> From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Peter J
> Zeiszler
> Sent: Friday, February 23, 2007 3:34 PM
> To: bb@bb4.com
> Subject: RE: {bb} LARRD stopped
> Importance: Low
> 
> I made those changes and this definitely gives more information.
> /usr/local/larrd/la-larrd.pl: DEBUG host: cheeta.sps.mot.com - users:
98,
> procs: 354, la: 300
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/cheeta.sps.mot.com.la.rrd: illegal attempt
to
> update using tim
> e 1172261970 when last update time is 1173599988 (minimum one second
step)
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/cheeta.sps.mot.com.users.rrd: illegal
attempt to
> update using
> time 1172261970 when last update time is 1173599988 (minimum one
second
> step)
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/cheeta.sps.mot.com.procs.rrd: illegal
attempt to
> update using
> time 1172261970 when last update time is 1173599988 (minimum one
second
> step)
> 
> That host line really helps narrow things down.
> The Warn though is probably exactly the problem.  Where is this time
> information gathered and what exactly is that format?  Does this mean
> somehow the rrd has time stamps created in the future?
> 
> Here is other information from the LARRDOUT that shows a different
update
> time - looks like its based on the system.  When I look at the larrd
> graphs
> for these systems they are the ones not updating the graphs.
> 
> /usr/local/larrd/la-larrd.pl: DEBUG host: yukon.sps.mot.com - users:
3,
> procs: 82, la: 1.69
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/yukon.sps.mot.com.la.rrd: illegal attempt to
> update using tim
>  1172262226 when last update time is 1173600143 (minimum one second
step)
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/yukon.sps.mot.com.users.rrd: illegal attempt
to
> update using
> ime 1172262226 when last update time is 1173600143 (minimum one second
> step)
> /usr/local/larrd/la-larrd.pl: WARN updating
> /opt/bigbrother/bbvar/rrd/yukon.sps.mot.com.procs.rrd: illegal attempt
to
> update using
> ime 1172262226 when last update time is 1173600143 (minimum one second
> step)
> 
> Peter Zeiszler
> VMS System Manager
> CSC
> (480)603-8128 Cell
> Pzeiszler@csc.com Email
> 4806038128@tmomail.net Cell Email
> 
> 
> 
> 
> 
> POPI Classification:
> |----------------------------------------|
> | [ ] General Business Use               |
> | [ ] Freescale Internal Use Only        |
> | [X] Freescale Confidential Proprietary |
> |----------------------------------------|
> 
> 
> 
> 
> 
>
------------------------------------------------------------------------
--
>
------------------------------------------------------------------------
--
> ----------------------------
> 
>  This is a PRIVATE message. If you are not the intended recipient,
please
>   delete without copying and kindly advise us by e-mail of the mistake
in
>   delivery. NOTE: Regardless of content, this e-mail shall not operate
to
> bind CSC to any order or other contract unless pursuant to explicit
> written
>  agreement or government initiative expressly permitting the use of
e-mail
>                              for such purpose.
>
------------------------------------------------------------------------
--
>
------------------------------------------------------------------------
--
> ----------------------------
> 
> 
> 
> 
> 
>              "McClinton, Rick"
>              <rmcclinton@tmare
>              sources.com>
To
>              Sent by:                  "bb@bb4.com" <bb@bb4.com>
>              owner-bb@bb4.com
cc
> 
>
Subject
>              02/23/2007 12:47          RE: {bb} LARRD stopped
>              PM
> 
> 
>              Please respond to
>                 bb@bb4.com
> 
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Peter
J
> > Zeiszler
> > Sent: Friday, February 23, 2007 1:57 PM
> > To: bb@bb4.com
> > Subject: RE: {bb} LARRD stopped
> > Importance: Low
> >
> > There is no bb-bbexttab file in the etc folders.  On my other
working
> bb
> > server it also does not contain that file.
> >
> > From the DEBUG being set the LARRDOUT now has new lines -
> > *.memory: No such file or directory
> > /usr/local/larrd/la-larrd.pl: DEBUG users: 2, procs: 207, la: 1.56
> [et al.]
> 
> OK so la-larrd.pl definitely ran. It was not very helpful of it not to
> log which file it was looking at. Does the number of lines there match
> the number of *.cpu Big Brother logs?
> 
> It also is interesting that DEBUG, WARN, and STATUS are not related
> variables; for full output from the script you could set $ENV{'WARN'}
> and $ENV{'STATUS'} to 1. You may also want to modify
>         print "$0: DEBUG users: $users, procs: $procs, la: $la\n" if
> $ENV{'DEBUG'};
> 
> to         print "$0: DEBUG host: $host users: $users, procs: $procs,
> la: $la\n" if $ENV{'DEBUG'};
> 
> for a little more help from the DEBUG statement.
> 
> Are you SURE the permissions on the RRD's are proper? Maybe the RRD
> files are botched; setting $ENV{'WARN'} = 1 will enable the message
> printed if the RRD update process has an error.
> 
> This message contains TMA Resources confidential information and is
> intended only for the individual named. If you are not the named
addressee
> you should not disseminate, distribute or copy this e-mail. Please
notify
> the sender immediately by e-mail if you have received this e-mail by
> mistake and delete this e-mail from your system. E-mail transmission
> cannot
> be guaranteed to be secure or error-free as information could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses. The sender therefore does not accept liability for
any
> errors or omissions in the contents of this message which arise as a
> result
> of e-mail transmission. If verification is required please request a
> hard-copy version.
> 
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.
> 
> 
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.

This message contains TMA Resources confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. 

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.