Symptoms
- The user field in the notification method does not allow the '@' symbol.
- Affects opsview 6.8.x +
Cause: The Implementation of UTF-8 in 6.8.x
Known issue OP-60056
Our system sets the UID to be the user's email address. The user field in the notification method doesn't allow the '@' symbol.
Note: Our docs state to use the username and not the email address.
Solution: Constraints Fix
Carry out the following steps on your opsview master (orchestrator) to resolve this issue.
This patch will resolve the field validation issues within the Push notification method.
1. Place the 2 JSON files attached on your system, say /tmp/
2. as root
cd /opt/opsview/corelibs/lib/
mv constraints.json constraints.json.BAK
mv constraints_unhashed.json constraints_unhashed.json.BAK
cp /tmp/constraints.json .
cp /tmp/constraints_unhashed.json .
chmod 440 constraints.json constraints_unhashed.json
chown root.opsview constraints.json constraints_unhashed.json
/opt/opsview/watchdog/bin/opsview-monit restart opsview-web
3. reload your web browser
4. Now you can go ahead with the steps in our documentation, you should now be able to enter a username containing the @ symbol, and the proxy field, if required, can now be left blank.
Take a snapshot/backup before doing these changes, as this is always a good idea, good luck.
If you have any issues
- Please contact our team via the chat service box available on any of our websites or via email to support@itrsgroup.com
Make sure you provide us with:
- ANY LOG FILE OR DIAGNOSTIC DATA
- ANY SCREENSHOT
- ANY VENDOR/VERSION etc
-
Tags:
- Opsview
- opsview
Comments
0 comments
Please sign in to leave a comment.