Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Database is locked for report server

Database is locked for report server

Scheduled Pinned Locked Moved Support
10 Posts 3 Posters 79.3k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    saksham.adyso
    wrote on last edited by
    #1

    If I install the report service on a separate server (a different server than the one on which the netxms server is installed), the event "Database is already locked by another NetXMS server instance (IP address: 192.168.0.254, machine info: nxserver Windows Server 2012 Build 9200)" is written to the netxmsd.log. NetXMS server and report server use the same login. I have also tried separate logins, the database always locks up.

    1 Reply Last reply
    0
    • A
      A
      Alex Kirhenshtein
      wrote on last edited by
      #2

      You are running second instance of the netxmsd. Only once instance of the netxmsd should access database at the same time.

      If you want to keep reporting server separate, change parameter ReportingServer.Hostname to remote IP of the reporting server.

      1 Reply Last reply
      0
      • S
        S
        saksham.adyso
        wrote on last edited by
        #3

        When installing a standalone report server, however, the Base component (and therefore netxmsd) is checked and cannot be unchecked and is therefore mandatory.
        ReportingServer.Hostname is set to remote report server correctly.
        For the report server to work, should I disable netxmsd and leave only the report service?

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          Normally reporting server is installed on the same system as netxms server itself. But theoretically yes, you can disable netxms server service and have only reporing service enabled.

          1 Reply Last reply
          0
          • S
            S
            saksham.adyso
            wrote on last edited by
            #5

            I wanted to try the scenario described in the documentation, where it says about the possibility of a separate report server. Unfortunately the installer contains another issue (another one I described here a here). It lists the base component as mandatory and in fact it is not necessary to install it for the report server.
            It is worth considering correcting this error.

            1 Reply Last reply
            0
            • A
              A
              Alex Kirhenshtein
              wrote on last edited by
              #6

              Just install full package, then disable “netxms core” service in service manager

              1 Reply Last reply
              0
              • S
                S
                saksham.adyso
                wrote on last edited by
                #7

                And also remove any unnecessary firewall rules. Would prefer an installer modification that would not put the user in this situation.

                1 Reply Last reply
                0
                • A
                  A
                  Alex Kirhenshtein
                  wrote on last edited by
                  #8

                  Well, you can send PR on the GitHub

                  1 Reply Last reply
                  0
                  • S
                    S
                    saksham.adyso
                    wrote on last edited by
                    #9

                    How to configure the ListenAddress parameter for nxreportd? If I run the report on a standalone server, by default the binding is set to loopback and thus it is not possible to connect to the service from a remote server.

                    1 Reply Last reply
                    0
                    • F
                      F
                      Filipp Sudanov
                      wrote on last edited by
                      #10

                      You can create nxreportd.properties file in C:\NetXMS\etc\nxreportd folder. In this file you can specify bind address:

                      nxreportd.bindAddress=1.2.3.4

                      setting it to * or 0.0.0.0 will bind to all available interfaces.

                      1 Reply Last reply
                      0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      Powered by NodeBB Contributors
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups