Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
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
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock <markus@best-practice.se mailto:markus@best-practice.se> wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though... 2014-10-05 4:38 GMT+02:00 Ben Steele <ben@bensteele.org <mailto:ben@bensteele.org>>: Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago. On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele <ben@bensteele.org <mailto:ben@bensteele.org>> wrote: Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc.. Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here. Hover over example: I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview): Inline image 1 Anyone else seen this, any ideas? Cheers. _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto: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
Dammit, this was my fault. I didn't realise there was a separate php.ini for CLI & Apache. Apologies for the pebkac.
On Tue, Oct 7, 2014 at 5:44 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
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 listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Please elaborate a little, i see the same problem and do have the proper timezones set. What exactly was your fix here?
Thanks! Torsten
2014-10-07 11:05 GMT+02:00 Ben Steele ben@bensteele.org:
Dammit, this was my fault. I didn't realise there was a separate php.ini for CLI & Apache. Apologies for the pebkac.
On Tue, Oct 7, 2014 at 5:44 PM, Tom Laermans tom.laermans@powersource.cx wrote:
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
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 listobservium@observium.orghttp://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
My fix was to set the timezone in /etc/php5/apache2/php.ini as I had only set it in /etc/php5/cli/php.ini
On Tue, Oct 7, 2014 at 7:44 PM, Torsten-Sven Urbas < torsten-sven.urbas@profitbricks.com> wrote:
Please elaborate a little, i see the same problem and do have the proper timezones set. What exactly was your fix here?
Thanks! Torsten
2014-10-07 11:05 GMT+02:00 Ben Steele ben@bensteele.org:
Dammit, this was my fault. I didn't realise there was a separate php.ini for CLI & Apache. Apologies for the pebkac.
On Tue, Oct 7, 2014 at 5:44 PM, Tom Laermans <tom.laermans@powersource.cx
wrote:
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
Since I installed Observium a few weeks ago I have noticed that the overview timestamp for syslog and event log delta is wrong for most (not all) devices, this is prevalent on the main overview and the specific device overview page. By wrong I mean "-1y -1d -xh." etc..
Hovering over the incorrect entry pops up the correct timestamp so I think it's just the logic in calculating the delta between current time and that event that's broken, also viewing the syslogs and entry logs directly with the original timestamp is fine as well. I checked my local timezone and php timezone just to be sure and they are reporting correctly, I would imagine this would break the original timestamp anyway which is not the problem here.
Hover over example:
I find it particularly weird as not every device is doing this, the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc and some even have a mixture of working and broken entries (individual device overview):
[image: Inline image 1]
Anyone else seen this, any ideas?
Cheers.
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 listobservium@observium.orghttp://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
-- Torsten-Sven Urbas Head of Network Operation
==== Bitte beachten Sie unsere neuen Rufnummern ====
ProfitBricks GmbH • Greifswalder Str. 207 • D - 10405 Berlin Tel: +49 (30) 57700 8234 • Mobile: +49 (170) 77 38 251 • Fax: +49 (30) 57700 8296 www.profitbricks.de • torsten-sven.urbas@profitbricks.com
Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss.
Please consider the environment before printing this email.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Alright Ben, thank you.
The reason i was asking is this: We're using Observium with a standard fedora setup, there's only one php.ini in /etc - and this one has got the timezone set properly.
Time to dig deeper - thanks again! /Torsten
2014-10-07 11:32 GMT+02:00 Ben Steele ben@bensteele.org:
My fix was to set the timezone in /etc/php5/apache2/php.ini as I had only set it in /etc/php5/cli/php.ini
On Tue, Oct 7, 2014 at 7:44 PM, Torsten-Sven Urbas < torsten-sven.urbas@profitbricks.com> wrote:
Please elaborate a little, i see the same problem and do have the proper timezones set. What exactly was your fix here?
Thanks! Torsten
2014-10-07 11:05 GMT+02:00 Ben Steele ben@bensteele.org:
Dammit, this was my fault. I didn't realise there was a separate php.ini for CLI & Apache. Apologies for the pebkac.
On Tue, Oct 7, 2014 at 5:44 PM, Tom Laermans < tom.laermans@powersource.cx> wrote:
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
Just to preempt anyone, i'm synced to 5870 at the moment and am generally syncing every few days. This didn't appear to break at a particular point that I noticed, I think it's been like this since the revision I first installed a few weeks ago.
On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org wrote:
> Since I installed Observium a few weeks ago I have noticed that the > overview timestamp for syslog and event log delta is wrong for most (not > all) devices, this is prevalent on the main overview and the specific > device overview page. By wrong I mean "-1y -1d -xh." etc.. > > Hovering over the incorrect entry pops up the correct timestamp so > I think it's just the logic in calculating the delta between current time > and that event that's broken, also viewing the syslogs and entry logs > directly with the original timestamp is fine as well. I checked my local > timezone and php timezone just to be sure and they are reporting correctly, > I would imagine this would break the original timestamp anyway which is not > the problem here. > > Hover over example: > > > I find it particularly weird as not every device is doing this, > the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc > and some even have a mixture of working and broken entries (individual > device overview): > > [image: Inline image 1] > > Anyone else seen this, any ideas? > > Cheers. >
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 listobservium@observium.orghttp://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
-- Torsten-Sven Urbas Head of Network Operation
==== Bitte beachten Sie unsere neuen Rufnummern ====
ProfitBricks GmbH • Greifswalder Str. 207 • D - 10405 Berlin Tel: +49 (30) 57700 8234 • Mobile: +49 (170) 77 38 251 • Fax: +49 (30) 57700 8296 www.profitbricks.de • torsten-sven.urbas@profitbricks.com
Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss.
Please consider the environment before printing this email.
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
The only other advice I can offer is check that all the following commands are in sync, correct any that aren't:
$ php -i | grep timezone Default timezone => Australia/Adelaide date.timezone => Australia/Adelaide => Australia/Adelaide
$ date +%::z +10:30:00
mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP); +--------------------------------+ | TIMEDIFF(NOW(), UTC_TIMESTAMP) | +--------------------------------+ | 10:30:00 | +--------------------------------+ 1 row in set (0.00 sec)
On Tue, Oct 7, 2014 at 8:27 PM, Torsten-Sven Urbas < torsten-sven.urbas@profitbricks.com> wrote:
Alright Ben, thank you.
The reason i was asking is this: We're using Observium with a standard fedora setup, there's only one php.ini in /etc - and this one has got the timezone set properly.
Time to dig deeper - thanks again! /Torsten
2014-10-07 11:32 GMT+02:00 Ben Steele ben@bensteele.org:
My fix was to set the timezone in /etc/php5/apache2/php.ini as I had only set it in /etc/php5/cli/php.ini
On Tue, Oct 7, 2014 at 7:44 PM, Torsten-Sven Urbas < torsten-sven.urbas@profitbricks.com> wrote:
Please elaborate a little, i see the same problem and do have the proper timezones set. What exactly was your fix here?
Thanks! Torsten
2014-10-07 11:05 GMT+02:00 Ben Steele ben@bensteele.org:
Dammit, this was my fault. I didn't realise there was a separate php.ini for CLI & Apache. Apologies for the pebkac.
On Tue, Oct 7, 2014 at 5:44 PM, Tom Laermans < tom.laermans@powersource.cx> wrote:
Sure:
To the best of my knowledge the code surrounding this was not changed in the last half year.
Is your PHP CLI timezone = your PHP CGI/Apache timezone = your MySQL timezone?
Tom
On 10/07/2014 03:19 AM, Ben Steele wrote:
Any observium devs care to comment?
On Sun, Oct 5, 2014 at 6:09 PM, Markus Klock markus@best-practice.se wrote:
Yes, I have also noted this appearing in my logs. I update observium with cron.daily and I first started notice this last week, no idea what revision though...
2014-10-05 4:38 GMT+02:00 Ben Steele ben@bensteele.org:
> Just to preempt anyone, i'm synced to 5870 at the moment and am > generally syncing every few days. This didn't appear to break at a > particular point that I noticed, I think it's been like this since the > revision I first installed a few weeks ago. > > On Sun, Oct 5, 2014 at 1:02 PM, Ben Steele ben@bensteele.org > wrote: > >> Since I installed Observium a few weeks ago I have noticed that the >> overview timestamp for syslog and event log delta is wrong for most (not >> all) devices, this is prevalent on the main overview and the specific >> device overview page. By wrong I mean "-1y -1d -xh." etc.. >> >> Hovering over the incorrect entry pops up the correct timestamp >> so I think it's just the logic in calculating the delta between current >> time and that event that's broken, also viewing the syslogs and entry logs >> directly with the original timestamp is fine as well. I checked my local >> timezone and php timezone just to be sure and they are reporting correctly, >> I would imagine this would break the original timestamp anyway which is not >> the problem here. >> >> Hover over example: >> >> >> I find it particularly weird as not every device is doing this, >> the ones that are have no real pattern either, mixture of N7K,N5K,ASA etc >> and some even have a mixture of working and broken entries (individual >> device overview): >> >> [image: Inline image 1] >> >> Anyone else seen this, any ideas? >> >> Cheers. >> > > > _______________________________________________ > 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 listobservium@observium.orghttp://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
-- Torsten-Sven Urbas Head of Network Operation
==== Bitte beachten Sie unsere neuen Rufnummern ====
ProfitBricks GmbH • Greifswalder Str. 207 • D - 10405 Berlin Tel: +49 (30) 57700 8234 • Mobile: +49 (170) 77 38 251 • Fax: +49 (30) 57700 8296 www.profitbricks.de • torsten-sven.urbas@profitbricks.com
Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss.
Please consider the environment before printing this email.
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
-- Torsten-Sven Urbas Head of Network Operation
==== Bitte beachten Sie unsere neuen Rufnummern ====
ProfitBricks GmbH • Greifswalder Str. 207 • D - 10405 Berlin Tel: +49 (30) 57700 8234 • Mobile: +49 (170) 77 38 251 • Fax: +49 (30) 57700 8296 www.profitbricks.de • torsten-sven.urbas@profitbricks.com
Sitz der Gesellschaft: Berlin. Registergericht: Amtsgericht Charlottenburg, HRB 125506 B. Geschäftsführer: Andreas Gauger, Achim Weiss.
Please consider the environment before printing this email.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (4)
-
Ben Steele -
Markus Klock -
Tom Laermans -
Torsten-Sven Urbas