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. After Cold Reboots, Dirty Shutdown Netxms Not working

After Cold Reboots, Dirty Shutdown Netxms Not working

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 36.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.
  • K
    K
    kiki
    wrote on last edited by
    #1

    After a power failure or dirty shutdown I Have to use run sudo netxmsd-d every time to get it back working. What's the issue?

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      that probably means that you don't have startup script for netxmsd or it is not registered for auto start. You should consult manuals for your OS/distribution on how to enable autostart. IN NetXMS source code ynder contrib/startup you can find startup scripts for various platforms.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • K
        K
        kiki
        wrote on last edited by
        #3

        Start up scripts are there. Like I mentioned, if I perform a clean reboot netxms works properly. Checked log and noted on every dirty shutdown

        [ERROR] Unable to establish connection with database (Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2))
        

        A clean reboot fixes the issue or running netxmsd -d

        1 Reply Last reply
        0
        • K
          K
          kiki
          wrote on last edited by
          #4

          Switching to postgres fixed the issue.

          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