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. Event Script issues

Event Script issues

Scheduled Pinned Locked Moved Support
2 Posts 1 Posters 26.9k 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.
  • W
    W
    Victor Wiebe
    wrote on last edited by
    #1

    I'm using the nxevent binary to insert a custom alert onto the console. Everything looks like it really should be working. The event shows up in the Event Monitor but an alarm does not show up in the Alarm Browser. I'm running this command manually:

    /usr/bin/nxevent -u admin -P adminPassword 10.42.1.31 '100002' 'clientName' 'businessUnit' 'ALERT' 'Alarm ID 1890000  Alarm goes here!' 'Critical' 'Custom.alarm.key'

    All the information and command line arguments are correct. The event processing policy - id 100002 - calls a script named NXEvent::Raw.

    I see these entries in the netxmsd.log file when I enter the command:

    [13-Aug-2015 15:19:26.613] [DEBUG] [CLSN-1] RecvNXCPMessageEx failed (0)
    [13-Aug-2015 15:19:26.613] [DEBUG] *actions* Executing action 3 (NXEVENT::Raw) of type NXSL SCRIPT
    [13-Aug-2015 15:19:26.613] [DEBUG] *actions* Executing NXSL script "NXEVENT::Raw"
    [13-Aug-2015 15:19:26.614] [DEBUG] ExecuteActionScript(): Cannot find script NXEVENT::Raw

    NXEVENT::Raw is certainly there. Is there anything else I can do to troubleshoot?

    1 Reply Last reply
    0
    • W
      W
      Victor Wiebe
      wrote on last edited by
      #2

      So I did some further digging and discovered that the issue was of my own doing. I had a syntax error in the script. Correcting that resolved my own problem.

      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