HAR stands for HTTP Archive Record and is a JSON structured file containing network traffic information about a browser’s interactions with a server as well as the content on a webpage.
When HAR files are useful
Performance issues: slow page loading, timeouts when performing tasks, time spent negotiating proxy connections, time spent issuing requests, time spent receiving the response data, DNS lookups, and others
Page Rendering: incorrectly formatted pages or missing information
How to Capture HAR files
Prior to performing a capture open an Incognito window or tab to eliminate capturing decrypted request-response communications or cookie from unrelated sites or events.
Chrome
Access Menu > More tools > Developer tools (CTRL+SHIFT+I or F12)
Select the Network tab, if not already selected.
Ensure that the Preserve log box is checked.
Check mark the Disable cache box.
Reload or recreate the activity you wish to capture.
Click the Download icon.
Firefox
Access Menu > More tools > Web Developer Tools (CTRL+SHIFT+I or F12)
Select the Network tab, if not already selected.
Ensure that the Persist Logs box is checked.
Check mark the Disable cache box.
Reload or recreate the activity you wish to capture.
The Disk Space Use% for the partition mounted as /smartvue should not reach 100%. If it does odd behavior too include loss of live or recorded video may occur. Further troubleshooting should help decide if the issue is related to a failed or failing hard drive or a corrupted database.
Product
Cloudvue Gateway
Steps to Reproduce
Access the Cloudvue Gateway via Cloudvue Manager
Expand Disk Space
Check the Use% for the partition Mounted on /smartvue
Expected Results
smartvue Use% should be less than 100%
Actual Results
smartvue Use% is 100%
Solution
Escalate to L3 for further troubleshooting or to setup a repair RMA.
Troubleshooting
Attempt to gain SSH access to the NVR either by tunneling or arranging a remote session for local ssh access. Review the syslogs to see if they give any clues.
Look in the syslog files in /var/log for something similar to
Jul 13 07:17:32 SMV-K1 /etc/init.d/mysql[18996]: error: ‘Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2)’
Also check the /var/log/mysql/error.log for entries simalr to:
230713 13:17:39 [ERROR] mysqld got signal 6 ;
Cloudvue Warranty
Cloudvue Gateway and C2C cameras have a 3-year warranty. Check the build date in Cloudvue Manager to figure out if a repair RMA is In or Out of Warranty.
Once updated Illustra camera firmware cannot be downgraded.
Product
Illustra
Notice
Previous versions of Illustra camera firmware are not available (nonnegotiable). Therefore, downgrading or rolling back to a previous firmware version should not be recommended or suggested as a troubleshooting step.
If there appears to be a compatibility issue and the following conditions are met, then the case should be escalated to L3 so they can work with engineering and product management towards resolution.
Camera is on the most recent version of firmware
exacqVision Server software is on the latest release
Troubleshooting notification e-mail server configuration settings when e-mail message profile tests fail.
Product
ExacqVision Client
Solution
If the profile test fails, review the exacqVision Verbose System Logs (Configuration > YOURSERVER > Systems Logs tab) for information about the cause. Pro Tip: Filter the displayed search results for entries relevant to notifications by typing “notifypi” in the filter box.
Here are some common causes including coresponding log entries.
Invalid E-mail Server Password
Invalid E-mail Server Username
Invalid E-mail Server Port
Invalid E-mail Server Security Type – STARTTLS
Invalid E-mail Server Security Type – Default
Invalid E-mail Server Outgoing Mail Server (SMTP) Address
We will never accept “It doesn’t work” as a valid reason to replace a machine. The purpose of this guide is to help determine why a unit “does not work.”
Some technical knowledge is assumed with this guide.
Possible causes:
Power Supply
Internal Components and Cabling
POST
Section 1
Power Supply
If the unit does not power on at all (no lights, no fans) when plugged in and the front power button is pushed:
Make sure the power cable plugged into both the wall outlet (or UPS) and the unit securely.
Make sure you push the power button on the front of the machine. You may need to open the door on the front of the machine to see the black rocker switch.
If the unit still does not turn on, try a different outlet (or known working outlet on the UPS) and/or a known working power cable.
If the problem persists and we get no activity within the machine (no lights, no fans), it is plausible the PSU in the unit is non-functional.
Do not stop here if the machine is right out of the box! Continue with the following steps make sure it is not related to some other component!
If the unit powers on for a few seconds and then powers off when plugged in:
This is a normal power-on procedure for the motherboard. In addition, you need to push the power button on the front of the machine.
If the rocker/power button on the front of the machine is pushed, but the unit still does not come on, continue on with the guide.
Section 2
Internal Components and Cabling
If the unit still does not power on:
Disconnect power to the machine.
Start removing the top cover to the machine by unscrewing the screws on the sides and back of the case.
The top cover should slide off fairly easily. There is a sticker on the underside of the top cover that has the motherboard cabling information.
Locate the power supply and follow the cables to where they connect to the motherboard.
Unseat and reseat the connectors to the motherboard coming from the power supply. Most connectors will have a clip to keep the plastic parts in place, but there will be a tab to pinch to unseat the connector.
Pinch the tabs on the connectors to unseat them. Push the connectors back down (you will feel the tab snap into place) to reseat.
From the front of the machine, follow the cables coming from the rocker/power switch to the motherboard.
Make sure this cable (red/black) is plugged in to the proper pins (ON/OFF) on the motherboard (follow the diagram on the underside of the top cover).
Reseat the RAM on the system.
Connect power to the machine and push the power button on the front of the machine.
See if any of the fans spin or any internal lights come on — specifically, the fan on top of the CPU and the green power indicator light on the motherboard.
If you still do not see any indicator lights on or system fans spinning, it is most likely a non-functional power supply.
Create an RMA for the part.
If the unit begins to boot, but does not pass POST (Power On Self Test) or load the OS, continue on.
If the unit powers on, passes POST and loads the OS, replace the top cover on the machine and proceed with installation.
Section 3
POST
If the unit does not pass POST:
By default, beep codes are not disabled on the motherboard. So, if the unit does not pass POST, some beep code should sound indicating what the problem component is.
If you cannot determine the problem from the beep code, continue.
POST requires a CPU (not overheating) and video controller, and RAM must be present and accessible.
Disconnect power from the system.
CPU: Make sure the CPU fan is secure and has its power cable connected securely to the motherboard.
RAM: Make sure RAM is seated properly and secure, and reseat if necessary.
Video Controller: This is integrated into the motherboard, but if there are multiple video cards or analog boards, remove them before trying to power the unit back on.
HDD: Ensure cabling (power and SATA cable) to hard drives is both present and secure, reseating/attaching if necessary.
Analog Riser Card: Make sure the Molex power connector is connected to the riser card (if appicable).
If all components are secure and extra components (video cards/analog boards) are removed, connect power to the machine and turn it on.
Possible outcomes:
The unit powers on and passes POST: This would inidcate there is an issue with one or more of the expansion cards/analog boards. Power the unit down via the OS and try to reconnect one card at a time with a reboot to find the culprit and create an RMA for the part.
The unit powers on, but does not pass POST: This would inidicate a possible motherboard issue. If you arrive at this point, and have done all the previous steps, get approval from a manager and have the unit sent in for repair.
An iSCSI configuration could be corrupt if the following are true:
Linux-based exacqVision Server
iSCSI used as extended storage
Extended Storage portal status displayed in exacqVision Client as anything other than OK
Server logs contain the following messages:
8/21/2014 1:48:12 PM ArchivePI Warning Errors from /usr/local/exacq/server/scripts/iscsiprep.py addportal -portaladdr 10.16.1.106 -portalport 3260 8/21/2014 1:48:12 PM ArchivePI Warning Error: while running command iscsiadm -m discovery -t sendtargets -p 10.16.1.106:3260 -o new. Exit code=255 8/21/2014 1:48:12 PM ArchivePI Warning iscsiadm: Cannot resolve host . getaddrinfo error: [Name or service not known] 8/21/2014 1:48:12 PM ArchivePI Warning iscsiadm: cannot resolve host name 8/21/2014 1:48:12 PM ArchivePI Warning iscsiadm: Could not perform SendTargets disco
Perform the following steps to resolve the possible corruption:
In exacqVision Client, delete the affected portal from the Extended Storage tab on the Storage page.
Open Terminal.
Execute command sudo su.
Execute command cd /etc/iscsi/send_targets.
Execute command ls -l
Note the directories listed from the ls command and the portal’s IP address in the name of a directory (such as 10.16.1.106,3260).
Execute command cd 10.16.1.106,3260 (using the address from the previous step).
Execute command ls -l.
Open the file st_config for editing. It should look like this (using the portal’s IP address and port as appropriate):
# BEGIN RECORD 2.0-871 discovery.startup = manual discovery.type = sendtargets discovery.sendtargets.address = 10.16.1.106 discovery.sendtargets.port = 3260 discovery.sendtargets.auth.authmethod = None discovery.sendtargets.timeo.login_timeout = 15 discovery.sendtargets.reopen_max = 5 discovery.sendtargets.timeo.auth_timeout = 45 discovery.sendtargets.timeo.active_timeout = 30 discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768 # END RECORD
Save changes to the st_config file.
Execute command cd ~
Execute command iscsiadm -m discovery -p 10.16.1.106 -o delete (use the portal’s IP address; this command deletes the portal from the iscsiadm configuration database).
Execute command iscsiadm -m discovery (the affected portal should NOT be included in the output).
In exacqVision Client, re-create the Extended Storage configuration for the portal. It should connect with no problem and report a status of OK.
When a Server’s configuration is updated excessively, the Client “flickers” repeatedly. It will be helpful to know which plugin’s config is being updated so you know where to focus your troubleshooting.
Run the following commands, depending on your OS environment to see which plugin’s xml was updated most recently.
