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. Connection Refused, service failed

Connection Refused, service failed

Scheduled Pinned Locked Moved Support
2 Posts 1 Posters 29.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.
  • C
    C
    CMelchior
    wrote on last edited by
    #1

    Need a little help troubleshooting my test NetXMS system. I am unable to log into the web or console and get a connection refused error.
    Systemctl status shows the following:

     netxmsd.service - NetXMS Server
       Loaded: loaded (/lib/systemd/system/netxmsd.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Thu 2020-10-22 13:13:19 CDT; 38s ago
      Process: 869 ExecStart=/usr/bin/netxmsd -d (code=exited, status=0/SUCCESS)
     Main PID: 870 (code=exited, status=3)
    
    Oct 22 13:13:19 netxms-test systemd[1]: Starting NetXMS Server...
    Oct 22 13:13:19 netxms-test systemd[1]: Started NetXMS Server.
    Oct 22 13:13:19 netxms-test systemd[1]: netxmsd.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
    Oct 22 13:13:19 netxms-test systemd[1]: netxmsd.service: Unit entered failed state.
    Oct 22 13:13:19 netxms-test systemd[1]: netxmsd.service: Failed with result 'exit-code'.
    

    Tried upgrading all packages, and restarting the service but get the same errors.
    This is running on Debian 9, installed a couple months ago per the install instructions on the Wiki.

    Thanks.

    1 Reply Last reply
    0
    • C
      C
      CMelchior
      wrote on last edited by
      #2

      OK well I solved my own problem...

      I checked the netxmsd log at /var/log/netxmsd and the latest entries indicated that the DB was locked by a different IP address. I then realized that my test server had shifted IP addresses, I forgot to set a static IP on this VM when I built it...

      so I forced the DB unlock "nxdbmgr unlock" and rebooted the machine.

      The service started and I'm back in business.

      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