Xeoma

Command followed by port you need. If Xeoma is installed, go to the autostart script and change serverport there. For example, in Windows: go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\XeomaCoreService in registry and change thereC:\Users\test\AppData\Local\VirtualStore\Program Files\Xeoma\xeoma.exe -service -startdelay 10 -serverport 10099. For Linux, see here where autostart script is6. Xeoma is running in fedora 18. When I run xeoma -core, I cannot connect remotely from the client. What should I do?Please run -showpassword in a command line of Xeoma to see a remote access password (you need it to connect remotely) and it will enable remove access automatically. Then start Xeoma again and it will accept connections from any IP. If you install Xeoma, remote access will be enabled automatically.7. The message I get every time I try to start ./xeoma.app -client is:! XWindow graphical shell is not available in console modeAny ideas what could be wrong?Please check if you have XAUTHORITY variable installed:echo $XAUTHORITYIf not, install it.8. I have Xeoma server on my Linux without GUI. How do I get to know the server part’s version?When you connect to the server part from a client you will see version of server and version of client in the title of Xeoma window. If your server part is not installed to autostart, you get the info in Terminal when you launch Xeoma.9. How do I download previous Xeoma version on my Linux server without GUI?You can use the following command (e.g. to download 20.12.18 Xeoma version): wget Where “2020-12-18” is number of the version 20.12.18 that you require expanded into the date format (another example: wget for version Xeoma 17.8.31). You can check the name of Xeoma’s previous versions here.After you download necessary version, you can use this Linux manual to unpack and install Xeoma.10. I am running Xeoma on an Odroid XU4 with Ubuntu Mate 20.04. Installed a VNC server for remote access, but the Xeoma app will not start over the VNC session. Any ideas how to fix thisAre you using TightVNC? Its settings do not allow to start Xeoma Client.The easiest way to resolve this issue is to inslall RealVNC version:sudo apt-get updatesudo apt-get install realvnc-vnc-server realvnc-vnc-viewerthen:sudo raspi-configThen select Interfacing Options and enable VNC. This way the client should start correctly.11. I don’t have sound on Linux. What is the reason?When Xeoma is installed to autostart on a Linux system, it runs under “root” user. By default, “root” does not have access to audio, that is why you can’t get it to play back your own files.You can either run Xeoma under a normal user (without installing to autostart) or use a workaround to provide sound for “root”. Read the instruction on how to do it by the link: feel free to

XeomaCoreService autostart script can be found in:etc/init.detc/init/etc/systemd/system/If you need to edit the script (for example, to increase delay before start) you need to do that with admin rights, otherwise the changes won’t be saved.Starting from the version Xeoma 22.11.25, a new feature to specify console command that will be added to the autostart script after installation has been added for console commands when installing Xeoma. For example, if you conduct -install -coreauto -serverport 8888, -serverport 8888 command will be added to the autostart script automatically. Previously, additional commands were not combined with the installation commands and they had to be specified manually in the autostart script.Launch/installation troubleshooting1. Error cannot execute binary file (at launch)If you’re getting an error message as follows:root@myUser:/home/myFolder# uname -aLinux myUser 2.7.32-504.el6.i686 #1 SMP Wed Oct 15 03:02:07 UTC 2014 i686 i686 i386 GNU/Linuxroot@myUser:/home/myFolder# ./xeoma.appbash: ./xeoma.app: cannot execute binary filePlease make sure that you are launching 32 bit Xeoma on 32 bit Linux, or 64 bit Xeoma on 64 bit Linux. Installing ia32-libs might help, or simply use Xeoma of bit capacity that matches your OS’s bit capacity.Another reason for this error might be insufficient rights. In such case please try to execute chmod 777 xeoma.app in the folder where your xeoma.app is, and then launch Xeoma server again (xeoma.app -core).2. Error “No such file or directory” (at launch)If you are getting the No such file or directory error at launch, please check if you run the program on one of supported operating systems.Also, this error can occur if you run 32-bit Xeoma on 64-bit Linux (or vice versa). Make sure to run 32-bit Xeoma on 32-bit Linux and 64-bit Xeoma on 64-bit Linux – just download suitable version of Xeoma for your OS. 3. Error “Access denied” (at launch)If you’re getting an error message as follows:bash: ./xeoma.app: Access deniedThis error can occur if you’re trying to launch Xeoma on a USB stick or a disc mounted into the system with a noexec parameter. We recommend to try to launch Xeoma on a system disc or disable execution restrictions.4. Error Illegal instruction (Core dumped) (at launch)If you’re getting the Illegal instruction error at launch you might be using an outdated processor that can’t process Xeoma. In this case please try to launch an older version Xeoma 15.2.25 instead. If it works while newer versions don’t you are advised to upgrade your hardware.There’s another variation of this error: Segmentation fault (core dumped)If you’re getting this error message, there might be 3 issues/resolutions:a. Processor is too old and it can not be used to run Xeoma. In this case please try to launch an older version Xeoma 15.2.25 instead.b. Wrong xeoma.app file. Please check your OS and download the

Pro, Xeoma Standard, Xeoma Lite, Xeoma Starter) that require activation – and they too work in virtual machines. Xeoma has several types of licenses (perpetual, rented or demo licenses) and there are several options for activation of each of them. In most cases the easiest way to activate Xeoma licenses is to have permanent Internet access enabled in the VM or Docker system. Sometimes – especially in banks, governmental or military organizations – Internet access is restricted but Xeoma has such cases covered too! With hardware keys and/or license server options video surveillance systems can work in virtual machines even in such isolated distributed systems.Online activation:After you obtain a Xeoma license, you will get an alphanumeric serial number that should be entered in Xeoma’s “Activate” tab or through a console command. This method works for virtual machines too if they have permanent Internet access. This method works for perpetual, rented and demo licenses (including Renewals, and Upgrade from Standard to Pro).License server:Using another machine – virtual or physical – in the same home network with the VM you need the licensed Xeoma on to send activation requests through and pass the responses to VM. That other machine should have Internet access and constant network connection to the VM with Xeoma. In simple words, the principle is to delegate the activation to another machine (even as small as a single-board micro computer or even a smartphone) that can seed the activated license to a virtual machine with video surveillance. Available for perpetual licenses (one-time Internet connection required) and rented or demo licenses (perpetual Internet connection required). Read more about network activation with a license serverHardware key:When the virtual machine or Docker with Xeoma video surveillance has no Internet connection, and there is no computer in the same network with constant connection to that VM that could be an intermediary for activation, you can use a hardware key license instead of a regular ‘software’ form of license Xeoma is supplied in. A hardware key is a USB device that should be inserted into a USB slot of the computer with Xeoma and