Tag: Guest

Categories
Knowledge Support Support exacqVision Client Categories Products

Default Windows User Accounts on Exacq Systems

When setting up a new Exacq system, the out-of-box experience will prompt you to create a default operating system account. This account will be given administrative privileges.

Additional user accounts may be created using the Kiosk scripts available on the Desktop. Kiosk user accounts have restricted privileges. The Kiosk account is blocked from all operating system functions and the user can only close the exacqVision Client and log out of the operating system account. This prevents the Kiosk user from shutting down the system, opening web browsers, or from starting and installing other applications while logged in as the Kiosk user. You are given the option to automatically log into the system with the Kiosk user account during creation of the account.

If you license exacqVision software and install it on your own computer, this script is not available, and you are responsible for configuring all operating system accounts and privileges.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Starting iSCSI on Startup with Linux Systems

After you reach the point where everything is logged in (you are able to type iscsiadm –m session and get output), following is the generic syntax:

iscsiadm -m node -T <targetname> -p <ip:port> –op update -n node.conn[0].startup -v automatic

<br>

The parameters between < and > are substitutions.

The syntax for persistent binding devices discovered on an internal connection under Ubuntu would look like this:

iscsiadm -m node -p 172.16.16.1 –op update -n node.conn[0].startup -v automatic

<br>

Here’s a more complete breakout, with examples from another system with two volumes (vol1-test and vol2-test), each with two connection paths, to log in to:

root@xxx:/etc/iscsi# iscsiadm -m node -l

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.3.15.102,3260]

<br>

The following is used for persistent binding to just the first volume, by target name:

# iscsiadm -m node -T iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a –op update -n node.conn[0].startup -v automatic

root@xxx:/etc/iscsi# /etc/init.d/open-iscsi restart

 * Disconnecting iSCSI targets                                                  Logout session [sid: 1, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Logout session [sid: 2, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

Logout session [sid: 3, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.4.15.164,3260]

Logout session [sid: 4, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.3.15.102,3260]

                                                                         [ OK ]

 * Stopping iSCSI initiator service                                      [ OK ]

 * Starting iSCSI initiator service iscsid                               [ OK ]

 * Setting up iSCSI targets

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

                                                                         [ OK ]

<br>

NOTE: This just pulls in that target (vol1-test). Further, we could add by –p 10.3.15.164 in a second operation and pull in one other connection that the above did not add, for vol2-test on an IP basis (or, if this were the first operation, it would have added one connection to each volume). To turn off automatic binding for a given connection, you would use –v manual instead of -v automatic.

<br>

Also, none of this takes effect until the iSCSI daemon is restarted.

<br>

Starting-iSCSI-on-Startup-with-Linux-Systems.pdf
Categories
Knowledge Support Support Categories Products exacqVision Hardware

Enumerating more than Four Serial Ports in Linux

If a system is built with the Radisys motherboard or has two or more eDVR boards, there are more then four serial ports. However, Ubuntu 8.04 enumerates only four serial ports by default. To change the number of serial ports enumerated, complete the following steps:

<br>

  1. Edit menu.lst by typing sudo nano /boot/grub/menu.lst
  2. Find the line that starts with # kopt= and ends with ro and add the following to the end: 8250.nr_uarts=16
  3. Save the file by pressing Ctrl-o and then Enter.
  4. Exit by pressing Ctrl-x.
  5. Execute the following command to refresh grub: sudo update-grub

<br>

NOTE: The first character in “lst” is the lowercase letter L and not the number 1.

<br>

Enumerating-more-than-Four-Serial-Ports-in-Linux.pdf
Categories
Knowledge Support Support exacqVision Client Categories Products

Panasonic NW502 JPEG versus H.264 Issue

If you connect to a Panasonic NW502 camera and the software displays JPEG while MPEG-4 is greyed out, you must enable H.264 video encoding. To do this, browse to the NW502 camera configurator and open the Image page. Then change the Video Encoding Format from MPEG-4 to H.264.

<br>

Panasonic-NW502-JPEG-versus-H.264-Issue.pdf

Categories
Knowledge Support Support exacqVision Client Categories Products

Supported exacqVision Client Languages

The following languages are supported in exacqVision Client as of November 11, 2009:

<br>

NOTE: To view the client software in the target language, simply change the Windows language and then run the client software.

<br>

Afrikaans
Arabic
Chinese
Danish
Dutch/Flemish
French
French Canadian
Greek
Hebrew
Hungarian
Japanese
Korean
Norwegian (Bokmål and Nynorsk)
Polish
Portuguese
Russian
Serbian
Slovak
Slovene
Spanish (Castilian)
Spanish (Venezuelan)
Spanish (Chilean)
Swedish

<br>

Supported-exacqVision-Client-Languages.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Locking Down Linux GRUB (Legacy)

To lock down Linux GRUB, complete the following steps:

<br>

  1. Download the attachment lock-grub.sh.
  2. Make it executable: chmod +x lock-grub.sh
  3. Execute the script with your desired password: sudo ./lock-grub.sh admin256

<br>

This puts a password entry in /boot/grub/menu.lst as an md5 hash. If you want to change it after running this script, replace the hash with one created with grub-md5-crypt.

<br>

To view code follow the link: http://exacq-staging.instil.co/#/file-manager/1b63f3e9-b6e5-48be-9cd2-14b4a1ad2fad/kb-00597-597-210212

<br>

Categories
Knowledge Support Support Categories Products exacqVision Hardware

Disabling Automatic Login in Linux

To disable automatic login on Linux, complete the following steps:

  1. Log in to the Admin account.
  2. Run Start -> System -> Administration -> Login Window.
  3. After you enter the admin password, the Login Window Preferences dialog appears. On the Security tab, deselect Enable Automatic Login. You can also change the User to admin if you want to always login as admin; however, this is not recommended for security reasons.

<br>

Disabling-Automatic-Login-in-Linux.pdf
Categories
Knowledge Support Support Categories exacqVision Webservice Products

Can the Web Server run on an Exacq EL NVR system?

Yes, exacqVision EL supports a Web Server used to provide the mobile device video access. The Web Server is not installed on EL by default because if it runs simultaneously with exacqVision Client on the EL hardware, performance of both the local client and the Web Server could be noticeably slower (this is the tradeoff for the low power consumption and reduced cost of the Intel Atom processor). The loading introduced by the Web Server is roughly equal to the client. Remote clients connected to the exacqVision Server do not introduce significant CPU loading.

<br>

On exacqVision ELP systems, the Intel Celeron processor can run exacqVision Client and Web Server simultaneously. exacqVision Client performance is still dependent on the processor. See Client Workstation Hardware Requirements on this page for more information.

<br>

The installation of the Web Service is very easy and no different than for any other Ubuntu Linux-based system. The Web Service installer is available at https://exacq.com/support/downloads.php.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products exacqVision Hardware

Manually Checking a Drive for Errors in Linux

Run fsck

On Linux systems, if a disk encounters a filesystem error, the physical drive may still be good but require a file system consistency check. Perform the following steps to attempt to correct this.

If the affected volume is a video storage volume:

  1. Stop the ExacqVision server service. Open a Terminal window and enter:
    sudo service edvrserver stop<br><br>
  2. Unmount the volume:
    sudo umount /mnt/edvr/X

    Replace the ‘X’ with your volume number.
    Example: If you have a write error on /mnt/edvr/2, you would enter:
    sudo umount /mnt/edvr/2

    NOTE: If this command fails, see Appendix below.<br><br>
  3. Run fsck on this volume, again replacing ‘X’ with the volume number:
    sudo fsck -yv /mnt/edvr/X

    This command will tell the system to automatically attempt to fix any issues it encounters. This may take minutes or several hours depending on the number of filesystem errors and the size of the volume. When completed, the Terminal will return to a prompt awaiting a new command. <br><br>
  4. When you have run fsck on all the affected storage volumes, reboot the system by entering:
    reboot

    OR

    Return to the Desktop and use the power icon to restart the machine. The drives will remount upon boot up.<br>br>

<br>

Appendix

If drive fails to unmount, you will need to open the fstab file and comment out the mount point of the drive in question.
sudo gedit /etc/fstab

  1. You will need to place a ‘#‘ character to the left of ‘Label=/mnt/edvr/X’
  2. Save
  3. Reboot the machine.
  4. The drive that was commented out should not be mounted at this point.

Continue with step 3 above.
Reminder: Do not forget to re-edit the fstab after the fsck is finished and remove the # you added.

<br>

What does fsck do?

The fsck command performs a consistency check and attempts to repair the filesystem from errors.

What causes filesystem errors?

When system processes or user activity require saving data or making changes to the filesystem, that data is first written to a buffer in memory (RAM). The system periodically moves the data waiting in the buffer to the hard disk. Therefore, at any moment, there is a difference between file changes waiting to be written to disk and what exists on the disks.

Filesystem errors and inconsistencies can develop due to hardware degradation, system halts, or unclean shutdowns. Sudden power loss and forced shutdowns occurring before the changes in the buffer are moved to permanent disk storage.

Components checked by fsck

Inodes
Inodes contain metadata about a file, which includes information like: whether the file is read/write or read-only, the type of file, the user ID of the file owner, file creation and modification date and time, and the number of bytes in the file.

Data Blocks
These contain the data that actually makes up the file.

Superblocks
The superblock contains details about the filesystem, such as the state of the filesystem, the filesystem size, the filesystem name and volume name(s), path name of the mount point, and number of inodes. Every change to the inodes also requires changes to the superblock.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Highpoint RAID Troubleshooting (Legacy)

For troubleshooting information, see the attached PDF.
The following exacqVision models were manufactured with Highpoint RAID controllers from 2007 to 2009:

  • 2310 (4 ports)
  • 2320 (8 ports)
  • 2300 (4 ports, PCIe 1x)

<br>

To determine whether your system contains a Highpoint RAID controller, look at the RAID BIOS screen that appears when the system is first started (before the operating system starts).

<br>