Home › Forums › Search › Search Results for 'code'

Need a new search?

If you didn't find what you were looking for, try a new search!

Viewing 15 results - 31 through 45 (of 113 total)
Previous 1 2 3 4 … 6 7 8 Next
  • Author
    Search Results
  • Telium Support Group
    Moderator
    October 14, 2018 at 2:00 pm
    Post count: 263
    #6831 In reply to: Connect to our site using VPN |

    We would be happy to SSH into your hosts to help with configuration.

    Our support machines have pre-installed VPN clients for the most popular protocols: Microsoft Windows protocols (PPTP/L2TP/IPSec/IKEv2), and shared Cisco VPN protocols.

    If you chose not to use one of these protocols, or you require that we install a VPN client that is locked to your VPN concentrator address, then we must build a virtual machine for our support techs to use when connecting to your system. Our support techs cannot (and may not) install any software on their machines, in order to protect our computing environment.

    If you cannot use one of the pre-installed VPN protocols above, and you cannot port forward SSH from your public IP to your nodes, then we will have to charge you an additional 2 hours of support time to build and maintain a support VM dedicated to your environment. We will also archive this VM (while your maintenance agreement is active) to ensure we can continue to support you going forward.

    See FAQ 10042 for additional information: https://telium.io/faq1042

    Customer Inquiry
    Participant
    October 14, 2018 at 1:53 pm
    Post count: 201
    #6547
    Topic: Connect to our site using VPN in forum General |

    We need help with some complex configuration issues and need you to SSH into our nodes. Can you VPN into our site to help?

    We use the SoftEther VPN server (https://www.softether.org/) so you would have to use that client.

    Customer Inquiry
    Participant
    October 14, 2018 at 1:53 pm
    Post count: 201
    #6548
    Topic: Connect to our site using VPN in forum General |

    We need help with some complex configuration issues and need you to SSH into our nodes. Can you VPN into our site to help?

    We use the SoftEther VPN server (https://www.softether.org/) so you would have to use that client.

    Customer Inquiry
    Participant
    October 14, 2018 at 1:53 pm
    Post count: 201
    #6576
    Topic: Connect to our site using VPN in forum General |

    We need help with some complex configuration issues and need you to SSH into our nodes. Can you VPN into our site to help?

    We use the SoftEther VPN server (https://www.softether.org/) so you would have to use that client.

    Telium Support Group
    Moderator
    October 14, 2018 at 1:18 pm
    Post count: 263
    #6794 In reply to: Different trunks on cluster nodes |

    HAAst can handle that easily using the event handler system. There are 2 aspects to your cluster that must be handled separately: the FreePBX configuration, and the Asterisk configuration. Remember that FreePBX is a pretty GUI with it’s own configuration database (in MySQL), and it regenerates the Asterisk configuration files (flat files) when you click apply changes. So we have to handle each a bit differently.

    I should also point out that because FreePBX creates a relationship between DIALPLAN->ROUTES->TRUNKS, you cannot simply delete a trunk on one node but have it present on the other. To effectively remove the second trunk from London we modify one trunk configuration to ensure it cannot be activated by Asterisk (so it will be ignored in the dialplan). We do so by setting the SIP port to an invalid number.

    FreePBX Configuration
    To make your life simpler (and setup less confusing), on your New York FreePBX name your NY1 and NY2 trunks:

    Quote:
    MASTER_TRUNK1 (for the trunk)
    MASTER_TRUNK1_IN (for inbound)
    MASTER_TRUNK1_OUT (for outbound)
    MASTER_TRUNK2
    MASTER_TRUNK2_IN
    MASTER_TRUNK2_OUT

    Next, add to your New York FreePBX your LON trunk named exactly as follows:

    Quote:
    SLAVE_TRUNK1 (for the trunk)
    SLAVE_TRUNK1_IN (for inbound)
    SLAVE_TRUNK1_OUT (for outbound)

    Finally, add to your New York FreePBX a duplicate the above SLAVE_TRUNK1 to be named SLAVE_TRUNK2:

    Quote:
    SLAVE_TRUNK2
    SLAVE_TRUNK2_IN
    SLAVE_TRUNK2_OUT

    In FreePBX (on Master) edit your routes to use:

    1. MASTER_TRUNK1
    2. SLAVE_TRUNK1
    3. MASTER_TRUNK2
    4. SLAVE_TRUNK2

    in that order. Don’t worry about NY using SLAVE trunks, or London using MASTER trunks. HAAst will disable them to ensure only the right trunks are used in the right location.

    HAAst FreePBX MySQL event handler
    HAAst will be responsible for enabling all master trunks in New York (and disabling all slave trunks), and enabling all slave trunks in London (and disabling master trunks there), and changing the external IP address (for SIP config). HAAst will also disable SLAVE_TRUNK2 in London so it won’t be used (contents ignored). HAAst will also change the external IP address in SIP settings. Assuming that you are using the sample HAAst configuration file for Sangoma FreePBX, you will have a sync job named ‘freepbx-mysql’. You need to create a post-sync event handler (file) called sync.stop.post.freepbx-mysql in the /usr/local/haast/events folder. That event handler will be responsible for enabling/disabling trunks:


    #!/bin/bash

    # Determine if this is the SLAVE PBX
    ISSLAVE=$(hostname | grep london | wc -l)

    # Determine value of ‘disabled’ setting in FreePBX
    if [ ${ISSLAVE} -eq 0 ] ; then
    NODENAME=”NewYork”
    LOCALIP=”1.2.3.4″
    REMOTEIP=”5.6.7.8″
    MASTERDISABLED=”off”
    SLAVEDISABLED=”on”
    else
    NODENAME=”London”
    REMOTEIP=”1.2.3.4″
    LOCALIP=”5.6.7.8″
    MASTERDISABLED=”on”
    SLAVEDISABLED=”off”
    fi

    #—————————————————————————-

    HVERBOSE=0
    if [ -f “/usr/local/haast/internal/helperfunctions.sh” ] ; then
    . /usr/local/haast/internal/helperfunctions.sh
    elif [ -f “../internal/helperfunctions.sh” ] ; then
    . ../internal/helperfunctions.sh
    else
    echo “ERROR: Cannot find helperfunctions.sh”
    exit 10
    fi

    # Update the trunks table for MASTER_XXX trunks
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”update trunks set disabled=’${MASTERDISABLED}’ where name like ‘MASTER_%'”

    # Update the trunks table for SLAVE_XXX trunks
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”update trunks set disabled=’${SLAVEDISABLED}’ where name like ‘SLAVE_%'”

    # Update the kvblob table for the SIP settings > externip value
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”UPDATE kvblobstore SET content = REPLACE(content, ‘${REMOTEIP}’, ‘${LOCALIP}’)”
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”UPDATE kvstore_FreePBX_modules_Sysadmin SET val = REPLACE(val, ‘${REMOTEIP}’, ‘${LOCALIP}’)”
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”UPDATE kvstore_Sipsettings SET val = REPLACE(val, ‘${REMOTEIP}’, ‘${LOCALIP}’)”
    mysql
    -u ${MYSQL_SYNCUSERNAME}
    -p${MYSQL_SYNCPASSWORD}
    -h ${MYSQL_SYNCLOCALHOST}
    -D asterisk
    -P ${MYSQL_SYNCPORT}
    -N
    -B
    –execute=”UPDATE sysadmin_options SET value = REPLACE(value, ‘${REMOTEIP}’, ‘${LOCALIP}’)”

    # Tell HAAst all exitted ok
    exit 0

    HAAst Asterisk file event handler
    HAAst will be responsible for ensuring the trunk information (in sip.conf) has the contents appropriate for the node it is running on. There are also 2 distinct use cases we must consider. First use case: if SLAVE becomes active and the admin edits the configuration in FreePBX then Asterisk must accept that configuration and run normally (even if no event handlers have run). In this case there is nothing to be done since the disabled trunks will not generate any config data for Asterisk since they have been disabled in FreePBX. (Nothing to do). Second use case: The Asterisk configuration files from MASTER has been sent to SLAVE, and the SLAVE trunks contain information relevant for New York. To handler this situation we replace trunk content (in the Asterisk config files), and we also remove the MASTER_ prefix from any Asterisk config files (for clarity). Assuming that you are using the sample HAAst configuration file for Sangoma FreePBX, you will have a sync job named ‘freepbx-conf’. You need to create a post-sync event handler (file) called sync.stop.post.freepbx-conf in the /usr/local/haast/events folder. That event handler will be responsible for modify the Asterisk config files:


    #!/bin/bash

    # Determine if this is the SLAVE PBX
    ISSLAVE=$(hostname | grep london | wc -l)

    # Determine value of ‘disabled’ setting in FreePBX
    if [ ${ISSLAVE} -eq 0 ] ; then
    NODENAME=”NewYork”
    SECRET=”NySeCrEt”
    HOST=”12.23.34.45″
    EXTERNIP=”1.2.3.4″
    else
    NODENAME=”London”
    SECRET=”LoNSeCrEt”
    HOST=”98.87.76.65″
    EXTERNIP=”9.8.7.6″
    fi

    #—————————————————————————-

    HVERBOSE=0
    if [ -f “/usr/local/haast/internal/helperfunctions.sh” ] ; then
    . /usr/local/haast/internal/helperfunctions.sh
    elif [ -f “../internal/helperfunctions.sh” ] ; then
    . ../internal/helperfunctions.sh
    else
    echo “ERROR: Cannot find helperfunctions.sh”
    exit 10
    fi

    # Remove MASTER_ and SLAVE_ prefixes from sip config files and dialplan config files,
    # to allow for shared files between MASTER and SLAVE (with shared trunk names)
    sed -i ‘s/MASTER_//g’ /etc/asterisk/sip_additional.conf
    sed -i ‘s/MASTER_//g’ /etc/asterisk/extensions_additional.conf
    sed -i ‘s/SLAVE_//g’ /etc/asterisk/sip_additional.conf
    sed -i ‘s/SLAVE_//g’ /etc/asterisk/extensions_additional.conf

    # Enable / disable trunks in Asterisk config files, and alter settings for common
    if [ ${ISSLAVE} -eq 0 ] ; then
    # THIS IS MASTER
    # Enable trunk2 by removing port to a value that will never accept SIP
    # TRUNK2
    crudini –del –inplace /etc/asterisk/sip_additional.conf “TRUNK2_OUT” port
    else
    # THIS IS SLAVE
    # Disable trunk2 by setting port to a value that will never accept SIP
    crudini –set –inplace /etc/asterisk/sip_additional.conf “TRUNK2_OUT” port “9999”
    fi

    # Change values to match required local node settings
    # TRUNK1
    echo secret=”${HOST}” | crudini –merge –inplace /etc/asterisk/sip_additional.conf “TRUNK1_OUT”
    echo secret=”${SECRET}” | crudini –merge –inplace /etc/asterisk/sip_additional.Tconf “TRUNK1_OUT”
    # External IP address
    echo external_media_address=”${EXTERNIP}” | crudini –merge –inplace /etc/asterisk/pjsip.transports.conf “0.0.0.0-udp”
    echo external_signaling_address=”${EXTERNIP}” | crudini –merge –inplace /etc/asterisk/pjsip.transports.conf “0.0.0.0-udp”
    echo externip=”${EXTERNIP}” | crudini –merge –inplace /etc/asterisk/sip_general_additional.conf “”

    # Notify HAAst of success
    exit 0

    Notice that the above event handler also disables TRUNK2 by adding an incorrect sip port number (9999), and uses the open source ‘crudini’ package to accomplish this. This will cause the trunk connection to fail, and Asterisk will ignore the trunk. The result is that the ROUTES as setup in FreePBX will skip this trunk.

    Notice as well that we hard coded a bit of information at the start of the event handlers; this is for simplicity. If you want to get really fancy, you can extract the relevant trunk data from the MySQL database and use that to update the Asterisk files. But the above explains the concept in the simplest way possible.

    teliumcustomer4
    Member
    October 3, 2018 at 2:05 pm
    Post count: 3
    #6789 In reply to: Database command failed on write to eventlog table |

    Its contiguous and database are in same server

    With dblevel=debug after restart secast, direct log:


    Wed Oct 3 15:48:05 2018, 00000103, I, General, Received shutdown request via TERM signal
    Wed Oct 3 15:48:05 2018, 00000126, W, Controller, Manual shutdown request by module Operating System
    Wed Oct 3 15:48:05 2018, 00010038, W, Controller, Stopping
    Wed Oct 3 15:48:05 2018, 00000128, D, Telnet Server, Requesting disconnect of all telnet clients
    Wed Oct 3 15:48:05 2018, 00000120, D, Socket Server, Requesting disconnect of all socket clients
    Wed Oct 3 15:48:05 2018, 00000107, I, General, SecAst state changing to not protecting
    Wed Oct 3 15:48:05 2018, 00000800, D, Alert, Sent email: Entering Non-Protecting State
    Wed Oct 3 15:48:05 2018, 00001211, D, Asterisk Controller, Flushed 0 message(s) from received message queue
    Wed Oct 3 15:48:05 2018, 00001210, D, Asterisk Controller, Flushed 1 message(s) from sent message queue
    Wed Oct 3 15:48:06 2018, 00001400, D, Controller, Flushed 0 IP(‘s) from IP watch list
    Wed Oct 3 15:48:06 2018, 00000903, D, Threat Info, Flushed 8 IP(‘s) from internal blocked list
    Wed Oct 3 15:48:06 2018, 00002823, D, Controller, Stopping – stage 1
    Wed Oct 3 15:48:06 2018, 00001211, D, Asterisk Controller, Flushed 0 message(s) from received message queue
    Wed Oct 3 15:48:06 2018, 00001210, D, Asterisk Controller, Flushed 0 message(s) from sent message queue
    Wed Oct 3 15:48:06 2018, 00001259, I, Asterisk Controller, Stopped
    Wed Oct 3 15:48:06 2018, 00001303, I, Geo IP, Closed GeoIP database
    Wed Oct 3 15:48:06 2018, 00001307, D, Geo IP, Flushed 0 location(s) from geoIP cache
    Wed Oct 3 15:48:06 2018, 00001602, I, Controller, Pipe server stopping
    Wed Oct 3 15:48:06 2018, 00000201, I, Controller, Telnet server stopping
    Wed Oct 3 15:48:06 2018, 00000601, D, Security Event Queue, Security event queue stopping
    Wed Oct 3 15:48:06 2018, 00000604, D, Security Event Queue, Flushed 0 event(s) from queue
    Wed Oct 3 15:48:06 2018, 00002832, I, Controller, Recovery state will no longer be automatically saved
    Wed Oct 3 15:48:06 2018, 00002833, D, Controller, Initiating final recovery state save
    Wed Oct 3 15:48:06 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:48:06 2018, 00002808, D, Controller, firewall (iptables) not flushed on shutdown
    Wed Oct 3 15:48:07 2018, 00002823, D, Controller, Stopping – stage 2
    Wed Oct 3 15:48:07 2018, 00000800, D, Alert, Sent email: Stopping Normally
    Wed Oct 3 15:48:07 2018, 00000113, D, General, SecAst state changing to stopping
    Wed Oct 3 15:48:07 2018, 00002824, I, Controller, Stopped
    Wed Oct 3 15:48:07 2018, 00000101, I, General, SecAst terminating with exit code 0 (normal termination) after running for 34 seconds
    Wed Oct 3 15:48:09 2018, 00000100, I, General, SecAst version 1.5.9 starting as daemon under process ID 31226
    Wed Oct 3 15:48:09 2018, 00000100, D, General, SecAst Build 1157; Build date Monday June 25 2018 10:47:00 AM CEST; Architecture Intel 64-bit; Distribution unknown
    Wed Oct 3 15:48:09 2018, 00000111, D, General, SecAst state changing to starting
    Wed Oct 3 15:48:09 2018, 00001700, D, Database Controller, Database manager thread started
    Wed Oct 3 15:48:09 2018, 00001009, I, License, Unable to find license file ‘/usr/local/secast/secast.license’. Switching to Free Edition
    Wed Oct 3 15:48:09 2018, 00000122, I, General, Settings contained 0 information; 0 warning; and 0 error messages.
    Wed Oct 3 15:48:09 2018, 00000300, I, Controller, Telnet server listening on 0.0.0.0:3000
    Wed Oct 3 15:48:09 2018, 00001600, I, Controller, Pipe server listening on /run/secast.sock
    Wed Oct 3 15:48:09 2018, 00002810, D, Controller, firewall (iptables) not flushed on start
    Wed Oct 3 15:48:09 2018, 00001300, D, Geo IP, Found GeoIP database version 2.0.1501721259 updated Thursday August 3 2017 2:47:39 AM CEST
    Wed Oct 3 15:48:09 2018, 00001302, I, Geo IP, Opened GeoIP database
    Wed Oct 3 15:48:09 2018, 00000600, D, Security Event Queue, Security event queue starting
    Wed Oct 3 15:48:09 2018, 00000612, E, Security Event Queue, Adding 8 IP addresses found in firewall as managed addresses
    Wed Oct 3 15:48:09 2018, 00002835, D, Controller, Restoring recovery state from file
    Wed Oct 3 15:48:09 2018, 00002837, I, Controller, Restoring recovering state from file created by host ‘My VOIP PBX’ at Wed Oct 3 13:48:06 2018 GMT
    Wed Oct 3 15:48:09 2018, 00002831, I, Controller, Recovery state will be saved every 60 seconds
    Wed Oct 3 15:48:09 2018, 00001258, I, Asterisk Controller, Starting
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘37.75.214.124’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘185.85.241.179’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘173.249.38.228’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘104.206.96.186’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘162.245.239.26’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘185.53.91.49’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘209.95.48.131’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000902, D, Threat Info, Adding IP address ‘173.249.32.182’ to banned IP list
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘37.75.214.124’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘185.85.241.179’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘173.249.38.228’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘104.206.96.186’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘162.245.239.26’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘185.53.91.49’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘209.95.48.131’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000900, D, Threat Info, Ignoring attempt to add recovery IP ‘173.249.32.182’ to banned IP list due to already present
    Wed Oct 3 15:48:09 2018, 00000800, D, Alert, Sent email: SecAst Starting
    Wed Oct 3 15:48:09 2018, 00000107, I, General, SecAst state changing to not protecting
    Wed Oct 3 15:48:09 2018, 00000800, D, Alert, Sent email: Entering Non-Protecting State
    Wed Oct 3 15:48:09 2018, 00001201, I, Asterisk Controller, Connection established to AMI
    Wed Oct 3 15:48:09 2018, 00001205, D, Asterisk Controller, Login to AMI succeeded
    Wed Oct 3 15:48:09 2018, 00000108, I, General, SecAst state changing to protecting
    Wed Oct 3 15:48:09 2018, 00000800, D, Alert, Sent email: Entering Protecting State
    Wed Oct 3 15:48:10 2018, 00002828, D, General, Installed SecAst version (1.5.9) at or beyond latest version (0.0.0) available for download
    Wed Oct 3 15:48:10 2018, 00001705, D, Database Controller, Opened database ‘secastdb1’ on host ‘localhost’
    Wed Oct 3 15:48:10 2018, 00001705, I, Database Controller, Database open for archiving
    Wed Oct 3 15:48:13 2018, 00001603, D, Socket Server, Connection 1: Connecting
    Wed Oct 3 15:48:13 2018, 00001605, D, Socket Server, Connection 1: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:13 2018, 00001604, D, Socket Server, Connection 1: Disconnecting
    Wed Oct 3 15:48:13 2018, 00001603, D, Socket Server, Connection 2: Connecting
    Wed Oct 3 15:48:13 2018, 00001605, D, Socket Server, Connection 2: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:13 2018, 00001605, D, Socket Server, Connection 2: Executing command [geteventloglist]
    Wed Oct 3 15:48:13 2018, 00000002, D, Socket Server, open db connection
    Wed Oct 3 15:48:13 2018, 00001611, D, Socket Server, Opened database [secastdb1] on host [localhost]
    Wed Oct 3 15:48:13 2018, 00001613, D, Socket Server, Database closed
    Wed Oct 3 15:48:13 2018, 00001604, D, Socket Server, Connection 2: Disconnecting
    Wed Oct 3 15:48:18 2018, 00001603, D, Socket Server, Connection 3: Connecting
    Wed Oct 3 15:48:18 2018, 00001605, D, Socket Server, Connection 3: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:18 2018, 00001604, D, Socket Server, Connection 3: Disconnecting
    Wed Oct 3 15:48:23 2018, 00001603, D, Socket Server, Connection 4: Connecting
    Wed Oct 3 15:48:23 2018, 00001605, D, Socket Server, Connection 4: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:23 2018, 00001604, D, Socket Server, Connection 4: Disconnecting
    Wed Oct 3 15:48:27 2018, 00001603, D, Socket Server, Connection 5: Connecting
    Wed Oct 3 15:48:27 2018, 00001605, D, Socket Server, Connection 5: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:27 2018, 00001605, D, Socket Server, Connection 5: Executing command [gethistoricalbannediplist]
    Wed Oct 3 15:48:27 2018, 00000002, D, Socket Server, open db connection
    Wed Oct 3 15:48:27 2018, 00001611, D, Socket Server, Opened database [secastdb1] on host [localhost]
    Wed Oct 3 15:48:27 2018, 00001613, D, Socket Server, Database closed
    Wed Oct 3 15:48:27 2018, 00001604, D, Socket Server, Connection 5: Disconnecting
    Wed Oct 3 15:48:29 2018, 00001603, D, Socket Server, Connection 6: Connecting
    Wed Oct 3 15:48:29 2018, 00001605, D, Socket Server, Connection 6: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:29 2018, 00001605, D, Socket Server, Connection 6: Executing command [geteventloglist]
    Wed Oct 3 15:48:29 2018, 00000002, D, Socket Server, open db connection
    Wed Oct 3 15:48:29 2018, 00001611, D, Socket Server, Opened database [secastdb1] on host [localhost]
    Wed Oct 3 15:48:29 2018, 00001613, D, Socket Server, Database closed
    Wed Oct 3 15:48:29 2018, 00001604, D, Socket Server, Connection 6: Disconnecting
    Wed Oct 3 15:48:34 2018, 00001603, D, Socket Server, Connection 7: Connecting
    Wed Oct 3 15:48:34 2018, 00001605, D, Socket Server, Connection 7: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:34 2018, 00001604, D, Socket Server, Connection 7: Disconnecting
    Wed Oct 3 15:48:39 2018, 00001603, D, Socket Server, Connection 8: Connecting
    Wed Oct 3 15:48:39 2018, 00001605, D, Socket Server, Connection 8: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:39 2018, 00001604, D, Socket Server, Connection 8: Disconnecting
    Wed Oct 3 15:48:44 2018, 00001603, D, Socket Server, Connection 9: Connecting
    Wed Oct 3 15:48:44 2018, 00001605, D, Socket Server, Connection 9: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:44 2018, 00001604, D, Socket Server, Connection 9: Disconnecting
    Wed Oct 3 15:48:50 2018, 00001603, D, Socket Server, Connection 10: Connecting
    Wed Oct 3 15:48:50 2018, 00001605, D, Socket Server, Connection 10: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:50 2018, 00001604, D, Socket Server, Connection 10: Disconnecting
    Wed Oct 3 15:48:53 2018, 00001603, D, Socket Server, Connection 11: Connecting
    Wed Oct 3 15:48:53 2018, 00001605, D, Socket Server, Connection 11: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:53 2018, 00001605, D, Socket Server, Connection 11: Executing command [geteventloglist]
    Wed Oct 3 15:48:53 2018, 00000002, D, Socket Server, open db connection
    Wed Oct 3 15:48:53 2018, 00001611, D, Socket Server, Opened database [secastdb1] on host [localhost]
    Wed Oct 3 15:48:53 2018, 00001613, D, Socket Server, Database closed
    Wed Oct 3 15:48:53 2018, 00001604, D, Socket Server, Connection 11: Disconnecting
    Wed Oct 3 15:48:55 2018, 00001603, D, Socket Server, Connection 12: Connecting
    Wed Oct 3 15:48:55 2018, 00001605, D, Socket Server, Connection 12: Executing command [getdatabasestatus]
    Wed Oct 3 15:48:55 2018, 00001605, D, Socket Server, Connection 12: Executing command [geteventloglist]
    Wed Oct 3 15:48:55 2018, 00000002, D, Socket Server, open db connection
    Wed Oct 3 15:48:55 2018, 00001611, D, Socket Server, Opened database [secastdb1] on host [localhost]
    Wed Oct 3 15:48:55 2018, 00001613, D, Socket Server, Database closed
    Wed Oct 3 15:48:55 2018, 00001604, D, Socket Server, Connection 12: Disconnecting
    Wed Oct 3 15:49:00 2018, 00001603, D, Socket Server, Connection 13: Connecting
    Wed Oct 3 15:49:00 2018, 00001605, D, Socket Server, Connection 13: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:00 2018, 00001604, D, Socket Server, Connection 13: Disconnecting
    Wed Oct 3 15:49:05 2018, 00001603, D, Socket Server, Connection 14: Connecting
    Wed Oct 3 15:49:05 2018, 00001605, D, Socket Server, Connection 14: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:05 2018, 00001604, D, Socket Server, Connection 14: Disconnecting
    Wed Oct 3 15:49:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:49:10 2018, 00001603, D, Socket Server, Connection 15: Connecting
    Wed Oct 3 15:49:10 2018, 00001605, D, Socket Server, Connection 15: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:10 2018, 00001604, D, Socket Server, Connection 15: Disconnecting
    Wed Oct 3 15:49:16 2018, 00001603, D, Socket Server, Connection 16: Connecting
    Wed Oct 3 15:49:16 2018, 00001605, D, Socket Server, Connection 16: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:16 2018, 00001604, D, Socket Server, Connection 16: Disconnecting
    Wed Oct 3 15:49:21 2018, 00001603, D, Socket Server, Connection 17: Connecting
    Wed Oct 3 15:49:21 2018, 00001605, D, Socket Server, Connection 17: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:21 2018, 00001604, D, Socket Server, Connection 17: Disconnecting
    Wed Oct 3 15:49:26 2018, 00001603, D, Socket Server, Connection 18: Connecting
    Wed Oct 3 15:49:26 2018, 00001605, D, Socket Server, Connection 18: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:26 2018, 00001604, D, Socket Server, Connection 18: Disconnecting
    Wed Oct 3 15:49:31 2018, 00001603, D, Socket Server, Connection 19: Connecting
    Wed Oct 3 15:49:31 2018, 00001605, D, Socket Server, Connection 19: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:31 2018, 00001604, D, Socket Server, Connection 19: Disconnecting
    Wed Oct 3 15:49:36 2018, 00001603, D, Socket Server, Connection 20: Connecting
    Wed Oct 3 15:49:36 2018, 00001605, D, Socket Server, Connection 20: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:36 2018, 00001604, D, Socket Server, Connection 20: Disconnecting
    Wed Oct 3 15:49:41 2018, 00001603, D, Socket Server, Connection 21: Connecting
    Wed Oct 3 15:49:41 2018, 00001605, D, Socket Server, Connection 21: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:41 2018, 00001604, D, Socket Server, Connection 21: Disconnecting
    Wed Oct 3 15:49:46 2018, 00001603, D, Socket Server, Connection 22: Connecting
    Wed Oct 3 15:49:46 2018, 00001605, D, Socket Server, Connection 22: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:46 2018, 00001604, D, Socket Server, Connection 22: Disconnecting
    Wed Oct 3 15:49:51 2018, 00001603, D, Socket Server, Connection 23: Connecting
    Wed Oct 3 15:49:51 2018, 00001605, D, Socket Server, Connection 23: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:51 2018, 00001604, D, Socket Server, Connection 23: Disconnecting
    Wed Oct 3 15:49:56 2018, 00001603, D, Socket Server, Connection 24: Connecting
    Wed Oct 3 15:49:56 2018, 00001605, D, Socket Server, Connection 24: Executing command [getdatabasestatus]
    Wed Oct 3 15:49:56 2018, 00001604, D, Socket Server, Connection 24: Disconnecting
    Wed Oct 3 15:50:01 2018, 00001603, D, Socket Server, Connection 25: Connecting
    Wed Oct 3 15:50:01 2018, 00001605, D, Socket Server, Connection 25: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:01 2018, 00001604, D, Socket Server, Connection 25: Disconnecting
    Wed Oct 3 15:50:06 2018, 00001603, D, Socket Server, Connection 26: Connecting
    Wed Oct 3 15:50:06 2018, 00001605, D, Socket Server, Connection 26: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:06 2018, 00001604, D, Socket Server, Connection 26: Disconnecting
    Wed Oct 3 15:50:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:50:11 2018, 00001603, D, Socket Server, Connection 27: Connecting
    Wed Oct 3 15:50:11 2018, 00001605, D, Socket Server, Connection 27: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:11 2018, 00001604, D, Socket Server, Connection 27: Disconnecting
    Wed Oct 3 15:50:16 2018, 00001603, D, Socket Server, Connection 28: Connecting
    Wed Oct 3 15:50:16 2018, 00001605, D, Socket Server, Connection 28: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:16 2018, 00001604, D, Socket Server, Connection 28: Disconnecting
    Wed Oct 3 15:50:22 2018, 00001603, D, Socket Server, Connection 29: Connecting
    Wed Oct 3 15:50:22 2018, 00001605, D, Socket Server, Connection 29: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:22 2018, 00001604, D, Socket Server, Connection 29: Disconnecting
    Wed Oct 3 15:50:27 2018, 00001603, D, Socket Server, Connection 30: Connecting
    Wed Oct 3 15:50:27 2018, 00001605, D, Socket Server, Connection 30: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:27 2018, 00001604, D, Socket Server, Connection 30: Disconnecting
    Wed Oct 3 15:50:32 2018, 00001603, D, Socket Server, Connection 31: Connecting
    Wed Oct 3 15:50:32 2018, 00001605, D, Socket Server, Connection 31: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:32 2018, 00001604, D, Socket Server, Connection 31: Disconnecting
    Wed Oct 3 15:50:37 2018, 00001603, D, Socket Server, Connection 32: Connecting
    Wed Oct 3 15:50:37 2018, 00001605, D, Socket Server, Connection 32: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:37 2018, 00001604, D, Socket Server, Connection 32: Disconnecting
    Wed Oct 3 15:50:42 2018, 00001603, D, Socket Server, Connection 33: Connecting
    Wed Oct 3 15:50:42 2018, 00001605, D, Socket Server, Connection 33: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:42 2018, 00001604, D, Socket Server, Connection 33: Disconnecting
    Wed Oct 3 15:50:47 2018, 00001603, D, Socket Server, Connection 34: Connecting
    Wed Oct 3 15:50:47 2018, 00001605, D, Socket Server, Connection 34: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:47 2018, 00001604, D, Socket Server, Connection 34: Disconnecting
    Wed Oct 3 15:50:52 2018, 00001603, D, Socket Server, Connection 35: Connecting
    Wed Oct 3 15:50:52 2018, 00001605, D, Socket Server, Connection 35: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:52 2018, 00001604, D, Socket Server, Connection 35: Disconnecting
    Wed Oct 3 15:50:57 2018, 00001603, D, Socket Server, Connection 36: Connecting
    Wed Oct 3 15:50:57 2018, 00001605, D, Socket Server, Connection 36: Executing command [getdatabasestatus]
    Wed Oct 3 15:50:57 2018, 00001604, D, Socket Server, Connection 36: Disconnecting
    Wed Oct 3 15:51:02 2018, 00001603, D, Socket Server, Connection 37: Connecting
    Wed Oct 3 15:51:02 2018, 00001605, D, Socket Server, Connection 37: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:02 2018, 00001604, D, Socket Server, Connection 37: Disconnecting
    Wed Oct 3 15:51:07 2018, 00001603, D, Socket Server, Connection 38: Connecting
    Wed Oct 3 15:51:07 2018, 00001605, D, Socket Server, Connection 38: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:07 2018, 00001604, D, Socket Server, Connection 38: Disconnecting
    Wed Oct 3 15:51:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:51:12 2018, 00001603, D, Socket Server, Connection 39: Connecting
    Wed Oct 3 15:51:12 2018, 00001605, D, Socket Server, Connection 39: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:12 2018, 00001604, D, Socket Server, Connection 39: Disconnecting
    Wed Oct 3 15:51:17 2018, 00001603, D, Socket Server, Connection 40: Connecting
    Wed Oct 3 15:51:17 2018, 00001605, D, Socket Server, Connection 40: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:17 2018, 00001604, D, Socket Server, Connection 40: Disconnecting
    Wed Oct 3 15:51:22 2018, 00001603, D, Socket Server, Connection 41: Connecting
    Wed Oct 3 15:51:22 2018, 00001605, D, Socket Server, Connection 41: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:22 2018, 00001604, D, Socket Server, Connection 41: Disconnecting
    Wed Oct 3 15:51:27 2018, 00001603, D, Socket Server, Connection 42: Connecting
    Wed Oct 3 15:51:27 2018, 00001605, D, Socket Server, Connection 42: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:27 2018, 00001604, D, Socket Server, Connection 42: Disconnecting
    Wed Oct 3 15:51:32 2018, 00001603, D, Socket Server, Connection 43: Connecting
    Wed Oct 3 15:51:32 2018, 00001605, D, Socket Server, Connection 43: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:32 2018, 00001604, D, Socket Server, Connection 43: Disconnecting
    Wed Oct 3 15:51:38 2018, 00001603, D, Socket Server, Connection 44: Connecting
    Wed Oct 3 15:51:38 2018, 00001605, D, Socket Server, Connection 44: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:38 2018, 00001604, D, Socket Server, Connection 44: Disconnecting
    Wed Oct 3 15:51:43 2018, 00001603, D, Socket Server, Connection 45: Connecting
    Wed Oct 3 15:51:43 2018, 00001605, D, Socket Server, Connection 45: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:43 2018, 00001604, D, Socket Server, Connection 45: Disconnecting
    Wed Oct 3 15:51:48 2018, 00001603, D, Socket Server, Connection 46: Connecting
    Wed Oct 3 15:51:48 2018, 00001605, D, Socket Server, Connection 46: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:48 2018, 00001604, D, Socket Server, Connection 46: Disconnecting
    Wed Oct 3 15:51:53 2018, 00001603, D, Socket Server, Connection 47: Connecting
    Wed Oct 3 15:51:53 2018, 00001605, D, Socket Server, Connection 47: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:53 2018, 00001604, D, Socket Server, Connection 47: Disconnecting
    Wed Oct 3 15:51:58 2018, 00001603, D, Socket Server, Connection 48: Connecting
    Wed Oct 3 15:51:58 2018, 00001605, D, Socket Server, Connection 48: Executing command [getdatabasestatus]
    Wed Oct 3 15:51:58 2018, 00001604, D, Socket Server, Connection 48: Disconnecting
    Wed Oct 3 15:52:03 2018, 00001603, D, Socket Server, Connection 49: Connecting
    Wed Oct 3 15:52:03 2018, 00001605, D, Socket Server, Connection 49: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:03 2018, 00001604, D, Socket Server, Connection 49: Disconnecting
    Wed Oct 3 15:52:08 2018, 00001603, D, Socket Server, Connection 50: Connecting
    Wed Oct 3 15:52:08 2018, 00001605, D, Socket Server, Connection 50: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:08 2018, 00001604, D, Socket Server, Connection 50: Disconnecting
    Wed Oct 3 15:52:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:52:13 2018, 00001603, D, Socket Server, Connection 51: Connecting
    Wed Oct 3 15:52:13 2018, 00001605, D, Socket Server, Connection 51: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:13 2018, 00001604, D, Socket Server, Connection 51: Disconnecting
    Wed Oct 3 15:52:18 2018, 00001603, D, Socket Server, Connection 52: Connecting
    Wed Oct 3 15:52:18 2018, 00001605, D, Socket Server, Connection 52: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:18 2018, 00001604, D, Socket Server, Connection 52: Disconnecting
    Wed Oct 3 15:52:23 2018, 00001603, D, Socket Server, Connection 53: Connecting
    Wed Oct 3 15:52:23 2018, 00001605, D, Socket Server, Connection 53: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:23 2018, 00001604, D, Socket Server, Connection 53: Disconnecting
    Wed Oct 3 15:52:28 2018, 00001603, D, Socket Server, Connection 54: Connecting
    Wed Oct 3 15:52:28 2018, 00001605, D, Socket Server, Connection 54: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:28 2018, 00001604, D, Socket Server, Connection 54: Disconnecting
    Wed Oct 3 15:52:33 2018, 00001603, D, Socket Server, Connection 55: Connecting
    Wed Oct 3 15:52:33 2018, 00001605, D, Socket Server, Connection 55: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:33 2018, 00001604, D, Socket Server, Connection 55: Disconnecting
    Wed Oct 3 15:52:38 2018, 00001603, D, Socket Server, Connection 56: Connecting
    Wed Oct 3 15:52:38 2018, 00001605, D, Socket Server, Connection 56: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:38 2018, 00001604, D, Socket Server, Connection 56: Disconnecting
    Wed Oct 3 15:52:43 2018, 00001603, D, Socket Server, Connection 57: Connecting
    Wed Oct 3 15:52:43 2018, 00001605, D, Socket Server, Connection 57: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:43 2018, 00001604, D, Socket Server, Connection 57: Disconnecting
    Wed Oct 3 15:52:49 2018, 00001603, D, Socket Server, Connection 58: Connecting
    Wed Oct 3 15:52:49 2018, 00001605, D, Socket Server, Connection 58: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:49 2018, 00001604, D, Socket Server, Connection 58: Disconnecting
    Wed Oct 3 15:52:54 2018, 00001603, D, Socket Server, Connection 59: Connecting
    Wed Oct 3 15:52:54 2018, 00001605, D, Socket Server, Connection 59: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:54 2018, 00001604, D, Socket Server, Connection 59: Disconnecting
    Wed Oct 3 15:52:59 2018, 00001603, D, Socket Server, Connection 60: Connecting
    Wed Oct 3 15:52:59 2018, 00001605, D, Socket Server, Connection 60: Executing command [getdatabasestatus]
    Wed Oct 3 15:52:59 2018, 00001604, D, Socket Server, Connection 60: Disconnecting
    Wed Oct 3 15:53:04 2018, 00001603, D, Socket Server, Connection 61: Connecting
    Wed Oct 3 15:53:04 2018, 00001605, D, Socket Server, Connection 61: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:04 2018, 00001604, D, Socket Server, Connection 61: Disconnecting
    Wed Oct 3 15:53:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:53:09 2018, 00001603, D, Socket Server, Connection 62: Connecting
    Wed Oct 3 15:53:09 2018, 00001605, D, Socket Server, Connection 62: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:09 2018, 00001604, D, Socket Server, Connection 62: Disconnecting
    Wed Oct 3 15:53:14 2018, 00001603, D, Socket Server, Connection 63: Connecting
    Wed Oct 3 15:53:14 2018, 00001605, D, Socket Server, Connection 63: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:14 2018, 00001604, D, Socket Server, Connection 63: Disconnecting
    Wed Oct 3 15:53:19 2018, 00001603, D, Socket Server, Connection 64: Connecting
    Wed Oct 3 15:53:19 2018, 00001605, D, Socket Server, Connection 64: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:19 2018, 00001604, D, Socket Server, Connection 64: Disconnecting
    Wed Oct 3 15:53:24 2018, 00001603, D, Socket Server, Connection 65: Connecting
    Wed Oct 3 15:53:24 2018, 00001605, D, Socket Server, Connection 65: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:24 2018, 00001604, D, Socket Server, Connection 65: Disconnecting
    Wed Oct 3 15:53:29 2018, 00001603, D, Socket Server, Connection 66: Connecting
    Wed Oct 3 15:53:29 2018, 00001605, D, Socket Server, Connection 66: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:29 2018, 00001604, D, Socket Server, Connection 66: Disconnecting
    Wed Oct 3 15:53:34 2018, 00001603, D, Socket Server, Connection 67: Connecting
    Wed Oct 3 15:53:34 2018, 00001605, D, Socket Server, Connection 67: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:34 2018, 00001604, D, Socket Server, Connection 67: Disconnecting
    Wed Oct 3 15:53:39 2018, 00001603, D, Socket Server, Connection 68: Connecting
    Wed Oct 3 15:53:39 2018, 00001605, D, Socket Server, Connection 68: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:39 2018, 00001604, D, Socket Server, Connection 68: Disconnecting
    Wed Oct 3 15:53:45 2018, 00001603, D, Socket Server, Connection 69: Connecting
    Wed Oct 3 15:53:45 2018, 00001605, D, Socket Server, Connection 69: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:45 2018, 00001604, D, Socket Server, Connection 69: Disconnecting
    Wed Oct 3 15:53:50 2018, 00001603, D, Socket Server, Connection 70: Connecting
    Wed Oct 3 15:53:50 2018, 00001605, D, Socket Server, Connection 70: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:50 2018, 00001604, D, Socket Server, Connection 70: Disconnecting
    Wed Oct 3 15:53:55 2018, 00001603, D, Socket Server, Connection 71: Connecting
    Wed Oct 3 15:53:55 2018, 00001605, D, Socket Server, Connection 71: Executing command [getdatabasestatus]
    Wed Oct 3 15:53:55 2018, 00001604, D, Socket Server, Connection 71: Disconnecting
    Wed Oct 3 15:54:00 2018, 00001603, D, Socket Server, Connection 72: Connecting
    Wed Oct 3 15:54:00 2018, 00001605, D, Socket Server, Connection 72: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:00 2018, 00001604, D, Socket Server, Connection 72: Disconnecting
    Wed Oct 3 15:54:05 2018, 00001603, D, Socket Server, Connection 73: Connecting
    Wed Oct 3 15:54:05 2018, 00001605, D, Socket Server, Connection 73: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:05 2018, 00001604, D, Socket Server, Connection 73: Disconnecting
    Wed Oct 3 15:54:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:54:10 2018, 00001603, D, Socket Server, Connection 74: Connecting
    Wed Oct 3 15:54:10 2018, 00001605, D, Socket Server, Connection 74: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:10 2018, 00001604, D, Socket Server, Connection 74: Disconnecting
    Wed Oct 3 15:54:15 2018, 00001603, D, Socket Server, Connection 75: Connecting
    Wed Oct 3 15:54:15 2018, 00001605, D, Socket Server, Connection 75: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:15 2018, 00001604, D, Socket Server, Connection 75: Disconnecting
    Wed Oct 3 15:54:20 2018, 00001603, D, Socket Server, Connection 76: Connecting
    Wed Oct 3 15:54:20 2018, 00001605, D, Socket Server, Connection 76: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:20 2018, 00001604, D, Socket Server, Connection 76: Disconnecting
    Wed Oct 3 15:54:25 2018, 00001603, D, Socket Server, Connection 77: Connecting
    Wed Oct 3 15:54:25 2018, 00001605, D, Socket Server, Connection 77: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:25 2018, 00001604, D, Socket Server, Connection 77: Disconnecting
    Wed Oct 3 15:54:31 2018, 00001603, D, Socket Server, Connection 78: Connecting
    Wed Oct 3 15:54:31 2018, 00001605, D, Socket Server, Connection 78: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:31 2018, 00001604, D, Socket Server, Connection 78: Disconnecting
    Wed Oct 3 15:54:37 2018, 00001603, D, Socket Server, Connection 79: Connecting
    Wed Oct 3 15:54:37 2018, 00001605, D, Socket Server, Connection 79: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:37 2018, 00001604, D, Socket Server, Connection 79: Disconnecting
    Wed Oct 3 15:54:43 2018, 00001603, D, Socket Server, Connection 80: Connecting
    Wed Oct 3 15:54:43 2018, 00001605, D, Socket Server, Connection 80: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:43 2018, 00001604, D, Socket Server, Connection 80: Disconnecting
    Wed Oct 3 15:54:49 2018, 00001603, D, Socket Server, Connection 81: Connecting
    Wed Oct 3 15:54:49 2018, 00001605, D, Socket Server, Connection 81: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:49 2018, 00001604, D, Socket Server, Connection 81: Disconnecting
    Wed Oct 3 15:54:55 2018, 00001603, D, Socket Server, Connection 82: Connecting
    Wed Oct 3 15:54:55 2018, 00001605, D, Socket Server, Connection 82: Executing command [getdatabasestatus]
    Wed Oct 3 15:54:55 2018, 00001604, D, Socket Server, Connection 82: Disconnecting
    Wed Oct 3 15:55:01 2018, 00001603, D, Socket Server, Connection 83: Connecting
    Wed Oct 3 15:55:01 2018, 00001605, D, Socket Server, Connection 83: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:01 2018, 00001604, D, Socket Server, Connection 83: Disconnecting
    Wed Oct 3 15:55:07 2018, 00001603, D, Socket Server, Connection 84: Connecting
    Wed Oct 3 15:55:07 2018, 00001605, D, Socket Server, Connection 84: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:07 2018, 00001604, D, Socket Server, Connection 84: Disconnecting
    Wed Oct 3 15:55:08 2018, 00000905, D, Threat Info, Saved recovery state
    Wed Oct 3 15:55:13 2018, 00001603, D, Socket Server, Connection 85: Connecting
    Wed Oct 3 15:55:13 2018, 00001605, D, Socket Server, Connection 85: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:13 2018, 00001604, D, Socket Server, Connection 85: Disconnecting
    Wed Oct 3 15:55:19 2018, 00001603, D, Socket Server, Connection 86: Connecting
    Wed Oct 3 15:55:19 2018, 00001605, D, Socket Server, Connection 86: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:19 2018, 00001604, D, Socket Server, Connection 86: Disconnecting
    Wed Oct 3 15:55:25 2018, 00001603, D, Socket Server, Connection 87: Connecting
    Wed Oct 3 15:55:25 2018, 00001605, D, Socket Server, Connection 87: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:25 2018, 00001604, D, Socket Server, Connection 87: Disconnecting
    Wed Oct 3 15:55:31 2018, 00001603, D, Socket Server, Connection 88: Connecting
    Wed Oct 3 15:55:31 2018, 00001605, D, Socket Server, Connection 88: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:31 2018, 00001604, D, Socket Server, Connection 88: Disconnecting
    Wed Oct 3 15:55:37 2018, 00001603, D, Socket Server, Connection 89: Connecting
    Wed Oct 3 15:55:37 2018, 00001605, D, Socket Server, Connection 89: Executing command [getdatabasestatus]
    Wed Oct 3 15:55:37 2018, 00001604, D, Socket Server, Connection 89: Disconnecting

    • This reply was modified 4 years, 3 months ago by WebMaster.
    teliumcustomer4
    Member
    September 29, 2018 at 7:23 pm
    Post count: 3
    #6546
    Topic: Database command failed on write to eventlog table in forum General |

    I’m seeing this error in Event Log.

    Everything seems to work well, what can be wrong?


    Fri, 28 Sep 2018 22:03:18 +0000 Information Database Database closed
    Fri, 28 Sep 2018 22:03:18 +0000 Error Database Database command failed on write to eventlog table
    Fri, 28 Sep 2018 22:03:28 +0000 Information Database Database open for archiving
    Sat, 29 Sep 2018 18:36:48 +0000 Information Database Database closed
    Sat, 29 Sep 2018 18:36:48 +0000 Error Database Database command failed on write to eventlog table
    Sat, 29 Sep 2018 18:36:56 +0000 Information Asterisk Controller Connection established to AMI
    Sat, 29 Sep 2018 18:36:57 +0000 Information General SecAst state changing to protecting
    Sat, 29 Sep 2018 18:36:58 +0000 Information Database Database open for archiving

    thanks

    • This topic was modified 4 years, 3 months ago by WebMaster.
    Telium Support Group
    Moderator
    September 16, 2018 at 7:38 pm
    Post count: 263
    #6756 In reply to: Failed dependencies during qt5-base installation |

    There’s the problem: you are running a derivative of Red Hat 6 yet the rpm command you issued above was trying to install a package designed for Red Hat 7. That’s why you got the GLIBC error.

    If you google how to add EPEL to your distro (CentOS 6) you will find detailed instructions; or try this link: https://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ That will make installation of qt5 (and other non-core packages) easier.

    If you want to install a single package directly from a repo (as you did above), you can do so but ensure you are using CentOS 6 repo. (Not CentOS 7).

    teliumcustomer5
    Member
    September 16, 2018 at 5:27 pm
    Post count: 3
    #6787 In reply to: Failed dependencies during qt5-base installation |

    There is it:

    [root@ASTERISK01 ~]# cat /etc/redhat-release
SHMZ release 6.6 (Final)

    How can I do about the EPEL? I tried picking using ‘yum’ and i can’t do it.

    [root@ASTERISK01 ~]# yum install epel
Loaded plugins: fastestmirror, kmod
Setting up Install Process
Loading mirror speeds from cached hostfile
No package epel available.
Error: Nothing to do
[root@ASTERISK01 ~]# yum install EPEL
Loaded plugins: fastestmirror, kmod
Setting up Install Process
Loading mirror speeds from cached hostfil
No package EPEL available.
Error: Nothing to do

    Tks

    Telium Support Group
    Moderator
    September 16, 2018 at 11:31 am
    Post count: 263
    #6786 In reply to: Failed dependencies during qt5-base installation |

    I suspect you are mixing incompatible packages. I’m guessing that your OS is redhat based. Please post the output of:

    cat /etc/redhat-release

    Instead of manually picking packages from various repo’s on the internet you may wish to add a comprehensive repo like EPEL which has all of these packages available. (Assuming your OS distro is compatible)

    teliumcustomer5
    Member
    September 15, 2018 at 10:40 pm
    Post count: 3
    #6544
    Topic: Failed dependencies during qt5-base installation in forum Installation & Upgrade |

    I want to install the HAAst on my AsteriskNOW FreePBX environment at home. I’m reading the pdf about the detailed installation and I stopped in the page about “Install prerequisite packages”. But I cannot install the packages qt5-qtbase package and qt5-qtbase-mysql because the OS needs of the library’s below:

    [root@ASTERISK01 ~]# ldd /usr/local/haast/haast
linux-vdso.so.1 =>  (0x00007ffdb1de7000)
libQt5Network.so.5 => not found
libQt5Xml.so.5 => not found
libQt5Sql.so.5 => not found
libQt5Core.so.5 => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5a45a86000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f5a45780000)
libm.so.6 => /lib64/libm.so.6 (0x00007f5a454fc000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f5a452e5000)
libc.so.6 => /lib64/libc.so.6 (0x00007f5a44f51000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5a45cb1000)

    How can I install the libraries above? I tried the command “yum install glibc” and the OS doesn’t find anything relationed.

    Thanks very much.

    Telium Support Group
    Moderator
    August 14, 2018 at 3:36 pm
    Post count: 263
    #6777 In reply to: USB license on Hyper-V guest |

    In order to connect a USB device to a Hyper-V guest you need to use a USB over IP solution. This means you plug the USB device into a real (physical) device(possibly even the Hyper-V host) and then attach it to the guest over a network (IP) connection.

    For example, there are software packages which will share a USB device over an IP connection:
    Locally attached USB over IP

    Example packages include:

    Note that the free solution may already be rolled into your Linux kernel (so you don’t need to install anything on the guest).

    There are also commercial hardware products which will share a USB device over an IP connection:
    Network attached USB over IP

    Example devices include:

    Some clients have used a Raspberry Pi to create a USB device server on their network for USB keys and other devices shared across their data center.

    We try to avoid endorsing third party products unless we continually test their product with our dongles (which we do not at this time), but we have been told by customers that they have had success with a couple of the software packages above.

    • This reply was modified 4 years, 3 months ago by WebMaster.
    • This reply was modified 4 years, 3 months ago by WebMaster.
    • This reply was modified 4 years, 3 months ago by WebMaster.
    • This reply was modified 4 years, 3 months ago by WebMaster.
    • This reply was modified 4 years, 3 months ago by WebMaster.
    Telium Support Group
    Moderator
    August 11, 2018 at 10:18 am
    Post count: 263
    #6775 In reply to: AMI connection issue at startup |

    Distribution type 11 would be correct for your setup, so that’s not the problem. I would focus solely on ensuring HAAst can start your FreePBX instance properly. The problem could even be that FreePBX is starting but shutting down with an error code, or is getting severely delayed (see Sangoma notes on very slow FreePBX startup) causing HAAst to treat the startup as failed.

    I would suggest you look at:

    1. Try to start/stop the FreePBX service using systemctl from the commandline. Does Asterisk start/stop properly with it?
    2. Confirm permissions on FreePBX and Asterisk resources, relative to who you are logged in as (and relative to root)
    3. Start FreePBX using the commands within the systemd service script directly to look for errors
    4. Look for FreePBX startup errors
    5. Look for severe FreePBX startup delays (and follow Sangoma wiki instructions on correcting very slow startup if necessary)
    teliumcustomer6
    Member
    August 11, 2018 at 6:09 am
    Post count: 3
    #6768 In reply to: AMI connection issue at startup |

    1. I am using the proprietary “FreePBX Distro” version 14. In HAAst I am using option 11. I tried option 8 with the same result, option 2 doesn’t generate any error but obviously I have other kind of problem with my distro choice.
    2. I have obfuscated the ip address , I am using two different ip for Management and voip.
    3. This is clear now. I didn’t realize that “snooze” was related to the [cluster] stanza.
    4.I will look into this as soon as I have HAAst running smoothly.

    At this point I am not sure why there is this error

    Fri Aug 10 06:47:42 2018, 00000721, E, System Command, Failed to start Asterisk (start) wrapper. Run result 3; exitcode 0

    As per the install guide the correct option is 11.

    Telium Support Group
    Moderator
    August 11, 2018 at 1:46 am
    Post count: 263
    #6774 In reply to: AMI connection issue at startup |

    You have a number of issues:

    1. The following error in your event log indicates that HAAst is unable to successfully start Asterisk (and/or FreePBX services).


    Fri Aug 10 06:47:42 2018, 00000721, E, System Command, Failed to start Asterisk (start) wrapper. Run result 3; exitcode 0

    What have you set your ‘distribution’ key to in the [asterisk] stanza of your haast.conf file? Are you running the fully open source version of FreePBX or proprietary (FreePBX ‘distro’)? If open source, on what Linux distro and architecture?
    This error indicates Asterisk is not being started (properly), and also explains why you aren’t getting an AMI connection error. (Error 0 means HAAst could not establish a connection to the AMI)

    2. The follow errors in your event log suggest your PeerLinkServer is listening on the same IP that you are using for the dynamic HAAst created interface:


    Fri Aug 10 06:46:56 2018, 00001901, I, Peer Link Server, PeerLinkServer listening on 12.34.56.78:3002
    Fri Aug 10 06:47:10 2018, 00010106, I, NIC, IP address ‘12.34.56.78’ added to physical NIC device ‘eth0’ as new virtual NIC device ‘eth0:haast’

    Have you obfuscated the IP addresses in your posting? If not you will need to fix your IP addresses (which may also prevent Asterisk from Starting depending on the FreePBX settings).

    3. The reason you see snoozing messages relates to the promotesnoozetime and demotesnoozetime keys in the [cluster] stanza of haast.conf. This has nothing to do with your problem – in fact I suggest you leave those settings at default until you understand HAAst a little better. As background, these settings prevent the cluster from flipping back and forth in the event that it takes Asterisk some time to stabilize. (See https://telium.io/topic/manual-failover-leads-to-brief-dual-active-contention/ for more info).

    4. HAAst does not interact with firewalld or iptables, so that symptom isn’t directly related to HAAst. However, beware that Songoma calls fail2ban a ‘security system’ – when in fact it’s not. Actually Digium warns companies NOT to use fail2ban as a security system (see https://telium.io/topic/i-use-fail2ban-why-do-i-need-secast/ for more info). I suspect FreePBX is trying to start fail2ban and that is giving you the error messages. If you are anything but a small/SOHO business have a look at the SecAst pages on this site to understand the different between SecAst and fail2ban.

    With more info we can provide more suggestions but hopefully that clarifies the meaning of the messages. I suspect all of the above relate to starting FreePBX.

    • This reply was modified 4 years, 3 months ago by WebMaster.
  • Author
    Search Results
Viewing 15 results - 31 through 45 (of 113 total)
Previous 1 2 3 4 … 6 7 8 Next