close
keyboard_arrow_left
Table of Contents
- play_arrow Troubleshooting a Problem
- play_arrow Running Health Checks
- play_arrow Increased DNS Requests
- play_arrow JSA System Notifications
- JSA System Notifications
- Disk Usage System Notifications
- Asset Notifications for JSA Appliances
- Automatic Update Notifications for JSA Appliances
- Custom Rules Notifications for JSA Appliances
- Disk Notifications for JSA Appliances
- Event and Flow Notifications for JSA Appliances
- Failure Notifications for JSA Appliances
- Failure Notifications for QRadar Apps
- High Availability Notifications for JSA Appliances
- License Notifications for JSA Appliances
- Limit Notifications for JSA Appliances
- Log and Log Source Notifications for JSA Appliances
- Memory and Backup Notifications for JSA Appliances
- Offense Notifications for JSA Appliances
- Repair Notifications for JSA Appliances
- Vulnerability Scan Notifications for JSA Appliances
list Table of Contents
Resolving Log Source Error After Protocol Update
date_range
27-Mar-21
You must have SSH access and root account credentials.
An error message might appear when you attempt to edit a log source after you upgrade JSA, a Device Support Module (DSM), a protocol, or Vulnerability Information Services (VIS) components. To remove cached files, restart the JSA web service and clear the JSA files from your browser cache.
The following message indicates that the web server didn't restart after JSA was updated:
An error has occurred. Refresh your browser (press
F5) and attempt the action again. If the problem persists, please
contact Juniper Customer Support for assistance.
A file might be cached by JSA web service or your desktop browser. You must restart JSA web service and remove the cached files on your desktop.
