Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-1133

Manual override of location does not then apply the location information in config.php

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      devices with manually set locations are not then correctly grouped using the location details loaded manually into config.php

      Attachments

        Activity

          [OBS-1133] Manual override of location does not then apply the location information in config.php
          landy Mike Stupalov made changes -
          Workflow Original: classic default workflow [ 12018 ] New: Observium workflow [ 14371 ]
          landy Mike Stupalov made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          As of 0.15.1.6185, it's working fine for me.

          Thank you!

          rjk Richard Kuhns added a comment - As of 0.15.1.6185, it's working fine for me. Thank you!
          landy Mike Stupalov made changes -
          Assignee Original: Adam Armstrong [ adama ] New: Mike Stupalov [ landy ]

          This problem with auto enabled "manual" flag, should be fixed in r6179.
          Geolocation feature is updated at the end of December.

          If after update (svn up) and upgrade DB (./discovery.php -u) not fixed, try correct manually:
          1. uncheck manual flag and save changes
          2. wait next poll when geolocation updated
          3. send new screenshot if geolocation still not correct

          landy Mike Stupalov added a comment - This problem with auto enabled "manual" flag, should be fixed in r6179. Geolocation feature is updated at the end of December. If after update (svn up) and upgrade DB (./discovery.php -u) not fixed, try correct manually: 1. uncheck manual flag and save changes 2. wait next poll when geolocation updated 3. send new screenshot if geolocation still not correct

          I have what seems to be the same problem.

          In the event log I find an entry for mulberry-sw1:

          2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) ->
          [40.420760, -86.890249] United States (Country), Indiana (State),
          Tippecanoe County (County), Lafayette (City)

          This is just wrong. The actual location string for this device (which
          has been untouched since it worked correctly for the community version)
          shows that it's in Mulberry, Indiana. That's even in a different county.

          I've attached a screenshot.

          Observium 0.15.1.6165

          rjk Richard Kuhns added a comment - I have what seems to be the same problem. In the event log I find an entry for mulberry-sw1: 2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City) This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county. I've attached a screenshot. Observium 0.15.1.6165
          rjk Richard Kuhns made changes -
          Attachment New: mulberry.jpg [ 12237 ]

          Screenshot of geolocation page for mulberry-sw1.
          On the map it shows up in Lafayette, IN.

          rjk Richard Kuhns added a comment - Screenshot of geolocation page for mulberry-sw1. On the map it shows up in Lafayette, IN.

          There zero useful info..
          observium version, config, locations..

          landy Mike Stupalov added a comment - There zero useful info.. observium version, config, locations..

          People

            landy Mike Stupalov
            robert.hatch Robert Hatch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: