Aug 19 2020
By default Apache logs all requests. Sometimes you need to exclude logging of certain requests from Apache‘s access.log. For example some automated requests coming and flood your log distorting your statistics. This short guide shows how you use Apache’s SetEnvIf directive to prevent Apache from logging such requests.
Aug 12 2020
In default Tomcat installation, you will find the following line at the top of Tomcat‘s global server configuration file server.xml :
|
1 |
<Server port="8005" shutdown="SHUTDOWN"> |
This configuration allows remote shutdown of Tomcat by sending telnet command to port 8005. Something to note:
1. Port 8005 is on TCP protocol. This is important for firewall configuration
2. Port 8005 must be available for Tomcat to start. Use “netstate -an | grep 8005 | grep LISTEN” to confirm prior of Tomcat startup
3. The shutdown command is configurable, and case sensitive. In this default configuration (as above), it must be uppercase SHUTDOWN. It can be configured to other value if there is a security concern.
4. If port number is -1, then remote shutdown is disabled
Following steps illustrate how to shutdown Tomcat remotely (I will login directly to Tomcat server and shut it down by telnet) Continue reading
Aug 04 2020
At some moment Jira app stopped responding. When I stopped and started it Jira failed to start with:
JIRA Startup Failed You cannot access JIRA at present. Look at the table below to identify the reasons Description Unable to clean the cache directory: /opt/jira/plugins/.osgi-plugins/felix
In catalina.out log there were following lines:
|
1 2 |
2020-08-04 11:09:09,183 JIRA-Bootstrap ERROR [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked. com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: /data/jira/plugins/.osgi-plugins/felix |
and
|
1 2 |
2020-08-04 11:09:09,183 JIRA-Bootstrap ERROR [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked. com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: /data/jira/plugins/.osgi-plugins/felix |
There are two known causes for this issue: Continue reading
Jul 29 2020
Upon trying to start Oracle database service I got the following ORA-09925 error in $DB_HOME/startup.log file
|
1 2 3 4 |
SQL> Connected to an idle instance. SQL> ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 2: No such file or directory Additional information: 9925 |
The same ORA-09925 error when I tried to log on to SQL*Plus. Continue reading
Jul 22 2020
This article will cover the process of IAX clients configuration in Asterisk.
There are three authentication methods that are supported: MD5, plaintext and RSA. The least secure is “plaintext”, which sends passwords cleartext across the net. “md5” uses a challenge/response md5 sum arrangement, but still requires both ends have plain text access to the secret. “rsa” allows unidirectional secret knowledge through public/private keys. If “rsa” authentication is used, “inkeys” is a list of acceptable public keys on the local system that can be used to authenticate the remote peer, separated by the “:” character. “outkey” is a single, private key to use to authenticate to the other side.
Public keys are named /var/lib/asterisk/keys/<name>.pub while private keys are named /var/lib/asterisk/keys/<name>.key. Private keys should always be 3DES encrypted. Continue reading
Jul 22 2020
This error is usually caused by a username/secret/type mismatch.
This error also occurs when the context requested in the incoming call is different from one in the section of incoming peer. Multiple contexts in the peer section can be defined. Continue reading
Jul 22 2020
This article explains the process that Asterisk uses to authenticate incoming and outgoing IAX2 connections. Reference to “type=user” in the text below should be assumed to include “type=friend” as well, since a friend can act as a user. The same assumption holds for “type=peer” references below. Continue reading
Jul 17 2020
The FreePBX Distro has some built in features to allow you to change the Major Asterisk version you are using without reinstalling/recompiling it manually.
For example the 6.12.65 release track supports Asterisk 1.8, 11, 12 and 13, FreePBX 14 supports Asterisk 13,15,16 and 17.
To change Asterisk version in FreePBX in Linux command prompt type: Continue reading
Jul 08 2020
Once you successfully completed hybrid connectivity between your Skype for Business on-premises and Office 365 you should be ready to migrate your users to Skype for Business Online or Microsoft Teams.
In this article it will be showed how to migrate users to Microsoft Teams or Skype for Business Online. Continue reading
Jul 02 2020
To make a long story short I wrote this is quick guide on configuring hybrid connectivity between Skype for Business Server and Office 365.
It is based on this TechNet article:
https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/configure-hybrid-connectivity
It is assumed that your Skype for Business deployment is fully functional. Continue reading
