Hi,Did you run ./discovery.php -u ?If you didn't, that'd explain it. If you did, downgrading will break your database.But if it you had done that and it wasn't working, the likely causes are either database desync or local modifications.The former is pretty difficult and time consuming to track down, and usually involves removing the database and readding all of the devices.Adam.Sent from BlueMailOn 6 Aug 2020, at 19:18, Renuka Arya via observium <observium@observium.org> wrote:Update ; so we rolled back to the current version - O bservium 19.6.9932 and it seems to be fixed now.
However, we noticed two things:1) when we run 'svn update' it never prompts for user/pwd. Please note that we have a valid subscription & user/pwd2) After we run 'svn update' it updates to 20.7.10615 . However, our observium site says : So lookslike just running svn update is not updating to current stable version?
There is a newer revision of Observium available!
Version 20.7.10614 (6th August 2020) is 682 revisions ahead.
On Thu, Aug 6, 2020 at 11:18 AM Renuka Arya < rarya@uchicago.edu> wrote:
Hello Team,
I upgraded my Observium from Observium 19.6.9932 to Observium Professional 20.7.10615 this morning.
I cannot login to the UI now; With my user and admin user it lets me in as unauthenticated, shows broken graphs and kicks me out or would say Remote IP has changed.
and we see this
[2020/08/06 09:47:42 -0500] discovery.php(8383): ====== Schema update 429 -> 430 ==============
[2020/08/06 09:47:42 -0500] discovery.php(8383): Query: ALTER TABLE `autodiscovery` ADD INDEX `remote_hostname_ip` (`poller_id`, `remote_hostname`, `remote_ip`);
[2020/08/06 09:47:42 -0500] discovery.php(8383): Error: (1061) Duplicate key name 'remote_hostname_ip'Any help will be appreciated!Thank you!RegardsRenuka Arya
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium