OpenKB::Server Technical Papers

Error
ejabberdctl status
RPC failed on the node ejabberd@localhost: nodedown

This occurred when using a live cd in a virtual player under bridge mode. The app loads after a virtual player reboot, but restarting the service within ssh returned the error. So I did a hard reboot on the host machine which resolve the issue.

You will also need to make sure the host name is correct in the ejabberd cfg file.

Error

JAuthentication::__construct: Could not load authentication libraries.

solution..

Make sure the authentication plugin is enabled ..
in the Joomla database, and changed it’s published status to 1 in the “jos_plugins” table.

Brown Bear software

error:
Software error: Can’t locate Calendar/CalciumStart.pm in @INC (@INC contains: CalciumDir40/upgrades CalciumDir40/redist …

Solution:
A message like this means that Calcium can’t find its installation directory. The location of the Calcium source code files and data directory are specified in the main Calcium script; some installations will require the full path to the Calcium installation directory here, instead of a relative path. To fix this, edit the main script (Calcium40.pl), and change the line near the top that looks like this:
BEGIN {$Defines::calendar_root = ‘CalciumDir40′}
Replace CalciumDir40 with the full filesystem path to that directory. For example, something like:
BEGIN {$Defines::calendar_root = ‘C:\public\html\cgi-bin\CalciumDir40′}
or maybe
BEGIN {$Defines::calendar_root = ‘/usr/local/apache/cgi-bin/CalciumDir40′}
should help.

Make sure you have vim-enhanced installed

Run
yum install vim-enhanced

or within vi
:syntax on

Generate key on local machine

ssh-keygen -t rsa

It will ask you for a password but you can leave it blank.

Note you could also pick -t dsa if you prefer.

Ensure that the remote server has a .ssh directory

Make sure the server your connecting to has a .ssh directory in your home
directory. If it doesn’t exist you can run the ssh-keygen command above, and
it will create one with the correct permissions.

Copy your local public key to the remote server

If your remote server doesn’t have a file called ~/.ssh/authorized_keys2
then we can create it. If that file already exists, you need to append to it
instead of overwriting it, which the command below would do:
scp ~/.ssh/id_rsa.pub remote.server.com:.ssh/authorized_keys2

Now ssh to the remote server

Now you can ssh to the remote server without entering your password.