Send observium mailing list submissions to
observium@observium.org
To subscribe or unsubscribe via the World Wide Web, visit
http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
or, via email, send a message with subject or body 'help' to
observium-request@observium.org
You can reach the person managing the list at
observium-owner@observium.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of observium digest..."
Today's Topics:
1. Re: question regarding traffic accounting (Adam Armstrong)
2. Re: question regarding traffic accounting (Michael)
3. Re: question regarding traffic accounting (Adam Armstrong)
4. Re: question regarding traffic accounting (Ross [Eve IT])
5. Re: question regarding traffic accounting (Adam Armstrong)
6. Re: question regarding traffic accounting (Adam Armstrong)
7. Re: Windows Processor Numbers are Odd (Max Krabbenhöft)
8. SVN Update doesn't seem to update observium (Lorenzo Zafra)
9. Re: Windows Processor Numbers are Odd (Adam Armstrong)
10. Re: SVN Update doesn't seem to update observium (Adam Armstrong)
11. Re: question regarding traffic accounting (Ross [Eve IT])
12. Re: question regarding traffic accounting (Ross [Eve IT])
13. Help with monitor Tomcat Traffic without Apache (Michael)
------------------------------------------------------------ ----------
Message: 1
Date: Wed, 08 Mar 2017 12:06:39 +0000
From: Adam Armstrong <adama@memetic.org>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID: <9574d4e3-a350-4a31-9469-9d255671a64e@typeapp.com >
Content-Type: text/plain; charset="utf-8"
It has to be large to keep the c*nt per square mile density the same as in normal countries...
...
:D
Sent from BlueMail
On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net> wrote:
>Thanks for the response,
>It is virtual, we did actually vmotion a few hosts to this server
>including
>the Observium machine.
>
>But I've checked the hypervisor, and its clock is good.
>Also uses NTP, same as the other Hypervisors.
>
>Although good point, I've actually been thinking about that exact same
>thing for logging purposes. UTC across the board as we also span a few
>timezones, Australia is large!
>
>
>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com> wrote:
>
>> It's very odd as there's no timezone of UTC+21.
>>
>> Your Observium instance isn't virtual is it? We've encountered
>problems
>> with guests set to obtain their time from the local clock and (on
>ESXi
>> hypervisors) have a massive time jump when vmotioned to a new host as
>they
>> grab their time from that clock. Any inconsistencies between the
>> hypervisors will throw your guests clock big time. All of a sudden,
>your
>> guest has jumped +10 hours (and ntpd will often wet its pants and
>refuse to
>> correct such a huge offset)...
>>
>> We had a similar problem to above when one hypervisor was set to our
>local
>> time (+10/11, same as you) when it was supposed to be set to UTC. In
>our
>> case, we run all of our clocks deliberately in UTC to preserve
>logging
>> integrity etc (you never get duplicated log times during the daylight
>> savings shift).
>>
>> Might not be your issue, but it may help somebody else (and worth
>keeping
>> in mind)!
>>
>> Michael
>>
>>
>>
>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net> wrote:
>> >
>> > Looks correct
>> >
>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>> > +--------------------------------+
>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>> > +--------------------------------+
>> > | 11:00:00 |
>> > +--------------------------------+
>> > 1 row in set (0.00 sec)
>> >
>> > mysql>
>> >
>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>> > +--------------------+---------------------+
>> > | @@global.time_zone | @@session.time_zone |
>> > +--------------------+---------------------+
>> > | SYSTEM | SYSTEM |
>> > +--------------------+---------------------+
>> > 1 row in set (0.00 sec)
>> >
>> > mysql>
>> >
>> > # date
>> > Wednesday 8 March 20:55:17 AEDT 2017
>> >
>> >
>> >
>> >
>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de>
>wrote:
>> > MySQL Time ?
>> >
>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net>:
>> >
>> >> Tried all that, still no go.
>> >>
>> >> I've set PHP to the right timezone.
>> >> NTP is set and running on all our servers.
>> >>
>> >> Any other ideas ?
>> >>
>> >>
>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>> sophanith.chhom@gmail.com> wrote:
>> >> Try to use single quote? eg:
>> >>
>> >> date.timezone = 'Australia/Melbourne'
>> >>
>> >> Then restart httpd service
>> >>
>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net>
>wrote:
>> >> Hi Sam,
>> >> thanks for responding.
>> >> however I already have that set correctly.
>> >>
>> >> [Date]
>> >> ; Defines the default timezone used by the date functions
>> >> ; http://php.net/date.timezone
>> >> date.timezone = Australia/Melbourne
>> >>
>> >> any other ideas ?
>> >>
>> >>
>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>> Sam.Hernandez-gill@qvc.com> wrote:
>> >>
>> >> I think that’s usually the php.ini timezone setting when the
>filtered
>> time doesn’t match, check out what you have set there, and match your
>> system’s timezone and restart apache
>> >>
>> >>
>> >>
>> >> From: observium [mailto:observium-bounces@observium.org ] On Behalf
>Of
>> Ross [Eve IT]
>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>> >> To: observium@observium.org
>> >> Subject: [Observium] question regarding traffic accounting
>> >>
>> >>
>> >>
>> >> Hello all,
>> >>
>> >>
>> >>
>> >> I'm using traffic accounting for multiple interfaces and have
>noticed a
>> strange occurrence.
>> >>
>> >> The graphs seem to be be producing the wrong time in the graphs.
>> >>
>> >>
>> >>
>> >> See attached;
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> If you notice the top right corner, 2017/03/08 03:15:04
>> >>
>> >> It's Tues 7th here 5:15pm.
>> >>
>> >>
>> >>
>> >> The server clock is synced NTP.
>> >>
>> >>
>> >>
>> >> Is there something I've missed here ?
>> >>
>> >>
>> >>
>> >> Observium 17.3.8420 (rolling)
>> >>
>> >> Debian Wheezy.
>> >>
>> >>
>> >>
>> >> Ross.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ----------------------------
>> >> This message (including any attachments) contains confidential
>> information intended for a specific individual and purpose, and is
>> protected by law. If you are not the intended recipient of this
>> (even if the e-mail address above is yours), (i) you may not use,
>copy or
>> retransmit it, (ii) please delete this message and (iii) please
>notify the
>> sender immediately. Any disclosure, copying, or distribution of this
>> message or the taking of any action based on it, is strictly
>prohibited.
>> >> ----------------------------
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> observium mailing list
>> >> observium@observium.org
>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> observium mailing list
>> >> observium@observium.org
>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> observium mailing list
>> >> observium@observium.org
>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>
>> >>
>> >> _______________________________________________
>> >> observium mailing list
>> >> observium@observium.org
>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >
>> > _______________________________________________
>> > observium mailing list
>> > observium@observium.org
>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >
>> >
>> > _______________________________________________
>> > observium mailing list
>> > observium@observium.org
>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>
>> _______________________________________________
>> observium mailing list
>> observium@observium.org
>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>
>
>
>----------------------------------------------------------- -------------
>
>_______________________________________________
>observium mailing list
>observium@observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/373c0059/ attachment-0001.html
------------------------------
Message: 2
Date: Thu, 09 Mar 2017 06:00:49 +1100
From: Michael <obslist@smarsz.com>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID: <322AB003-F30C-4BE8-933E-FC07D416F37A@smarsz.com >
Content-Type: text/plain; charset=utf-8
Maybe you're confused. In Australia, we call c*nts mate and our mates c*nt...
Here is a good vmware page on clock and ntpd settings for guests. https://kb.vmware.com/selfservice/microsites/search. do?language=en_US&cmd= displayKC&externalId=1006427
Michael
On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org> wrote:
>It has to be large to keep the c*nt per square mile density the same as
>in normal countries...
>
>...
>
>:D
>
>Sent from BlueMail
>
>On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net>
>wrote:
>>Thanks for the response,
>>It is virtual, we did actually vmotion a few hosts to this server
>>including
>>the Observium machine.
>>
>>But I've checked the hypervisor, and its clock is good.
>>Also uses NTP, same as the other Hypervisors.
>>
>>Although good point, I've actually been thinking about that exact same
>>thing for logging purposes. UTC across the board as we also span a few
>>timezones, Australia is large!
>>
>>
>>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com> wrote:
>>
>>> It's very odd as there's no timezone of UTC+21.
>>>
>>> Your Observium instance isn't virtual is it? We've encountered
>>problems
>>> with guests set to obtain their time from the local clock and (on
>>ESXi
>>> hypervisors) have a massive time jump when vmotioned to a new host
>as
>>they
>>> grab their time from that clock. Any inconsistencies between the
>>> hypervisors will throw your guests clock big time. All of a sudden,
>>your
>>> guest has jumped +10 hours (and ntpd will often wet its pants and
>>refuse to
>>> correct such a huge offset)...
>>>
>>> We had a similar problem to above when one hypervisor was set to our
>>local
>>> time (+10/11, same as you) when it was supposed to be set to UTC.
>In
>>our
>>> case, we run all of our clocks deliberately in UTC to preserve
>>logging
>>> integrity etc (you never get duplicated log times during the
>daylight
>>> savings shift).
>>>
>>> Might not be your issue, but it may help somebody else (and worth
>>keeping
>>> in mind)!
>>>
>>> Michael
>>>
>>>
>>>
>>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net> wrote:
>>> >
>>> > Looks correct
>>> >
>>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>>> > +--------------------------------+
>>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>>> > +--------------------------------+
>>> > | 11:00:00 |
>>> > +--------------------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>>> > +--------------------+---------------------+
>>> > | @@global.time_zone | @@session.time_zone |
>>> > +--------------------+---------------------+
>>> > | SYSTEM | SYSTEM |
>>> > +--------------------+---------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > # date
>>> > Wednesday 8 March 20:55:17 AEDT 2017
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de>
>>wrote:
>>> > MySQL Time ?
>>> >
>>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net>:
>>> >
>>> >> Tried all that, still no go.
>>> >>
>>> >> I've set PHP to the right timezone.
>>> >> NTP is set and running on all our servers.
>>> >>
>>> >> Any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>>> sophanith.chhom@gmail.com> wrote:
>>> >> Try to use single quote? eg:
>>> >>
>>> >> date.timezone = 'Australia/Melbourne'
>>> >>
>>> >> Then restart httpd service
>>> >>
>>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net>
>>wrote:
>>> >> Hi Sam,
>>> >> thanks for responding.
>>> >> however I already have that set correctly.
>>> >>
>>> >> [Date]
>>> >> ; Defines the default timezone used by the date functions
>>> >> ; http://php.net/date.timezone
>>> >> date.timezone = Australia/Melbourne
>>> >>
>>> >> any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>>> Sam.Hernandez-gill@qvc.com> wrote:
>>> >>
>>> >> I think that’s usually the php.ini timezone setting when the
>>filtered
>>> time doesn’t match, check out what you have set there, and match
>your
>>> system’s timezone and restart apache
>>> >>
>>> >>
>>> >>
>>> >> From: observium [mailto:observium-bounces@observium.org ] On
>Behalf
>>Of
>>> Ross [Eve IT]
>>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>>> >> To: observium@observium.org
>>> >> Subject: [Observium] question regarding traffic accounting
>>> >>
>>> >>
>>> >>
>>> >> Hello all,
>>> >>
>>> >>
>>> >>
>>> >> I'm using traffic accounting for multiple interfaces and have
>>noticed a
>>> strange occurrence.
>>> >>
>>> >> The graphs seem to be be producing the wrong time in the graphs.
>>> >>
>>> >>
>>> >>
>>> >> See attached;
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> If you notice the top right corner, 2017/03/08 03:15:04
>>> >>
>>> >> It's Tues 7th here 5:15pm.
>>> >>
>>> >>
>>> >>
>>> >> The server clock is synced NTP.
>>> >>
>>> >>
>>> >>
>>> >> Is there something I've missed here ?
>>> >>
>>> >>
>>> >>
>>> >> Observium 17.3.8420 (rolling)
>>> >>
>>> >> Debian Wheezy.
>>> >>
>>> >>
>>> >>
>>> >> Ross.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ----------------------------
>>> >> This message (including any attachments) contains confidential
>>> information intended for a specific individual and purpose, and is
>>> protected by law. If you are not the intended recipient of this
>>> (even if the e-mail address above is yours), (i) you may not use,
>>copy or
>>> retransmit it, (ii) please delete this message and (iii) please
>>notify the
>>> sender immediately. Any disclosure, copying, or distribution of this
>>> message or the taking of any action based on it, is strictly
>>prohibited.
>>> >> ----------------------------
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>>
>>> _______________________________________________
>>> observium mailing list
>>> observium@observium.org
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>>
>>
>>
>>---------------------------------------------------------- --------------
>>
>>_______________________________________________
>>observium mailing list
>>observium@observium.org
>>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
------------------------------
Message: 3
Date: Wed, 08 Mar 2017 19:03:08 +0000
From: "Adam Armstrong" <adama@memetic.org>
To: "" <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID: <a4dbe102-94ec-4912-81c3-0852b709ae5f@getmailbird.com >
Content-Type: text/plain; charset="utf-8"
That was the joke! :D
On 08/03/2017 19:01:22, Michael <obslist@smarsz.com> wrote:
Maybe you're confused. In Australia, we call c*nts mate and our mates c*nt...
Here is a good vmware page on clock and ntpd settings for guests. https://kb.vmware.com/selfservice/microsites/search. do?language=en_US&cmd= displayKC&externalId=1006427
Michael
On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong wrote:
>It has to be large to keep the c*nt per square mile density the same as
>in normal countries...
>
>...
>
>:D
>
>Sent from BlueMail
>
>On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]"
>wrote:
>>Thanks for the response,
>>It is virtual, we did actually vmotion a few hosts to this server
>>including
>>the Observium machine.
>>
>>But I've checked the hypervisor, and its clock is good.
>>Also uses NTP, same as the other Hypervisors.
>>
>>Although good point, I've actually been thinking about that exact same
>>thing for logging purposes. UTC across the board as we also span a few
>>timezones, Australia is large!
>>
>>
>>On Wed, Mar 8, 2017 at 9:29 PM, Michael wrote:
>>
>>> It's very odd as there's no timezone of UTC+21.
>>>
>>> Your Observium instance isn't virtual is it? We've encountered
>>problems
>>> with guests set to obtain their time from the local clock and (on
>>ESXi
>>> hypervisors) have a massive time jump when vmotioned to a new host
>as
>>they
>>> grab their time from that clock. Any inconsistencies between the
>>> hypervisors will throw your guests clock big time. All of a sudden,
>>your
>>> guest has jumped +10 hours (and ntpd will often wet its pants and
>>refuse to
>>> correct such a huge offset)...
>>>
>>> We had a similar problem to above when one hypervisor was set to our
>>local
>>> time (+10/11, same as you) when it was supposed to be set to UTC.
>In
>>our
>>> case, we run all of our clocks deliberately in UTC to preserve
>>logging
>>> integrity etc (you never get duplicated log times during the
>daylight
>>> savings shift).
>>>
>>> Might not be your issue, but it may help somebody else (and worth
>>keeping
>>> in mind)!
>>>
>>> Michael
>>>
>>>
>>>
>>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] wrote:
>>> >
>>> > Looks correct
>>> >
>>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>>> > +--------------------------------+
>>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>>> > +--------------------------------+
>>> > | 11:00:00 |
>>> > +--------------------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>>> > +--------------------+---------------------+
>>> > | @@global.time_zone | @@session.time_zone |
>>> > +--------------------+---------------------+
>>> > | SYSTEM | SYSTEM |
>>> > +--------------------+---------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > # date
>>> > Wednesday 8 March 20:55:17 AEDT 2017
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz
>>wrote:
>>> > MySQL Time ?
>>> >
>>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] :
>>> >
>>> >> Tried all that, still no go.
>>> >>
>>> >> I've set PHP to the right timezone.
>>> >> NTP is set and running on all our servers.
>>> >>
>>> >> Any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom
>>> sophanith.chhom@gmail.com> wrote:
>>> >> Try to use single quote? eg:
>>> >>
>>> >> date.timezone = 'Australia/Melbourne'
>>> >>
>>> >> Then restart httpd service
>>> >>
>>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT]
>>wrote:
>>> >> Hi Sam,
>>> >> thanks for responding.
>>> >> however I already have that set correctly.
>>> >>
>>> >> [Date]
>>> >> ; Defines the default timezone used by the date functions
>>> >> ; http://php.net/date.timezone
>>> >> date.timezone = Australia/Melbourne
>>> >>
>>> >> any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill
>>> Sam.Hernandez-gill@qvc.com> wrote:
>>> >>
>>> >> I think that’s usually the php.ini timezone setting when the
>>filtered
>>> time doesn’t match, check out what you have set there, and match
>your
>>> system’s timezone and restart apache
>>> >>
>>> >>
>>> >>
>>> >> From: observium [mailto:observium-bounces@observium.org ] On
>Behalf
>>Of
>>> Ross [Eve IT]
>>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>>> >> To: observium@observium.org
>>> >> Subject: [Observium] question regarding traffic accounting
>>> >>
>>> >>
>>> >>
>>> >> Hello all,
>>> >>
>>> >>
>>> >>
>>> >> I'm using traffic accounting for multiple interfaces and have
>>noticed a
>>> strange occurrence.
>>> >>
>>> >> The graphs seem to be be producing the wrong time in the graphs.
>>> >>
>>> >>
>>> >>
>>> >> See attached;
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> If you notice the top right corner, 2017/03/08 03:15:04
>>> >>
>>> >> It's Tues 7th here 5:15pm.
>>> >>
>>> >>
>>> >>
>>> >> The server clock is synced NTP.
>>> >>
>>> >>
>>> >>
>>> >> Is there something I've missed here ?
>>> >>
>>> >>
>>> >>
>>> >> Observium 17.3.8420 (rolling)
>>> >>
>>> >> Debian Wheezy.
>>> >>
>>> >>
>>> >>
>>> >> Ross.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ----------------------------
>>> >> This message (including any attachments) contains confidential
>>> information intended for a specific individual and purpose, and is
>>> protected by law. If you are not the intended recipient of this
>>> (even if the e-mail address above is yours), (i) you may not use,
>>copy or
>>> retransmit it, (ii) please delete this message and (iii) please
>>notify the
>>> sender immediately. Any disclosure, copying, or distribution of this
>>> message or the taking of any action based on it, is strictly
>>prohibited.
>>> >> ----------------------------
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>> >
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>>
>>> _______________________________________________
>>> observium mailing list
>>> observium@observium.org
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>>
>>
>>
>>---------------------------------------------------------- --------------
>>
>>_______________________________________________
>>observium mailing list
>>observium@observium.org
>>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/bf72965c/ attachment-0001.html
------------------------------
Message: 4
Date: Thu, 9 Mar 2017 08:26:13 +1100
From: "Ross [Eve IT]" <ross@eve-it.net>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID:
<CAODA=KF+HcBrNTjeOFBTh-L78Tu=0OA89uiG3C0gjn65mK9zKQ@mail. >gmail.com
Content-Type: text/plain; charset="utf-8"
Thanks Michael, good reference.
However I don't think that's my issue.
Is there any way I can debug the traffic accounting module to see where
this timestamp is being set perhaps ?
SUMMARY
observium bill accounting
Last calculated Thursday, 9 March 2017 @ 08:22:34
date on machine
root@eros:/usr/share/zoneinfo# date
Thursday 9 March 08:23:08 AEDT 2017
on observium graph, last plot is
09/03/17 21:20
The graph seems to be reporting approx 13 hours in the future.
On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com> wrote:
> Maybe you're confused. In Australia, we call c*nts mate and our mates
> c*nt...
>
> Here is a good vmware page on clock and ntpd settings for guests.
> https://kb.vmware.com/selfservice/microsites/search. do?language=en_US&cmd=
> displayKC&externalId=1006427
>
> Michael
>
>
>
> On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org>
> wrote:
> >It has to be large to keep the c*nt per square mile density the same as
> >in normal countries...
> >
> >...
> >
> >:D
> >
> >Sent from BlueMail
> >
> >On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net>
> >wrote:
> >>Thanks for the response,
> >>It is virtual, we did actually vmotion a few hosts to this server
> >>including
> >>the Observium machine.
> >>
> >>But I've checked the hypervisor, and its clock is good.
> >>Also uses NTP, same as the other Hypervisors.
> >>
> >>Although good point, I've actually been thinking about that exact same
> >>thing for logging purposes. UTC across the board as we also span a few
> >>timezones, Australia is large!
> >>
> >>
> >>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com> wrote:
> >>
> >>> It's very odd as there's no timezone of UTC+21.
> >>>
> >>> Your Observium instance isn't virtual is it? We've encountered
> >>problems
> >>> with guests set to obtain their time from the local clock and (on
> >>ESXi
> >>> hypervisors) have a massive time jump when vmotioned to a new host
> >as
> >>they
> >>> grab their time from that clock. Any inconsistencies between the
> >>> hypervisors will throw your guests clock big time. All of a sudden,
> >>your
> >>> guest has jumped +10 hours (and ntpd will often wet its pants and
> >>refuse to
> >>> correct such a huge offset)...
> >>>
> >>> We had a similar problem to above when one hypervisor was set to our
> >>local
> >>> time (+10/11, same as you) when it was supposed to be set to UTC.
> >In
> >>our
> >>> case, we run all of our clocks deliberately in UTC to preserve
> >>logging
> >>> integrity etc (you never get duplicated log times during the
> >daylight
> >>> savings shift).
> >>>
> >>> Might not be your issue, but it may help somebody else (and worth
> >>keeping
> >>> in mind)!
> >>>
> >>> Michael
> >>>
> >>>
> >>>
> >>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net> wrote:
> >>> >
> >>> > Looks correct
> >>> >
> >>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
> >>> > +--------------------------------+
> >>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
> >>> > +--------------------------------+
> >>> > | 11:00:00 |
> >>> > +--------------------------------+
> >>> > 1 row in set (0.00 sec)
> >>> >
> >>> > mysql>
> >>> >
> >>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
> >>> > +--------------------+---------------------+
> >>> > | @@global.time_zone | @@session.time_zone |
> >>> > +--------------------+---------------------+
> >>> > | SYSTEM | SYSTEM |
> >>> > +--------------------+---------------------+
> >>> > 1 row in set (0.00 sec)
> >>> >
> >>> > mysql>
> >>> >
> >>> > # date
> >>> > Wednesday 8 March 20:55:17 AEDT 2017
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de>
> >>wrote:
> >>> > MySQL Time ?
> >>> >
> >>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net>:
> >>> >
> >>> >> Tried all that, still no go.
> >>> >>
> >>> >> I've set PHP to the right timezone.
> >>> >> NTP is set and running on all our servers.
> >>> >>
> >>> >> Any other ideas ?
> >>> >>
> >>> >>
> >>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
> >>> sophanith.chhom@gmail.com> wrote:
> >>> >> Try to use single quote? eg:
> >>> >>
> >>> >> date.timezone = 'Australia/Melbourne'
> >>> >>
> >>> >> Then restart httpd service
> >>> >>
> >>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net>
> >>wrote:
> >>> >> Hi Sam,
> >>> >> thanks for responding.
> >>> >> however I already have that set correctly.
> >>> >>
> >>> >> [Date]
> >>> >> ; Defines the default timezone used by the date functions
> >>> >> ; http://php.net/date.timezone
> >>> >> date.timezone = Australia/Melbourne
> >>> >>
> >>> >> any other ideas ?
> >>> >>
> >>> >>
> >>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
> >>> Sam.Hernandez-gill@qvc.com> wrote:
> >>> >>
> >>> >> I think that’s usually the php.ini timezone setting when the
> >>filtered
> >>> time doesn’t match, check out what you have set there, and match
> >your
> >>> system’s timezone and restart apache
> >>> >>
> >>> >>
> >>> >>
> >>> >> From: observium [mailto:observium-bounces@observium.org ] On
> >Behalf
> >>Of
> >>> Ross [Eve IT]
> >>> >> Sent: Tuesday, March 07, 2017 1:19 AM
> >>> >> To: observium@observium.org
> >>> >> Subject: [Observium] question regarding traffic accounting
> >>> >>
> >>> >>
> >>> >>
> >>> >> Hello all,
> >>> >>
> >>> >>
> >>> >>
> >>> >> I'm using traffic accounting for multiple interfaces and have
> >>noticed a
> >>> strange occurrence.
> >>> >>
> >>> >> The graphs seem to be be producing the wrong time in the graphs.
> >>> >>
> >>> >>
> >>> >>
> >>> >> See attached;
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> If you notice the top right corner, 2017/03/08 03:15:04
> >>> >>
> >>> >> It's Tues 7th here 5:15pm.
> >>> >>
> >>> >>
> >>> >>
> >>> >> The server clock is synced NTP.
> >>> >>
> >>> >>
> >>> >>
> >>> >> Is there something I've missed here ?
> >>> >>
> >>> >>
> >>> >>
> >>> >> Observium 17.3.8420 (rolling)
> >>> >>
> >>> >> Debian Wheezy.
> >>> >>
> >>> >>
> >>> >>
> >>> >> Ross.
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> ----------------------------
> >>> >> This message (including any attachments) contains confidential
> >>> information intended for a specific individual and purpose, and is
> >>> protected by law. If you are not the intended recipient of this
> >>> (even if the e-mail address above is yours), (i) you may not use,
> >>copy or
> >>> retransmit it, (ii) please delete this message and (iii) please
> >>notify the
> >>> sender immediately. Any disclosure, copying, or distribution of this
> >>> message or the taking of any action based on it, is strictly
> >>prohibited.
> >>> >> ----------------------------
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> observium mailing list
> >>> >> observium@observium.org
> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>> >>
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> observium mailing list
> >>> >> observium@observium.org
> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>> >>
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> observium mailing list
> >>> >> observium@observium.org
> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>> >>
> >>> >>
> >>> >> _______________________________________________
> >>> >> observium mailing list
> >>> >> observium@observium.org
> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>> >
> >>> > _______________________________________________
> >>> > observium mailing list
> >>> > observium@observium.org
> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > observium mailing list
> >>> > observium@observium.org
> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>>
> >>> _______________________________________________
> >>> observium mailing list
> >>> observium@observium.org
> >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> >>>
> >>
> >>
> >>---------------------------------------------------------- --------------
> >>
> >>_______________________________________________
> >>observium mailing list
> >>observium@observium.org
> >>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
> _______________________________________________
> observium mailing list
> observium@observium.org
> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170309/e41b7cdb/ attachment-0001.html
------------------------------
Message: 5
Date: Wed, 08 Mar 2017 21:34:54 +0000
From: "Adam Armstrong" <adama@memetic.org>
To: "" <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID: <140dbd40-52ae-4131-bef0-0d93fe385cfc@getmailbird.com >
Content-Type: text/plain; charset="utf-8"
What do the text elements of the UI say? (outside of the javascript).
The graphs are drawn by javascript, which also interacts with your local timezone (though i developed that code in the USA, on a timezone different to the server, which is in germany, so it shouldn't matter)
adam.
On 08/03/2017 21:26:23, Ross [Eve IT] <ross@eve-it.net> wrote:
Thanks Michael, good reference.
However I don't think that's my issue.
Is there any way I can debug the traffic accounting module to see where this timestamp is being set perhaps ?
SUMMARY
observium bill accounting
Last calculated Thursday, 9 March 2017 @ 08:22:34
date on machine
root@eros:/usr/share/zoneinfo# date
Thursday 9 March 08:23:08 AEDT 2017
on observium graph, last plot is
09/03/17 21:20
The graph seems to be reporting approx 13 hours in the future.
On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com [mailto:obslist@smarsz.com]> wrote:
Maybe you're confused. In Australia, we call c*nts mate and our mates c*nt...
Here is a good vmware page on clock and ntpd settings for guests. https://kb.vmware.com/selfservice/microsites/search. [https://kb.vmware.com/do?language=en_US&cmd= displayKC&externalId=1006427 selfservice/microsites/search. ]do?language=en_US&cmd= displayKC&externalId= 1006427
Michael
On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
>It has to be large to keep the c*nt per square mile density the same as
>in normal countries...
>
>...
>
>:D
>
>Sent from BlueMail
>
>On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net [mailto:ross@eve-it.net]>
>wrote:
>>Thanks for the response,
>>It is virtual, we did actually vmotion a few hosts to this server
>>including
>>the Observium machine.
>>
>>But I've checked the hypervisor, and its clock is good.
>>Also uses NTP, same as the other Hypervisors.
>>
>>Although good point, I've actually been thinking about that exact same
>>thing for logging purposes. UTC across the board as we also span a few
>>timezones, Australia is large!
>>
>>
>>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com [mailto:obslist@smarsz.com]> wrote:
>>
>>> It's very odd as there's no timezone of UTC+21.
>>>
>>> Your Observium instance isn't virtual is it? We've encountered
>>problems
>>> with guests set to obtain their time from the local clock and (on
>>ESXi
>>> hypervisors) have a massive time jump when vmotioned to a new host
>as
>>they
>>> grab their time from that clock. Any inconsistencies between the
>>> hypervisors will throw your guests clock big time. All of a sudden,
>>your
>>> guest has jumped +10 hours (and ntpd will often wet its pants and
>>refuse to
>>> correct such a huge offset)...
>>>
>>> We had a similar problem to above when one hypervisor was set to our
>>local
>>> time (+10/11, same as you) when it was supposed to be set to UTC.
>In
>>our
>>> case, we run all of our clocks deliberately in UTC to preserve
>>logging
>>> integrity etc (you never get duplicated log times during the
>daylight
>>> savings shift).
>>>
>>> Might not be your issue, but it may help somebody else (and worth
>>keeping
>>> in mind)!
>>>
>>> Michael
>>>
>>>
>>>
>>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]> wrote:
>>> >
>>> > Looks correct
>>> >
>>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>>> > +--------------------------------+
>>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>>> > +--------------------------------+
>>> > | 11:00:00 |
>>> > +--------------------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>>> > +--------------------+---------------------+
>>> > | @@global.time_zone | @@session.time_zone |
>>> > +--------------------+---------------------+
>>> > | SYSTEM | SYSTEM |
>>> > +--------------------+---------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > # date
>>> > Wednesday 8 March 20:55:17 AEDT 2017
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de [mailto:schmitz@eseven.de]>
>>wrote:
>>> > MySQL Time ?
>>> >
>>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]>:
>>> >
>>> >> Tried all that, still no go.
>>> >>
>>> >> I've set PHP to the right timezone.
>>> >> NTP is set and running on all our servers.
>>> >>
>>> >> Any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>>> sophanith.chhom@gmail.com [mailto:sophanith.chhom@gmail.com ]> wrote:
>>> >> Try to use single quote? eg:
>>> >>
>>> >> date.timezone = 'Australia/Melbourne'
>>> >>
>>> >> Then restart httpd service
>>> >>
>>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]>
>>wrote:
>>> >> Hi Sam,
>>> >> thanks for responding.
>>> >> however I already have that set correctly.
>>> >>
>>> >> [Date]
>>> >> ; Defines the default timezone used by the date functions
>>> >> ; http://php.net/date.timezone [http://php.net/date.timezone]
>>> >> date.timezone = Australia/Melbourne
>>> >>
>>> >> any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>>> Sam.Hernandez-gill@qvc.com [mailto:Sam.Hernandez-gill@qvc.com ]> wrote:
>>> >>
>>> >> I think that’s usually the php.ini timezone setting when the
>>filtered
>>> time doesn’t match, check out what you have set there, and match
>your
>>> system’s timezone and restart apache
>>> >>
>>> >>
>>> >>
>>> >> From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org ]] On
>Behalf
>>Of
>>> Ross [Eve IT]
>>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>>> >> To: observium@observium.org [mailto:observium@observium.org ]
>>> >> Subject: [Observium] question regarding traffic accounting
>>> >>
>>> >>
>>> >>
>>> >> Hello all,
>>> >>
>>> >>
>>> >>
>>> >> I'm using traffic accounting for multiple interfaces and have
>>noticed a
>>> strange occurrence.
>>> >>
>>> >> The graphs seem to be be producing the wrong time in the graphs.
>>> >>
>>> >>
>>> >>
>>> >> See attached;
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> If you notice the top right corner, 2017/03/08 03:15:04
>>> >>
>>> >> It's Tues 7th here 5:15pm.
>>> >>
>>> >>
>>> >>
>>> >> The server clock is synced NTP.
>>> >>
>>> >>
>>> >>
>>> >> Is there something I've missed here ?
>>> >>
>>> >>
>>> >>
>>> >> Observium 17.3.8420 (rolling)
>>> >>
>>> >> Debian Wheezy.
>>> >>
>>> >>
>>> >>
>>> >> Ross.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ----------------------------
>>> >> This message (including any attachments) contains confidential
>>> information intended for a specific individual and purpose, and is
>>> protected by law. If you are not the intended recipient of this
>>> (even if the e-mail address above is yours), (i) you may not use,
>>copy or
>>> retransmit it, (ii) please delete this message and (iii) please
>>notify the
>>> sender immediately. Any disclosure, copying, or distribution of this
>>> message or the taking of any action based on it, is strictly
>>prohibited.
>>> >> ----------------------------
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org [mailto:observium@observium.org ]
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org [mailto:observium@observium.org ]
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>>
>>> _______________________________________________
>>> observium mailing list
>>> observium@observium.org [mailto:observium@observium.org ]
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>>
>>
>>
>>---------------------------------------------------------- --------------
>>
>>_______________________________________________
>>observium mailing list
>>observium@observium.org [mailto:observium@observium.org ]
>>http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
_______________________________________________
observium mailing list
observium@observium.org [mailto:observium@observium.org ]
http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/edc95c37/ attachment-0001.html
------------------------------
Message: 6
Date: Wed, 08 Mar 2017 21:35:47 +0000
From: "Adam Armstrong" <adama@memetic.org>
To: "" <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID: <06bd0813-e7cf-4206-9cb8-dbe2ee0558d3@getmailbird.com >
Content-Type: text/plain; charset="utf-8"
And "./poller.php -d" will give you timezone info :
##### Timezones info #####
o Date Wednesday, 08-Mar-17 22:35:13 CET
o PHP +01:00
o MySQL +01:00
adam.
On 08/03/2017 21:34:54, Adam Armstrong <adama@memetic.org> wrote:
What do the text elements of the UI say? (outside of the javascript).
The graphs are drawn by javascript, which also interacts with your local timezone (though i developed that code in the USA, on a timezone different to the server, which is in germany, so it shouldn't matter)
adam.
On 08/03/2017 21:26:23, Ross [Eve IT] <ross@eve-it.net> wrote:
Thanks Michael, good reference.
However I don't think that's my issue.
Is there any way I can debug the traffic accounting module to see where this timestamp is being set perhaps ?
SUMMARY
observium bill accounting
Last calculated Thursday, 9 March 2017 @ 08:22:34
date on machine
root@eros:/usr/share/zoneinfo# date
Thursday 9 March 08:23:08 AEDT 2017
on observium graph, last plot is
09/03/17 21:20
The graph seems to be reporting approx 13 hours in the future.
On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com [mailto:obslist@smarsz.com]> wrote:
Maybe you're confused. In Australia, we call c*nts mate and our mates c*nt...
Here is a good vmware page on clock and ntpd settings for guests. https://kb.vmware.com/selfservice/microsites/search. [https://kb.vmware.com/do?language=en_US&cmd= displayKC&externalId=1006427 selfservice/microsites/search. ]do?language=en_US&cmd= displayKC&externalId= 1006427
Michael
On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org [mailto:adama@memetic.org]> wrote:
>It has to be large to keep the c*nt per square mile density the same as
>in normal countries...
>
>...
>
>:D
>
>Sent from BlueMail
>
>On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net [mailto:ross@eve-it.net]>
>wrote:
>>Thanks for the response,
>>It is virtual, we did actually vmotion a few hosts to this server
>>including
>>the Observium machine.
>>
>>But I've checked the hypervisor, and its clock is good.
>>Also uses NTP, same as the other Hypervisors.
>>
>>Although good point, I've actually been thinking about that exact same
>>thing for logging purposes. UTC across the board as we also span a few
>>timezones, Australia is large!
>>
>>
>>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com [mailto:obslist@smarsz.com]> wrote:
>>
>>> It's very odd as there's no timezone of UTC+21.
>>>
>>> Your Observium instance isn't virtual is it? We've encountered
>>problems
>>> with guests set to obtain their time from the local clock and (on
>>ESXi
>>> hypervisors) have a massive time jump when vmotioned to a new host
>as
>>they
>>> grab their time from that clock. Any inconsistencies between the
>>> hypervisors will throw your guests clock big time. All of a sudden,
>>your
>>> guest has jumped +10 hours (and ntpd will often wet its pants and
>>refuse to
>>> correct such a huge offset)...
>>>
>>> We had a similar problem to above when one hypervisor was set to our
>>local
>>> time (+10/11, same as you) when it was supposed to be set to UTC.
>In
>>our
>>> case, we run all of our clocks deliberately in UTC to preserve
>>logging
>>> integrity etc (you never get duplicated log times during the
>daylight
>>> savings shift).
>>>
>>> Might not be your issue, but it may help somebody else (and worth
>>keeping
>>> in mind)!
>>>
>>> Michael
>>>
>>>
>>>
>>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]> wrote:
>>> >
>>> > Looks correct
>>> >
>>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>>> > +--------------------------------+
>>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>>> > +--------------------------------+
>>> > | 11:00:00 |
>>> > +--------------------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>>> > +--------------------+---------------------+
>>> > | @@global.time_zone | @@session.time_zone |
>>> > +--------------------+---------------------+
>>> > | SYSTEM | SYSTEM |
>>> > +--------------------+---------------------+
>>> > 1 row in set (0.00 sec)
>>> >
>>> > mysql>
>>> >
>>> > # date
>>> > Wednesday 8 March 20:55:17 AEDT 2017
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de [mailto:schmitz@eseven.de]>
>>wrote:
>>> > MySQL Time ?
>>> >
>>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]>:
>>> >
>>> >> Tried all that, still no go.
>>> >>
>>> >> I've set PHP to the right timezone.
>>> >> NTP is set and running on all our servers.
>>> >>
>>> >> Any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>>> sophanith.chhom@gmail.com [mailto:sophanith.chhom@gmail.com ]> wrote:
>>> >> Try to use single quote? eg:
>>> >>
>>> >> date.timezone = 'Australia/Melbourne'
>>> >>
>>> >> Then restart httpd service
>>> >>
>>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net [mailto:ross@eve-it.net]>
>>wrote:
>>> >> Hi Sam,
>>> >> thanks for responding.
>>> >> however I already have that set correctly.
>>> >>
>>> >> [Date]
>>> >> ; Defines the default timezone used by the date functions
>>> >> ; http://php.net/date.timezone [http://php.net/date.timezone]
>>> >> date.timezone = Australia/Melbourne
>>> >>
>>> >> any other ideas ?
>>> >>
>>> >>
>>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>>> Sam.Hernandez-gill@qvc.com [mailto:Sam.Hernandez-gill@qvc.com ]> wrote:
>>> >>
>>> >> I think that’s usually the php.ini timezone setting when the
>>filtered
>>> time doesn’t match, check out what you have set there, and match
>your
>>> system’s timezone and restart apache
>>> >>
>>> >>
>>> >>
>>> >> From: observium [mailto:observium-bounces@observium.org [mailto:observium-bounces@observium.org ]] On
>Behalf
>>Of
>>> Ross [Eve IT]
>>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>>> >> To: observium@observium.org [mailto:observium@observium.org ]
>>> >> Subject: [Observium] question regarding traffic accounting
>>> >>
>>> >>
>>> >>
>>> >> Hello all,
>>> >>
>>> >>
>>> >>
>>> >> I'm using traffic accounting for multiple interfaces and have
>>noticed a
>>> strange occurrence.
>>> >>
>>> >> The graphs seem to be be producing the wrong time in the graphs.
>>> >>
>>> >>
>>> >>
>>> >> See attached;
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> If you notice the top right corner, 2017/03/08 03:15:04
>>> >>
>>> >> It's Tues 7th here 5:15pm.
>>> >>
>>> >>
>>> >>
>>> >> The server clock is synced NTP.
>>> >>
>>> >>
>>> >>
>>> >> Is there something I've missed here ?
>>> >>
>>> >>
>>> >>
>>> >> Observium 17.3.8420 (rolling)
>>> >>
>>> >> Debian Wheezy.
>>> >>
>>> >>
>>> >>
>>> >> Ross.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ----------------------------
>>> >> This message (including any attachments) contains confidential
>>> information intended for a specific individual and purpose, and is
>>> protected by law. If you are not the intended recipient of this
>>> (even if the e-mail address above is yours), (i) you may not use,
>>copy or
>>> retransmit it, (ii) please delete this message and (iii) please
>>notify the
>>> sender immediately. Any disclosure, copying, or distribution of this
>>> message or the taking of any action based on it, is strictly
>>prohibited.
>>> >> ----------------------------
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> observium mailing list
>>> >> observium@observium.org [mailto:observium@observium.org ]
>>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org [mailto:observium@observium.org ]
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>> >
>>> >
>>> > _______________________________________________
>>> > observium mailing list
>>> > observium@observium.org [mailto:observium@observium.org ]
>>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>>
>>> _______________________________________________
>>> observium mailing list
>>> observium@observium.org [mailto:observium@observium.org ]
>>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
>>>
>>
>>
>>---------------------------------------------------------- --------------
>>
>>_______________________________________________
>>observium mailing list
>>observium@observium.org [mailto:observium@observium.org ]
>>http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
_______________________________________________
observium mailing list
observium@observium.org [mailto:observium@observium.org ]
http://postman.memetic.org/cgi-bin/mailman/listinfo/ [http://postman.memetic.org/observium cgi-bin/mailman/listinfo/ ]observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/c0989944/ attachment-0001.html
------------------------------
Message: 7
Date: Wed, 8 Mar 2017 06:18:59 +0000
From: Max Krabbenhöft <max.krabbenhoft@cinnober.com>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] Windows Processor Numbers are Odd
Message-ID:
<VI1PR0501MB2336226EFACCCB4A01F8475D992E0@VI1PR0501MB2336. >eurprd05.prod.outlook.com
Content-Type: text/plain; charset="utf-8"
Hi Don,
I used this guide to get wmi-polling for our Windows hosts.
http://jira.observium.org/secure/attachment/11319/ WMIPoller-011013-1429-4.pdf
Works very well.
About your max-numbers, I’ve got no clue, it’s working fine for me.
BR
Max
From: observium [mailto:observium-bounces@observium.org ] On Behalf Of Don Maker
Sent: den 8 mars 2017 02:04
To: observium@observium.org
Subject: [Observium] Windows Processor Numbers are Odd
I got observium working almost exactly how I want it, but I have an issue with Windows cpu numbers. The graph looks fine (I think), but the numbers are weird. The max numbers look like a percentage, but the now and Avg show odd things like 640.5m I have no idea what that means. Also, the processor is never identified properly.
I would happily change to wmi for Windows devices, but I'm not sure how that is done, or if it is stable.
Does anyone have any suggestions or experiences with wmi and observium?
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/5a3528c1/ attachment-0001.html
------------------------------
Message: 8
Date: Wed, 8 Mar 2017 16:09:32 -0700
From: Lorenzo Zafra <lorenzo.zafra@edmonton.ca>
To: Observium Public Support <observium@observium.org>
Subject: [Observium] SVN Update doesn't seem to update observium
Message-ID:
<CAKbXqmnvu7ChA4vvc6pkSSHiTgiVoraQDGATmq6nrbSpL_s4sA@mail. >gmail.com
Content-Type: text/plain; charset="utf-8"
Hello All,
I submitted a patch and it was commited in r8368, but when I run svn update
to r8428 I dont get any of the changes. Anyone know whats wrong? We are
running the subscription edition, if that matters.
I checked to see if I would get the patch when creating a new copy of
observium through [svn co ... ] and yes it worked fine.
--
[image: Edmonton_sig_RGB_S.jpg]
Lorenzo Zafra
COMMUNICATIONS ENGINEERING STUDENT
ENGINEERING & MAINTENANCE
CITY OPERATIONS | EDMONTON TRANSIT
7 <(780)%20442-5021>80-944-0419 OFFICE
7 <(780)%20668-1302>80-885-3696 MOBILE
l <matthew.dyck@edmonton.ca>orenzo.zafra@edmonton.ca
City of Edmonton
D.L. MacDonald Transit Yards
ROW Building
13304 - 50A Street
Edmonton AB T5A 4P6
All information contained in this email post is proprietary to the City of
Edmonton, confidential and intended only for the addressed recipient. If
you have received this post in error, please disregard the contents, inform
the sender of the misdirection, and remove it from your system. The
copying, dissemination or distribution of this email, if misdirected, is
strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/e6fefb22/ attachment-0001.html
------------------------------
Message: 9
Date: Wed, 08 Mar 2017 23:23:23 +0000
From: Adam Armstrong <adama@memetic.org>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] Windows Processor Numbers are Odd
Message-ID: <46c73af4-9ab9-4657-a7ec-08d0785860c9@typeapp.com >
Content-Type: text/plain; charset="utf-8"
643m means 0.643
Adam.
Sent from BlueMail
On 8 Mar 2017, 22:55, at 22:55, "Max Krabbenhöft" <max.krabbenhoft@cinnober.com> wrote:
>Hi Don,
>
>I used this guide to get wmi-polling for our Windows hosts.
>
>http://jira.observium.org/secure/attachment/11319/ WMIPoller-011013-1429-4.pdf
>
>Works very well.
>About your max-numbers, I’ve got no clue, it’s working fine for me.
>
>BR
>Max
>
>From: observium [mailto:observium-bounces@observium.org ] On Behalf Of
>Don Maker
>Sent: den 8 mars 2017 02:04
>To: observium@observium.org
>Subject: [Observium] Windows Processor Numbers are Odd
>
>I got observium working almost exactly how I want it, but I have an
>issue with Windows cpu numbers. The graph looks fine (I think), but the
>numbers are weird. The max numbers look like a percentage, but the now
>and Avg show odd things like 640.5m I have no idea what that means.
>Also, the processor is never identified properly.
>
>I would happily change to wmi for Windows devices, but I'm not sure how
>that is done, or if it is stable.
>
>Does anyone have any suggestions or experiences with wmi and observium?
>
>Thanks!
>
>
>
>----------------------------------------------------------- -------------
>
>_______________________________________________
>observium mailing list
>observium@observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/991b753b/ attachment-0001.html
------------------------------
Message: 10
Date: Wed, 08 Mar 2017 23:25:15 +0000
From: Adam Armstrong <adama@memetic.org>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] SVN Update doesn't seem to update observium
Message-ID: <db18f4d8-6f67-4e2a-a8af-5d95691011d7@typeapp.com >
Content-Type: text/plain; charset="utf-8"
You're not being very specific about what on earth you're talking about and what you expect to happen.
There is practically zero chance of it not working, and with literally zero information beyond "why no work?????", there is no way to tell you what you are doing or expecting wrong.
Adam.
Sent from BlueMail
On 8 Mar 2017, 23:09, at 23:09, Lorenzo Zafra <lorenzo.zafra@edmonton.ca> wrote:
>Hello All,
>
>I submitted a patch and it was commited in r8368, but when I run svn
>update
>to r8428 I dont get any of the changes. Anyone know whats wrong? We are
>running the subscription edition, if that matters.
>
>I checked to see if I would get the patch when creating a new copy of
>observium through [svn co ... ] and yes it worked fine.
>
>--
>
>[image: Edmonton_sig_RGB_S.jpg]
>
>Lorenzo Zafra
>
>COMMUNICATIONS ENGINEERING STUDENT
>ENGINEERING & MAINTENANCE
>
>CITY OPERATIONS | EDMONTON TRANSIT
>
>7 <(780)%20442-5021>80-944-0419 OFFICE
>7 <(780)%20668-1302>80-885-3696 MOBILE
>
>l <matthew.dyck@edmonton.ca>orenzo.zafra@edmonton.ca
>
>City of Edmonton
>
>D.L. MacDonald Transit Yards
>
>ROW Building
>
>13304 - 50A Street
>
>Edmonton AB T5A 4P6
>
>All information contained in this email post is proprietary to the City
>of
>Edmonton, confidential and intended only for the addressed recipient.
>If
>you have received this post in error, please disregard the contents,
>inform
>the sender of the misdirection, and remove it from your system. The
>copying, dissemination or distribution of this email, if misdirected,
>is
>strictly prohibited.
>
>
>----------------------------------------------------------- -------------
>
>_______________________________________________
>observium mailing list
>observium@observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170308/753be1ce/ attachment-0001.html
------------------------------
Message: 11
Date: Thu, 9 Mar 2017 12:25:13 +1100
From: "Ross [Eve IT]" <ross@eve-it.net>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID:
<CAODA=KEwv9Nd-qnySkv66oU_FNN1CQN=r199K6fU3yv-R=w9OA@ mail.gmail.com >
Content-Type: text/plain; charset="utf-8"
##### *Timezones info* #####
o *Date * Thursday, 09-Mar-17 12:06:28 AEDT
o *PHP * +11:00
o *MySQL * +11:00
On Thu, Mar 9, 2017 at 8:35 AM, Adam Armstrong <adama@memetic.org> wrote:
> And "./poller.php -d" will give you timezone info :
>
> ##### Timezones info #####
>
> o Date Wednesday, 08-Mar-17 22:35:13 CET
> o PHP +01:00
> o MySQL +01:00
>
> adam.
>
> On 08/03/2017 21:34:54, Adam Armstrong <adama@memetic.org> wrote:
> What do the text elements of the UI say? (outside of the javascript).
>
> The graphs are drawn by javascript, which also interacts with your local
> timezone (though i developed that code in the USA, on a timezone different
> to the server, which is in germany, so it shouldn't matter)
>
> adam.
>
> On 08/03/2017 21:26:23, Ross [Eve IT] <ross@eve-it.net> wrote:
> Thanks Michael, good reference.
>
> However I don't think that's my issue.
> Is there any way I can debug the traffic accounting module to see where
> this timestamp is being set perhaps ?
>
> SUMMARY
>
> observium bill accounting
> Last calculated Thursday, 9 March 2017 @ 08:22:34
>
> date on machine
> root@eros:/usr/share/zoneinfo# date
> Thursday 9 March 08:23:08 AEDT 2017
>
> on observium graph, last plot is
> 09/03/17 21:20
>
> The graph seems to be reporting approx 13 hours in the future.
>
> On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com> wrote:
>
>> Maybe you're confused. In Australia, we call c*nts mate and our mates
>> c*nt...
>>
>> Here is a good vmware page on clock and ntpd settings for guests.
>> https://kb.vmware.com/selfservice/microsites/search. ?do
>> language=en_US&cmd=displayKC&externalId=1006427
>>
>> Michael
>>
>>
>>
>> On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org>
>> wrote:
>> >It has to be large to keep the c*nt per square mile density the same as
>> >in normal countries...
>> >
>> >...
>> >
>> >:D
>> >
>> >Sent from BlueMail
>> >
>> >On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net>
>> >wrote:
>> >>Thanks for the response,
>> >>It is virtual, we did actually vmotion a few hosts to this server
>> >>including
>> >>the Observium machine.
>> >>
>> >>But I've checked the hypervisor, and its clock is good.
>> >>Also uses NTP, same as the other Hypervisors.
>> >>
>> >>Although good point, I've actually been thinking about that exact same
>> >>thing for logging purposes. UTC across the board as we also span a few
>> >>timezones, Australia is large!
>> >>
>> >>
>> >>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com> wrote:
>> >>
>> >>> It's very odd as there's no timezone of UTC+21.
>> >>>
>> >>> Your Observium instance isn't virtual is it? We've encountered
>> >>problems
>> >>> with guests set to obtain their time from the local clock and (on
>> >>ESXi
>> >>> hypervisors) have a massive time jump when vmotioned to a new host
>> >as
>> >>they
>> >>> grab their time from that clock. Any inconsistencies between the
>> >>> hypervisors will throw your guests clock big time. All of a sudden,
>> >>your
>> >>> guest has jumped +10 hours (and ntpd will often wet its pants and
>> >>refuse to
>> >>> correct such a huge offset)...
>> >>>
>> >>> We had a similar problem to above when one hypervisor was set to our
>> >>local
>> >>> time (+10/11, same as you) when it was supposed to be set to UTC.
>> >In
>> >>our
>> >>> case, we run all of our clocks deliberately in UTC to preserve
>> >>logging
>> >>> integrity etc (you never get duplicated log times during the
>> >daylight
>> >>> savings shift).
>> >>>
>> >>> Might not be your issue, but it may help somebody else (and worth
>> >>keeping
>> >>> in mind)!
>> >>>
>> >>> Michael
>> >>>
>> >>>
>> >>>
>> >>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net> wrote:
>> >>> >
>> >>> > Looks correct
>> >>> >
>> >>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>> >>> > +--------------------------------+
>> >>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>> >>> > +--------------------------------+
>> >>> > | 11:00:00 |
>> >>> > +--------------------------------+
>> >>> > 1 row in set (0.00 sec)
>> >>> >
>> >>> > mysql>
>> >>> >
>> >>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>> >>> > +--------------------+---------------------+
>> >>> > | @@global.time_zone | @@session.time_zone |
>> >>> > +--------------------+---------------------+
>> >>> > | SYSTEM | SYSTEM |
>> >>> > +--------------------+---------------------+
>> >>> > 1 row in set (0.00 sec)
>> >>> >
>> >>> > mysql>
>> >>> >
>> >>> > # date
>> >>> > Wednesday 8 March 20:55:17 AEDT 2017
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de>
>> >>wrote:
>> >>> > MySQL Time ?
>> >>> >
>> >>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net>:
>> >>> >
>> >>> >> Tried all that, still no go.
>> >>> >>
>> >>> >> I've set PHP to the right timezone.
>> >>> >> NTP is set and running on all our servers.
>> >>> >>
>> >>> >> Any other ideas ?
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>> >>> sophanith.chhom@gmail.com> wrote:
>> >>> >> Try to use single quote? eg:
>> >>> >>
>> >>> >> date.timezone = 'Australia/Melbourne'
>> >>> >>
>> >>> >> Then restart httpd service
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net>
>> >>wrote:
>> >>> >> Hi Sam,
>> >>> >> thanks for responding.
>> >>> >> however I already have that set correctly.
>> >>> >>
>> >>> >> [Date]
>> >>> >> ; Defines the default timezone used by the date functions
>> >>> >> ; http://php.net/date.timezone
>> >>> >> date.timezone = Australia/Melbourne
>> >>> >>
>> >>> >> any other ideas ?
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>> >>> Sam.Hernandez-gill@qvc.com> wrote:
>> >>> >>
>> >>> >> I think that’s usually the php.ini timezone setting when the
>> >>filtered
>> >>> time doesn’t match, check out what you have set there, and match
>> >your
>> >>> system’s timezone and restart apache
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> From: observium [mailto:observium-bounces@observium.org ] On
>> >Behalf
>> >>Of
>> >>> Ross [Eve IT]
>> >>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>> >>> >> To: observium@observium.org
>> >>> >> Subject: [Observium] question regarding traffic accounting
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Hello all,
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> I'm using traffic accounting for multiple interfaces and have
>> >>noticed a
>> >>> strange occurrence.
>> >>> >>
>> >>> >> The graphs seem to be be producing the wrong time in the graphs.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> See attached;
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> If you notice the top right corner, 2017/03/08 03:15:04
>> >>> >>
>> >>> >> It's Tues 7th here 5:15pm.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> The server clock is synced NTP.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Is there something I've missed here ?
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Observium 17.3.8420 (rolling)
>> >>> >>
>> >>> >> Debian Wheezy.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Ross.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> ----------------------------
>> >>> >> This message (including any attachments) contains confidential
>> >>> information intended for a specific individual and purpose, and is
>> >>> protected by law. If you are not the intended recipient of this
>> >>> (even if the e-mail address above is yours), (i) you may not use,
>> >>copy or
>> >>> retransmit it, (ii) please delete this message and (iii) please
>> >>notify the
>> >>> sender immediately. Any disclosure, copying, or distribution of this
>> >>> message or the taking of any action based on it, is strictly
>> >>prohibited.
>> >>> >> ----------------------------
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >
>> >>> > _______________________________________________
>> >>> > observium mailing list
>> >>> > observium@observium.org
>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >
>> >>> >
>> >>> > _______________________________________________
>> >>> > observium mailing list
>> >>> > observium@observium.org
>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>>
>> >>> _______________________________________________
>> >>> observium mailing list
>> >>> observium@observium.org
>> >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>>
>> >>
>> >>
>> >>----------------------------------------------------------
>> --------------
>> >>
>> >>_______________________________________________
>> >>observium mailing list
>> >>observium@observium.org
>> >>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> _______________________________________________
>> observium mailing list
>> observium@observium.org
>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>
>
> _______________________________________________ observium mailing list
> observium@observium.org http://postman.memetic.org/
> cgi-bin/mailman/listinfo/observium
>
>
> _______________________________________________
> observium mailing list
> observium@observium.org
> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170309/4ba97f67/ attachment-0001.html
------------------------------
Message: 12
Date: Thu, 9 Mar 2017 13:47:22 +1100
From: "Ross [Eve IT]" <ross@eve-it.net>
To: Observium Public Support <observium@observium.org>
Subject: Re: [Observium] question regarding traffic accounting
Message-ID:
<CAODA=KHmrJsOGLSZhbp-jJZaUXwe6n1Ce8cHGWktGaktmQJkOA >@mail.gmail.com
Content-Type: text/plain; charset="utf-8"
Not sure exactly what you mean ?
What's the best way to get this info ?
On Thu, Mar 9, 2017 at 8:34 AM, Adam Armstrong <adama@memetic.org> wrote:
> What do the text elements of the UI say? (outside of the javascript).
>
> The graphs are drawn by javascript, which also interacts with your local
> timezone (though i developed that code in the USA, on a timezone different
> to the server, which is in germany, so it shouldn't matter)
>
> adam.
>
> On 08/03/2017 21:26:23, Ross [Eve IT] <ross@eve-it.net> wrote:
> Thanks Michael, good reference.
>
> However I don't think that's my issue.
> Is there any way I can debug the traffic accounting module to see where
> this timestamp is being set perhaps ?
>
> SUMMARY
>
> observium bill accounting
> Last calculated Thursday, 9 March 2017 @ 08:22:34
>
> date on machine
> root@eros:/usr/share/zoneinfo# date
> Thursday 9 March 08:23:08 AEDT 2017
>
> on observium graph, last plot is
> 09/03/17 21:20
>
> The graph seems to be reporting approx 13 hours in the future.
>
> On Thu, Mar 9, 2017 at 6:00 AM, Michael <obslist@smarsz.com> wrote:
>
>> Maybe you're confused. In Australia, we call c*nts mate and our mates
>> c*nt...
>>
>> Here is a good vmware page on clock and ntpd settings for guests.
>> https://kb.vmware.com/selfservice/microsites/search. ?do
>> language=en_US&cmd=displayKC&externalId=1006427
>>
>> Michael
>>
>>
>>
>> On 8 March 2017 11:06:39 PM LHDT, Adam Armstrong <adama@memetic.org>
>> wrote:
>> >It has to be large to keep the c*nt per square mile density the same as
>> >in normal countries...
>> >
>> >...
>> >
>> >:D
>> >
>> >Sent from BlueMail
>> >
>> >On 8 Mar 2017, 10:36, at 10:36, "Ross [Eve IT]" <ross@eve-it.net>
>> >wrote:
>> >>Thanks for the response,
>> >>It is virtual, we did actually vmotion a few hosts to this server
>> >>including
>> >>the Observium machine.
>> >>
>> >>But I've checked the hypervisor, and its clock is good.
>> >>Also uses NTP, same as the other Hypervisors.
>> >>
>> >>Although good point, I've actually been thinking about that exact same
>> >>thing for logging purposes. UTC across the board as we also span a few
>> >>timezones, Australia is large!
>> >>
>> >>
>> >>On Wed, Mar 8, 2017 at 9:29 PM, Michael <obslist@smarsz.com> wrote:
>> >>
>> >>> It's very odd as there's no timezone of UTC+21.
>> >>>
>> >>> Your Observium instance isn't virtual is it? We've encountered
>> >>problems
>> >>> with guests set to obtain their time from the local clock and (on
>> >>ESXi
>> >>> hypervisors) have a massive time jump when vmotioned to a new host
>> >as
>> >>they
>> >>> grab their time from that clock. Any inconsistencies between the
>> >>> hypervisors will throw your guests clock big time. All of a sudden,
>> >>your
>> >>> guest has jumped +10 hours (and ntpd will often wet its pants and
>> >>refuse to
>> >>> correct such a huge offset)...
>> >>>
>> >>> We had a similar problem to above when one hypervisor was set to our
>> >>local
>> >>> time (+10/11, same as you) when it was supposed to be set to UTC.
>> >In
>> >>our
>> >>> case, we run all of our clocks deliberately in UTC to preserve
>> >>logging
>> >>> integrity etc (you never get duplicated log times during the
>> >daylight
>> >>> savings shift).
>> >>>
>> >>> Might not be your issue, but it may help somebody else (and worth
>> >>keeping
>> >>> in mind)!
>> >>>
>> >>> Michael
>> >>>
>> >>>
>> >>>
>> >>> > On 8 Mar 2017, at 8:55 pm, Ross [Eve IT] <ross@eve-it.net> wrote:
>> >>> >
>> >>> > Looks correct
>> >>> >
>> >>> > mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
>> >>> > +--------------------------------+
>> >>> > | TIMEDIFF(NOW(), UTC_TIMESTAMP) |
>> >>> > +--------------------------------+
>> >>> > | 11:00:00 |
>> >>> > +--------------------------------+
>> >>> > 1 row in set (0.00 sec)
>> >>> >
>> >>> > mysql>
>> >>> >
>> >>> > mysql> SELECT @@global.time_zone, @@session.time_zone;
>> >>> > +--------------------+---------------------+
>> >>> > | @@global.time_zone | @@session.time_zone |
>> >>> > +--------------------+---------------------+
>> >>> > | SYSTEM | SYSTEM |
>> >>> > +--------------------+---------------------+
>> >>> > 1 row in set (0.00 sec)
>> >>> >
>> >>> > mysql>
>> >>> >
>> >>> > # date
>> >>> > Wednesday 8 March 20:55:17 AEDT 2017
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Mar 8, 2017 at 8:32 PM, Simon Schmitz <schmitz@eseven.de>
>> >>wrote:
>> >>> > MySQL Time ?
>> >>> >
>> >>> > Am 08.03.2017 um 15:31 schrieb Ross [Eve IT] <ross@eve-it.net>:
>> >>> >
>> >>> >> Tried all that, still no go.
>> >>> >>
>> >>> >> I've set PHP to the right timezone.
>> >>> >> NTP is set and running on all our servers.
>> >>> >>
>> >>> >> Any other ideas ?
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 7:45 PM, Sophanith Chhom <
>> >>> sophanith.chhom@gmail.com> wrote:
>> >>> >> Try to use single quote? eg:
>> >>> >>
>> >>> >> date.timezone = 'Australia/Melbourne'
>> >>> >>
>> >>> >> Then restart httpd service
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 3:28 PM, Ross [Eve IT] <ross@eve-it.net>
>> >>wrote:
>> >>> >> Hi Sam,
>> >>> >> thanks for responding.
>> >>> >> however I already have that set correctly.
>> >>> >>
>> >>> >> [Date]
>> >>> >> ; Defines the default timezone used by the date functions
>> >>> >> ; http://php.net/date.timezone
>> >>> >> date.timezone = Australia/Melbourne
>> >>> >>
>> >>> >> any other ideas ?
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 7, 2017 at 5:40 PM, Sam Hernandez-gill <
>> >>> Sam.Hernandez-gill@qvc.com> wrote:
>> >>> >>
>> >>> >> I think that’s usually the php.ini timezone setting when the
>> >>filtered
>> >>> time doesn’t match, check out what you have set there, and match
>> >your
>> >>> system’s timezone and restart apache
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> From: observium [mailto:observium-bounces@observium.org ] On
>> >Behalf
>> >>Of
>> >>> Ross [Eve IT]
>> >>> >> Sent: Tuesday, March 07, 2017 1:19 AM
>> >>> >> To: observium@observium.org
>> >>> >> Subject: [Observium] question regarding traffic accounting
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Hello all,
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> I'm using traffic accounting for multiple interfaces and have
>> >>noticed a
>> >>> strange occurrence.
>> >>> >>
>> >>> >> The graphs seem to be be producing the wrong time in the graphs.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> See attached;
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> If you notice the top right corner, 2017/03/08 03:15:04
>> >>> >>
>> >>> >> It's Tues 7th here 5:15pm.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> The server clock is synced NTP.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Is there something I've missed here ?
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Observium 17.3.8420 (rolling)
>> >>> >>
>> >>> >> Debian Wheezy.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> Ross.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> ----------------------------
>> >>> >> This message (including any attachments) contains confidential
>> >>> information intended for a specific individual and purpose, and is
>> >>> protected by law. If you are not the intended recipient of this
>> >>> (even if the e-mail address above is yours), (i) you may not use,
>> >>copy or
>> >>> retransmit it, (ii) please delete this message and (iii) please
>> >>notify the
>> >>> sender immediately. Any disclosure, copying, or distribution of this
>> >>> message or the taking of any action based on it, is strictly
>> >>prohibited.
>> >>> >> ----------------------------
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >>
>> >>> >>
>> >>> >> _______________________________________________
>> >>> >> observium mailing list
>> >>> >> observium@observium.org
>> >>> >> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >
>> >>> > _______________________________________________
>> >>> > observium mailing list
>> >>> > observium@observium.org
>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>> >
>> >>> >
>> >>> > _______________________________________________
>> >>> > observium mailing list
>> >>> > observium@observium.org
>> >>> > http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>>
>> >>> _______________________________________________
>> >>> observium mailing list
>> >>> observium@observium.org
>> >>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> >>>
>> >>
>> >>
>> >>----------------------------------------------------------
>> --------------
>> >>
>> >>_______________________________________________
>> >>observium mailing list
>> >>observium@observium.org
>> >>http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>> _______________________________________________
>> observium mailing list
>> observium@observium.org
>> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>>
>
> _______________________________________________ observium mailing list
> observium@observium.org http://postman.memetic.org/
> cgi-bin/mailman/listinfo/observium
>
>
> _______________________________________________
> observium mailing list
> observium@observium.org
> http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170309/a391c8e0/ attachment-0001.html
------------------------------
Message: 13
Date: Thu, 9 Mar 2017 08:44:11 +0100
From: Michael <mich4@gmx.de>
To: observium@observium.org
Subject: [Observium] Help with monitor Tomcat Traffic without Apache
Message-ID:
<trinity-4c5b56c8-92c6-482a-a62e-c1cdccf2d460- 1489045451044@3capp-gmx-bs65>
Content-Type: text/plain; charset="utf-8"
An HTML attachment was scrubbed...
URL: <http://postman.memetic.org/pipermail/observium/ >attachments/20170309/9ebb7832/ attachment-0001.html
------------------------------
Subject: Digest Footer
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/ observium
------------------------------
End of observium Digest, Vol 80, Issue 9
****************************************