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

H

Hybo

@Hybo
Unfollow Follow
About
Posts
1
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Cluster mode - Database is already locked by another NetXMS server instance
    H Hybo
    Support

    Hi,

    I have a problem with my NetXMS high availability solution. I have two nodes called server1 (172.16.103.16) and server2 (172.16.103.17) with pacemaker, corosync and DRBD. Database engine is PostgreSQL, with database on shared disk.

    When I destroy server1 (such as switching power off ), then the NetXMS on server2 does not start and writes into the log:

    [20-Nov-2012 17:49:16] Log file opened
    [20-Nov-2012 17:49:16] Platform subagent "/opt/NetXMS/lib/libnsm_linux.so" successfully loaded
    [20-Nov-2012 17:49:16] Database driver "/opt/NetXMS/lib/libnxddr_pgsql.so" loaded and initialized successfully
    [20-Nov-2012 17:49:16] Database is already locked by another NetXMS server instance (IP address: 172.16.103.16, machine info: server1 Linux Release 2.6.34.7-0.7-xen)
    

    database contents:

    ServerID                          | 451B2B5D9290AB50                                    |          0 |                   1
    DBLockPID                         | 8375                                                |          0 |                   0
    DBLockInfo                        | server1 Linux Release 2.6.34.7-0.7-xen            |          0 |                   0
    DBLockStatus                      | 172.16.103.16                                       |          0 |                   1
    

    Is there any solution other than "nxdbmgr check" before starting NetXMS on server2? Because this may cause some problem in my HA solution.

    Thanks,
    Hybo

  • 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