Ad Widget

Collapse

Unable to delete/update hosts

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • mortenatstatkart
    Junior Member
    • Nov 2022
    • 12

    #1

    Unable to delete/update hosts

    After updating from Zabbix 7.2.8 to 7.4 I am locked out of deleting hosts that have a discovery job attached. Ive tried only removing the template, and get the same error.

    Cannot update host
    • pg_query(): Query failed: ERROR: permission denied for table lld_macro_export [zabbix.php:17 → require_once() → ZBase->run() → ZBase->processRequest() → CController->run() → CControllerHostUpdate->doAction() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → CHost->update() → CHost->updateForce() → CHostGeneral->updateTemplates() → CHostGeneral::unlinkTemplatesObjects() → CDiscoveryRule::clearTemplateObjects() → CDiscoveryRule::deleteForce() → DB::delete() → DBexecute() → pg_query() in include/db.inc.php:255]
    • Error in query [DELETE FROM lld_macro_export WHERE (itemid IN ('197632','197633','197634','197635'))] [ERROR: permission denied for table lld_macro_export]
    • SQL statement execution has failed "DELETE FROM lld_macro_export WHERE (itemid IN ('197632','197633','197634','197635'))"
    Does anyone have a tip to what causes this, and how to fix it.
    I tried giving delete rights on the table specified to the db-user, but still no solution.
    Last edited by mortenatstatkart; 06-08-2025, 09:16.
  • Answer selected by mortenatstatkart at 20-08-2025, 07:37.
    mortenatstatkart
    Junior Member
    • Nov 2022
    • 12

    Incase anyone wants to know the results. It appears there was another username used when creating the tables in question. When this user/owner got the right rights, everything went back to normal.

    Comment

    • mortenatstatkart
      Junior Member
      • Nov 2022
      • 12

      #2
      Anybody had this issue? It seems I cannot add the SAML setting aswell.

      Cannot update authentication
      • pg_query(): Query failed: ERROR: permission denied for table settings [zabbix.php:17 → require_once() → ZBase->run() → ZBase->processRequest() → CController->run() → CControllerAuthenticationUpdate->doAction() → CControllerAuthenticationUpdate->processGeneralAuthenticationSettings() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → CAuthentication->update() → CApiSettingsHelper::updateParameters() → DB::update() → DBexecute() → pg_query() in include/db.inc.php:255]
      • Error in query [UPDATE settings SET value_int='1' WHERE name='saml_auth_enabled'] [ERROR: permission denied for table settings]
      • SQL statement execution has failed "UPDATE settings SET value_int='1' WHERE name='saml_auth_enabled'".

      Comment

      • mortenatstatkart
        Junior Member
        • Nov 2022
        • 12

        #3
        I feel there is something wrong with the database. Does anyone have issues with the database simular to this?

        Comment

        • cyber
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2006
          • 4807

          #4
          yea.. it looks like permission issues... Whos the tables owner ? Common owner is user zabbix who has create db rights... Any other user should be in same role..

          Comment

          • mortenatstatkart
            Junior Member
            • Nov 2022
            • 12

            #5
            the user that connects from Zabbix to the database has all the rights (Dadrtwx). it is also the owner.
            This is the user I have specified in the zabbix-server.conf file.
            Last edited by mortenatstatkart; 19-08-2025, 07:47.

            Comment

            • mortenatstatkart
              Junior Member
              • Nov 2022
              • 12

              #6
              Incase anyone wants to know the results. It appears there was another username used when creating the tables in question. When this user/owner got the right rights, everything went back to normal.

              Comment

              Working...