Posts

Showing posts from June, 2012

Fixing libdbus in 64 bit RPM based linux (Centos, SL, Fedora)

Issue affects Firefox, Thunderbird, gEdit etc. You will see an error: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file or directory most likly you have a 32 bit version of dbus libraries installed. To fix that you need to install 64 version as well: yum install dbus-libs.x86_64 Provided by: ForthScale systems, Cloud experts

Instalation of Nomachine NX server or VNC server on Centos 5

Both tools are great to enable external GUI remote access on Linux. To install NX Free server : Note. Installation of NX Server requires installation of all three packages: client, node and server due to tools and libraries dependencies. Download the packages from Nomachine: wget http://64.34.161.181/download/3.5.0/Linux/nxclient-3.5.0-7.x86_64.rpm wget http://64.34.161.181/download/3.5.0/Linux/nxnode-3.5.0-9.x86_64.rpm wget http://64.34.161.181/download/3.5.0/Linux/FE/nxserver-3.5.0-11.x86_64.rpm Install the packages: rpm -i nxclient-3.5.0-7.x86_64.rpm rpm -i nxnode-3.5.0-9.x86_64.rpm rpm -i nxserver-3.5.0-11.x86_64.rpm VNC server installation: yum install vnc-server yum install xorg* (you need to install those for VNC fonts) Provided by: ForthScale systems, Cloud experts

Adding KDE Environment to Centos 5

List installation packs on your CentOS 5 machine: yum grouplist Install KDE yum groupinstall "KDE (K Desktop Environment)" Now you might want to enable GUI remote access with either: VNC server or Nomachine NX. Provided by: Forthscale systems, Cloud experts

adding support for TCP socket proxy with Nginx

Install needed prerequisites: apt-get install build-essential checkinstall apt-get build-dep nginx apt-get source nginx Check out TCP sockets patch for nginx from git repository: git clone  https://github.com/yaoweibin/nginx_tcp_proxy_module.git Patch your nginx source code: cd nginx-1.1.19/ patch -p1 < ../nginx_tcp_proxy_module/tcp.patch Now configure and build a new package: ./configure \ --add-module=../nginx_tcp_proxy_module/  \ --conf-path=/etc/nginx/nginx.conf  \ --error-log-path=/var/log/nginx/error.log  \ --pid-path=/var/run/nginx.pid  \ --lock-path=/var/lock/nginx.lock  \ --http-log-path=/var/log/nginx/access.log  \ --with-http_dav_module  \ --http-client-body-temp-path=/var/lib/nginx/body  \ --with-http_ssl_module  \ --http-proxy-temp-path=/var/lib/nginx/proxy  \ --with-http_stub_status_module  \ --http-fastcgi-temp-path=/var/lib/nginx/fastcgi  \ --with-debug  \  --with-http_flv_module \ --prefix=/usr \ --sbin-path=/usr/sbin/nginx  make you will end w

Fixing SSH Daemon - Authentication refused: bad ownership or modes for directory

Then you are unable to connect to your ssh server with your PEM (or PPK) key with connection refused message check the /var/log/auth.log file. If you see something similar to: sshd: Authentication refused: bad ownership or modes for directory /Your/Home/Path You have a home directory permission problem. change to that user if not already one and execute: chmod go-w ~/ chmod 700 ~/.ssh chmod 600 ~/.ssh/authorized_keys  It will restore your permissions and you should be able to connect.  Provided by: SiQ systems, Cloud experts
Couple of simple steps to debug munin plugins First check if munin recognize the plugin. Execute munin plugin in regular mode: munin-run plugin_nam e you will get output in format of: some.value XX then execute munin plugin in configuration mode: munin-run plugin_name config you will get output in format of: graph_title Great Plugin graph_args --upper-limit 100 -l 0 graph_vlabel % graph_category some_category graph_info This is the best munin plugin ever. something.label LABEL If you have any problems they can be related to the plugin having a permission problem. Next step is to test the plugin connection via port 4949 Run a telnet on munin node port 4949 telnet munin-node.example.com 4949 You will get output in format of: Trying munin-node.example.com... Connected to munin-node.example.com. Escape character is '^]'. # munin node at munin-node.example.com then type in console: fetch plugin_name or fetch plugin_name config It will output something similar to munin-run . Th