Troubleshooting

This guide covers common issues you might encounter with LMDA Composer and how to resolve them.

Connection Issues

No Portals Detected

Symptoms:

• Portal dropdown is empty
• “No portals found” message

Solutions:

1. Log into LogicMonitor
   Open a new tab, navigate to your LogicMonitor portal, and log in with your credentials.

2. Wait for full load
   Ensure the LogicMonitor dashboard fully loads (not just the login page).

3. Return to LMDA Composer
   Click refresh in the Context dropdown.

4. Multiple Portals
   Each portal needs its own logged-in tab. Open separate tabs for each portal.

Tip

Some browsers block cross-tab communication. Try Chrome if using another browser.

Session Expired

Symptoms:

• Portal shows Offline
• Scripts fail with 401 errors
• “Unauthorized” messages

Solutions:

1. Open the LogicMonitor tab

2. Log in again if prompted

3. Return to LMDA Composer

4. Click refresh in Context dropdown

Note

LogicMonitor sessions expire after inactivity. Keep the LM tab active or re-login periodically.

Collector Offline

Symptoms:

• Collector shows offline status
• Cannot select the collector
• Scripts can’t execute

Solutions:

1. Verify in LogicMonitor
   Check collector status in Settings → Collectors

2. Restart Collector
   On the collector server, restart the collector service

3. Check Network
   Verify the collector can reach LogicMonitor and check firewall rules

---

Script Execution Issues

Script Won't Run

Symptoms:

• Run button doesn’t respond
• No output appears
• Execution never starts

Solutions:

• Check Context — Ensure portal is selected, collector is selected, and collector is online
• Check for Running Execution — Only one execution at a time. Cancel current execution first. Look for spinner on Run button.
• Script Errors — Check for syntax errors. Validate script compiles. Review error messages.

Script Times Out

Symptoms:

• Execution runs too long
• Timeout error appears
• Partial output visible

Solutions:

1. Optimize Script
   Reduce execution time, add efficient queries, avoid infinite loops

2. Check Target Device
   Device may be slow to respond, network latency, or overloaded

3. Simplify for Testing
   Test smaller portions, use fewer iterations, add debug output

PowerShell on Linux

Symptoms:

• PowerShell script fails
• Error about script type
• Collector compatibility warning

Solution:

Caution

PowerShell scripts only run on Windows collectors. Select a Windows collector or convert your script to Groovy.

---

Editor Issues

Editor Not Loading

Symptoms:

• Editor area is blank
• No syntax highlighting
• Can’t type in editor

Solutions:

1. Refresh the Page
   Press F5 or Ctrl+R

2. Clear Browser Cache
   Settings → Clear browsing data → Clear cached files

3. Check Extensions
   Other browser extensions may conflict—disable and test

Wrong Syntax Highlighting

Symptoms:

• Colors don’t match language
• Keywords not highlighted
• Editor confused

Solutions:

1. Check Language Setting
   Verify Groovy/PowerShell toggle is correct

2. File Extension
   Opening .ps1 should set PowerShell
   Opening .groovy should set Groovy

3. Switch and Switch Back
   Toggle the language setting to refresh

---

File System Issues

Can't Save Files

Symptoms:

• Save triggers download instead
• “Permission denied” errors
• Save dialog every time

Solutions:

1. Grant Permissions
   Browser may need file access permission. Click “Allow” when prompted. Choose “Edit” not “View”.

2. Brave Browser
   May require enabling File System Access API in brave://flags

3. Vivaldi Browser
   May require enabling File System Access API in vivaldi://extensions

File Handle Lost

Symptoms:

• “File no longer available”
• Can’t save to original location
• Need to Save As

Solutions:

1. Reconnect File
   Use Save As to re-establish handle, select the same file

2. File Was Moved
   Locate file in new location and open again

Drafts Not Recovering

Symptoms:

• No draft recovery prompt
• Lost unsaved work
• Drafts seem missing

Solutions:

1. Check Browser Storage
   Storage may be full—clear some browser data

2. Same Browser Required
   Drafts are per-browser. Use the same browser where you worked.

---

API Explorer Issues

Request Fails

Symptoms:

• 400/401/403/500 errors
• Request doesn’t complete
• Unexpected error messages

Solutions:

• Check Endpoint Path — Verify path is correct. Include required path parameters. Check LogicMonitor API docs.
• Check Request Body — Validate JSON syntax. Include required fields. Check data types.
• Check Permissions — 403 means insufficient permissions. Verify your user role. Contact admin if needed.
• Rate Limiting — 429 means rate limited. Wait before retrying. Reduce request frequency.

Response Not Displaying

Symptoms:

• Response area blank
• JSON not formatted
• Truncated response

Solutions:

1. Large Response
   Very large responses may truncate. Increase response limit in Settings. Use fields parameter to reduce size.

2. Invalid JSON
   Some endpoints return non-JSON. Check Content-Type header.

---

Module Operations

Can't Commit Changes

Symptoms:

• Commit button disabled
• Commit fails with error
• Changes not saved to LM

Solutions:

1. Check Module Binding
   Tab must be bound to a module. Local files can’t commit. Look for link icon on tab.

2. Check Portal Match
   Active portal must match bound portal. Switch portals if needed.

3. Check Permissions
   Need write access to the module. Verify role in LogicMonitor.

4. Validation Errors
   Check for error messages. Fix issues before committing.

Module Not Found

Symptoms:

• “Module not found” error
• Can’t load module script
• Browser shows empty list

Solutions:

1. Check Portal
   Ensure correct portal is selected. Module may be in different portal.

2. Module Deleted
   Module may have been removed. Check in LogicMonitor.

3. Permissions
   May not have access to the module. Check with administrator.

---

Performance Issues

• Slow Performance — Large files may be slow—split into smaller files. Close unused tabs. Close other browser tabs. Disable Minimap in Settings.
• High Memory Usage — Each tab uses memory—close when done. Clear large history. Refresh page periodically (save work first).

---

Getting Help

• Report a Bug — Note the steps to reproduce. Check browser console for errors (F12). Report via LogicMonitor community channels. Include browser and OS version.
• Community Support — Connect with other LogicMonitor users in the community forums for questions and solutions.
• Check for Updates — Ensure you’re running the latest version. Check extension version in Settings. Updates are automatic from the Chrome Web Store.

---

Next Steps

FAQ Frequently asked questions about LMDA Composer.