Tag: Linux

Categories
Knowledge Support Support exacqVision Server Categories Products

Email Notifications Not Sent from Linux-based exacqVision Server

If you install exacqVision Server software on a Linux-based system that does not have certain Perl modules installed, email notifications can fail. This does not apply to Linux-based exacqVision systems shipped by Exacq because the Perl modules are installed on the systems when they are manufactured.

If you do not receive expected email notifications, check the Linux system log for the following message from NotifyPI:

Can’t locate method “new” via package “IO::Socket::SSL” at sendEmail.pl line 1844

The following message should also appear on the Notifications page for the system in the exacqVision Client software:

This server does not support SSL or TLS connections

To install the necessary Perl modules, type the following commands in a Terminal window:

sudo apt-get install libio-socket-ssl-perl

sudo apt-get install libnet-ssleay-perl

Alternatively, you can install the modules using the Synaptic Package Manager.

<br>

Categories
Knowledge Support Support Categories exacqVision Webservice Products

Changing Web Server Default Image Quality (Legacy)

Instructions

These instructions only apply to web services 9.4 and earlier. 

The changes described only affect the default image quality in “simple” mode and this process is not upgrade safe. You must perform this process again each time you upgrade Web Server.

<br>

  1. For Windows: Browse to C:\Program Files\exacqVision\WebService\bin\templates.

    For Linux:     Browse to /usr/local/exacq/webservice/bin/templates.
  2. Open the file config.html.mako.
  3. Look for the following section:

    query_string = urllib.urlencode([(“s”, hex(server.id)),
                                       (“p”, camera.plugin),
                                       (“d”, camera.device),
                                       (“i”, camera.input),
                                       (“w”, “320”),
                                       (“h”, “240”),
                                       (“q”, “7”)])
  4. Add a line to the end of that section as follows:

    query_string = urllib.urlencode([(“s”, hex(server.id)),
                                       (“p”, camera.plugin),
                                       (“d”, camera.device),
                                       (“i”, camera.input),
                                       (“w”, “320”),
                                       (“h”, “240”),
                                       (“q”, “7”),
                                       (“r”, “5”)])
  5. Change the values to match your preferred settings for the following parameters:

    NOTE: Starting in Web Server 2.1, the following values are stored in a cookie generated from the Web Server. However, you can add these values to the config.html.mako file to override the cookie.

    w = width
    h = height
    q = quality
    r = refresh interval
  6. Save the file.
  7. Open or refresh the Web Server page in your web browser.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Firefox will not run on Linux-based exacqVision Server

If you cannot run Mozilla Firefox on a new Linux server, remove the .mozilla directory from the Admin account home folder. To do this, complete the following steps:

<br>

  1. Log in to Ubuntu as an admin.
  2. Open a Terminal window (Start > Accessories > Terminal).
  3. Typesudo rm -rf ~/.mozilla.
  4. Enter the password for the admin account.
  5. Run Firefox.

<br>

Firefox-will-not-run-on-Linux-based-exacqVision-Server.pdf
Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Analog Boards Don’t Work after Upgrading Ubuntu

A directory must be created to make after upgrading Ubuntu. Run the following command in the Terminal:

<br>

sudo make /usr/local/xdvapi/modules

<br>

Then restart the services.

<br>

Analog-Boards-Dont-Work-after-Upgrading-Ubuntu.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

How do I change the listening port number for exacqVision Server?

By default, the exacqVision Client communicates with exacqVision Servers on port 22609. If your network does not allow port 22609, or if you need to forward the port on multiple exacqVision systems, you can change the exacqVision Server’s listening port number. To do this, complete steps detailed on this page.

NOTE: The exacqVision Default Ports article states that 22610 is reserved for interprocess communication. This is true when using the default client to server port set to 22609. If this is changed to a port other than 22609, the reserved port becomes your chosen port number plus one.
Example: If you change 22609 to 2350, the reserved port becomes 2351.<br><br>

Windows 11, 10, 8, 7, Vista, XP

  1. Log into the system hosting the exacqVision Server application.<br><br>
  2. Exit all exacqVision software.<br><br>
  3. Highlight the exacqVision Server service listed, and Stop the ExacqVision Server service, in one of three ways:
    • Press the ‘Stop’ icon from the toolbar.
    • Click the ‘Stop’ link from the left-hand side.
    • Right-click the service name and select ‘Stop’.

      Note: Leave the Services window open, as you will need to restart the service later.<br><br>
  4. Open the Notepad application. Search for the application from the Windows Start menu, right-click and choose to ‘Run as Administrator’.
    <br><br>
  5. Use Notepad to Open the following file:
    C:\Program Files\exacqVision\Server\streampi.xml<br>
    If you are using a 32-bit installation, select Program Files (x86) instead of Program Files.<br>
    NOTE: In the Open file dialogue, you will likely need to change the file type field from ‘Text Documents (*.txt)’ to All Files (*.*)’ to see file types of other extensions.

    <br><br>
  6. In the streampi.xml file, scroll down until you find the line which states: <Port value="22609" />.

    Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’.
    <br><br>
  7. After changing the port number, open the File menu, select Save, and close the editor window.<br><br>
  8. Restart the exacqVision Server Service by clicking ‘Start’ button, link or from the right-click menu, in the Services window that you opened earlier. You should now be able to connect using the new port number.<br><br>
  9. In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number.
    NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.<br><br>

Ubuntu 20.04, 18.04, 16.04, 14.04, 12.04, 10.04

  1. Log into the system hosting the exacqVision Server application.<br><br>
  2. Exit all exacqVision software.<br><br>
  3. Open a Terminal command prompt by pressing CTRL+ALT+T

    NOTE: Depending on system settings, your Terminal window may appear with different colors than pictured.<br><br>
  4. Stop the exacqVision Server by entering one of the following commands:
    • sudo service edvrserver stop
    • sudo /etc/init.d/edvrserver stop

      NOTE: The sudo command elevates your system privileges in order to edit this file. Your system may prompt you for an administrator password. Enter this password if prompted. Linux systems do not display any characters when entering passwords in the CLI.

      NOTE: On some systems you may see output that reads:
      sudo: unable to resolve host <hostname>
      Ignore this message if seen.<br><br>
  5. You may use your preferred Linux editing tool, but in our example we will be using ‘gedit’.

    Use gedit to open the streampi.xml file containing the settings for the exacqVision Server by entering:
    sudo gedit /usr/local/exacq/server/streampi.xml<br><br>
  6. Locate the line which states: <Port value:"22609" />

    Change the number to the port you want to use between the quotation marks (” “). Do NOT use port 22610 since this is reserved. The following example changes the port number to ‘11111’.
    <br><br>
  7. Click ‘Save’ to commit your changes and close the editor window. <br><br>
  8. Returning to the Terminal prompt, enter one of the following commands to restart the exacqVision Server:
    • sudo service edvrserver start
    • sudo /etc/init.d/edvrserver start<br><br>
  9. In the exacqVision Client, make sure the port number on the ‘Add Systems’ page matches the new port number.

    NOTE: The exacqVision Web Service is also a client of the exacqVision Server. Therefore, if using the exacqVision Web Service you may also be required to change the connecting port in the exacqVision Web Service Configuration.

<br>

Categories
Categories exacqVision Webservice Products

Can ExacqVision Server run on Linux?

Yes, ExacqVision Server has been tested on the following:

  • Ubuntu 22.04 (64-bit)
  • Ubuntu 20.04 (64-bit)
  • Ubuntu 18.04 (64-bit)
  • Ubuntu 16.04 (64-bit)
  • Ubuntu 14.04 (64-bit or 32-bit with PAE1)
  • Ubuntu 12.04 (32-bit with PAE1)2
  • Ubuntu 10.04 (32-bit with PAE1)2

Version numbers are listed as YY.MM.

ExacqVision supports Ubuntu LTS releases only. Canonical provides LTS releases every two years. Long Term Support (LTS) lasts for a period of 10 years after release. ExacqVision will provide support for future LTS releases of Ubuntu as they become available.<br>

  1. PAE stands for Physical Address Extension, which allows 32-bit systems to use more than 4GB of memory.
  2. These versions are no longer receiving security updates from Canonical. At the end of long term support, future Exacq software releases will not be tested on these versions.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

When exacqVision software is released, how long until the macOS and Linux versions are available?

All versions of exacqVision software are released at the same time because the code that runs on Windows is the same as the code that runs on the Linux and macOS platforms but compiled for each operating system.

exacqVision Server, Web Service, and Enterprise Manager are currently available for Windows and Linux.

The exacqVision Desktop Client is available for Windows, macOS, and Linux.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Removing an Unwanted “Orphaned” Drive From the Storage Page

Title

Removing an Unwanted “Orphaned” Drive From the Storage Page

Description 

ExacqVision retains any drive which has ever been added to the NVR.  This can result in unwanted or “Orphaned” drives showing up on the Storage Page.  Removing these drives requires manual intervention. 

Product 

ExacqVision Server

Solution

Windows 

  1. Log into the operating system of the server as an administrator, you cannot perform these steps from a client workstation.
  2. Click the Windows key + R to open the run box 
  3. Type services.msc and press enter 
  4. Locate and right-click on exacqVision Server, select stop 
  5. Open Notepad as an administrator 
  6. Browse to and open C:\Program Files\exacqVision\Server\psfpi.xml
  7. Locate and delete the line containing the orphaned drive.
  8. Save and close psfpi.xml 
  9. Back in Services, right-click on exacqVision Server, select start
  10. Verify the drive is no longer present in the ExacqVision Client

Linux 

  1. Log into the operating system as an administrator
  2. Open a Terminal Window and stop the ExacqVision Server Service 
        sudo service edvrserver stop

Note: If prompted enter the admin operating systems password then press enter.  Linux will not give any feedback while entering the password. 

  1. Edit psfpi.xml using the following command 
        sudo nano /usr/local/exacq/server/psfpi.xml
  1. Using the arrow keys, move to the beginning of the line containing the orphaned drive 
  2. Press control+k to delete the line 
  3. Press control+o to save the file
  4. Press control+x to exit 
  5. Start the exacqVision Server Service 
        sudo service edvrserver start
  1. Verify the drive is no longer present in the exacqVision Client

Example

In the example below the drive labeled /mnt/edvr/2 is unwanted and will need to be manually removed. 
ExacqVision Client before and after orphaned drive removed

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Creating a Shutdown Hot Key in Linux

To create a shutdown hot key on a Linux ExacqVision system, complete the following steps:

Ubuntu 20.04 & 18.04

These systems are already configured to use CTRL+ALT+DEL to pop up a dialogue with a shutdown option. Once the dialogue opens the system will shutdown if no further user interaction occurs.

Ubuntu 16.04 and earlier

This requires advanced customization using donf-editor which is beyond the support provided by Exacq Support. Users perform any such customization on their own.

<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