Pandora FMS Community

Update from 161010 to 161107 not working

frossmark · 12 nov 2016, 3:39 · 13 mensajes · 78 visitas

  1. Inicio del debate

    Hi, since quite a while I see there is a new update available, but I am not able to install it over the web-console at all.

    The last version of package installed is: 161010 There is a new version: 161107 Update to the latest version

    results in this:

    The last version of package installed is: 161010 There is a unknown error.

    Now, doing quite some research and creating a SnapShot of CentOS VM today, I tried to install the SP4 build 161107 (server/agent/console) .rpm files, via terminal and GUI - it seems to upgrade to 6.0SP4 but I still have the Update manager informing me I am not on the latest build 161107 (the Diagnose Info in the web tells me otherwise), now after installing the RPMs and seeing SP4 everywhere (footer/login/debug info) I can actually install the update, but this seems to revert me back to SP3. The whole behavior is very weird and I rolled back a few times and tried different approaches. Actually, in the end I rolled back again and decided I have to ask the community about it, since I am pretty much stuck here. Any input is more than welcome.

  2. Same here. Stuck on 161010.

  3. Hello kaitwo/frossmark, I'd suggest you to install the packages manually by using the packages, and then see if the warning message persists. In that case, could you execute these queries and report here what they display:   select * from tupdate_settings where `key` = 'current_update'   select * from tconfig where id_config > 7 AND id_config < 11    //Basically I want to get the db_scheme_first_version, db_scheme_version and db_scheme_build results Kind regards, Antonio.

  4. Hi Antonio, Right now I get those results: current_update: 412 db_scheme_first_version: 6.0dev db_scheme_version: 6.0RC1 dc_scheme_build: PD150908 With doing the updates manually, do you mean installing RPM's directly on the system again? As mentioned, after that I still have an Update-Notification (even though I am on SP4), once I apply the update I am on SP3... messing supposedly everything up.

  5. Hi Antonio/frossmark, Once updated to 6.0SP4: current_update: 412 db_scheme_version: 6.0dev db_scheme_build: PD150624 show_unknown: 0 Updating from 161107 to 161114 = Fallo copiando los ficheros Manually updating console, via RPM's, shows 161114 is still pending. Regards.

  6. Yes, I mean manually installing the rpms. Don't worry about getting everything messed up, by using the rpm installation you are guaranteed to have the latest version with the updated console code, but I guess there is some bug that is not updating the database fields with the "current version" properly, that's why I wanted to know if there was a difference on those fields before and after applying the rpms. Naturally if you roll back to the SP3 the console code will again be updated to the previous version. Kind regards, Antonio.

  7. Okay here is what I just did:

    installed the RPMs I had on hand: 161107

    restarted the service

    Console footer showed SP4 161107

    of course newer update 161114 was available

    installed it via console

    Console footer showed SP3 ??????? and 161010!!!!

    - forgot earlier, but did SQL queries now... no change

    force installed 161107 RPMs again

    restarted service

    no direct change - console/web console did not show available updates

    installed RPMs for 161114

    restarted service

    Console footer showes SP4 161114

    - SQL queries - no change

    The SQL still shows: current_update 412 db_scheme_first_version 6.0dev db_scheme_version 6.0RC1 db_scheme_build PD150908 This does not make any sense to me. Is there an update script the should have been executed or I even might execute manually?? I am pretty sure once the next update comes out over the console, the whole thing will again roll back... that's an horrible situation and pretty much going in circles..

  8. Can you please attach the output of the following query?  

    select * from tconfig where token = 'url_update_manager'
    

    Recently we've detected some issues regarding Update Manager misconfiguration, due to updates not modifying correctly this value, and there might be the permanent fix. Kind regards, Antonio.

  9. Ok, please update that field substituting "firefly" for "licensing". You can do it on the update manager options or on the database. The complete url should be:

    https://licensing.artica.es/pandoraupdate6/server.php
    

    Then try to apply the updates, and watch that parameter after every update, the problem may be there, if you see that it changes again to "firefly", please say it on this post so we can fix it internally on the following update. Thanks! Kind regards, Antonio.

  10. Hi, Antonio: Same as frossmark again. url_update_manager doesn't changes between updates. Keeps on "licensing". Kind regards.

  11. Changed it - but I will need to wait for the next update to see if everything is fine. Thank you for the help!

  12. Ok, let me know if it gets applying the updates correctly from now on. Kind regards, Antonio.

Entra en tu cuenta para publicar.