Posts tagged ‘Linux’

Simpana 9 – Determine Unix Log and Install location

Another video clip from a demo/information series I put together. This one talks about how to find your Simpana 9 Unix Log and Install Location.

Atlassian Confluence and NGINX

I’ve always been an apache guy, but I thought it might be good to get NGINX going at home on some lower spec machine and have it forward http requests to other hosts where they can be served.

I finally got my Atlassian Confluence install going at home again, so I thought perfect time to install NGINX and configure it to be the frontend for the requests. Just like my previous post here. I want NGINX to listen on http (tcp/80) for a certain vhost name and forward those requests to my confluence install else where on my network running on the default 8090 port.

Create new site, example of my configuration below;

Filename: /etc/nginx/sites-available/confluence
File Contents:

server {
    listen 80;
    server_name wiki.heimic.net wiki;
    location / {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://192.168.33.25:8090;
    }
}

Now you should link this site file into /etc/nginx/sites-enabled as the same name and restart nginx.

If your dns for wiki.heimic.net and wiki in my example point to the NGINX host, they will forward to 192.168.33.25 on port 8090. Which is where my confluence would be running. Be sure to update confluence site name to match the vhost being used.

Simple as that, bit of a different take on the example Atlassian provide over here.

Screenly OSE on Raspbery Pi demo

This post is a follow up to my previous one about using an Raspberry Pi as an Information Display, as found here.

I wanted to capture some videos that show what the output looks like on a TV when the Raspberry Pi boots for the first time and what the assets look like as they get displayed.

Below is two videos (both available in 720p) that will help demonstrate this. The first is the Raspberry Pi being booted.

The other clip shows the assets being displayed post the splash screen being displayed. I have a shortened video clip being displayed of a 1920×1080 movie trailer, followed by 2 test pictures.

The web interface to administer the Screenly OSE application is shown below.

Raspberry Pi as an Information Display

A few months back I was looking for a device that could display an image, a webpage and/or a video.

I had also been playing around with having a Raspberry Pi to perform this task, since it has HDMI out and they were fairly well priced. I thought this would make an excellent platform for what I needed.

I did some research and came up with some possible solutions and even tinkered with some of those options.

Eventually I settled on an application called Screenly which runs on the Raspbian distribution, or you can download a pre-made image for it. Screenly is a commercial application which has many added benefits, however has a price tag associated with it.

I noticed that they still make the Screenly OSE edition available and it did everything I needed, and what I imagine many small businesses would also want to use (who might not otherwise already have an information display).

Screenly OSE is the open source edition and is free.

Whats needed:

  • Raspberry Pi (recommend using Model B 512MB edition)
  • 8GB SD-Card
  • USB power lead
  • HDMI lead

Installation:

Install Raspbian onto the 8GB SD-Card (as downloaded from here). The procedure to perform this should be followed from the same website.

Boot the Raspbian SD-Card in your Raspberry Pi and follow the process/procedure as outlined here. Follow process under Option 2. This will enable you to install the Screenly OSE application and other dependent software.

Configuration:

If everything goes well, the Raspberry Pi when booted will pickup a DHCP address via the network port. This IP address is displayed during the boot of the Raspberry Pi. At which point you can access it via the http://aaa.bbb.ccc.ddd:8080 address. This is the management interface to the Information Display so you can add your assests. i.e. Images, Web URL and/or Video.

Please note that it only supports the following media types:

Screenly currently three types of media:

  • Videos (Screenly uses omxplayer as the video back-end. It is currently limited to MP4/h264-encoded videos.)
  • Images
  • Web-pages

Please note that Adobe Flash media is not, and will most likely never be, supported. Also, images and web-pages will be rendered in 1920×1080, so adjust your content for this size.

Post my successfully testing, I’ve subsequently gone on to configure two (2) Raspberry Pi’s running Raspbian and Screenly OSE within a business environment which render assests that include web pages and images. These have been running fine with little to no manual intervention since install. Over 45+ days uptime on the units.

I’ll post a video showing the boot sequence of a Rasberry Pi running Screenly OSE and it displaying some test assets in the next few weeks.

If you’d like more information and/or assistance with the installation of a Screenly OSE on a Raspberry Pi for your business (or organisation etc) you should contact me via the page here. This way I can quote you on a complete setup including/excluding hardware, and/or just consult you on part of the work etc.

HP Microserver N40L with Ubuntu 12.04.x and LXC

What a weekend, after killing off the setup I had working really well and trying out some other options. I came to the conclusion very quickly that the setup I had was the best one.

Our HP Microserver N40L with Ubuntu 12.04.x and LXC (Linux Containers) worked best for us. We have our mdadm based software raid, and have Linux containers do other services as needed.

So I am in the process of reinstalling everything back as it was, I am very glad I made good notes for most things including LXC.

If anyone want’s more explicit details, let me know in the comments and I can post further follow ups with more details on what we do and how we are doing it.

XPEnology and HP Microserver N40L

As per my previous post here. I got it all installed and most things work as expected, however I just cant bring myself to keep it. As some features don’t work like wake on lan etc.

So it was a short lived installation, however very impressed with what has been done to allow it to be possible to install.

I guess it suits some people, however just doesn’t suit me with the limitations.

XPEnology DSM 4.2 on HP N40L Microserver

I’d previously heard about Synology NAS software being recompiled to work on other native x86 platforms. I also heard you could put it on the HP N40L Microserver.

So I thought it might be worth looking at, as I really do like Synology NAS gear and the software that runs them. In fact have owned two Synology devices in the past, and will certainly be buying some multi bay units in the future.

I really just want my Microserver to do basic raid file sharing via cifs and nfs. I also don’t want to have to configure it via cli, as I just want to click a few things and get it working.

Long story short, I downloaded the XPEnology DS3612x DSM 4.2 build 3211++ (repack v1.2) and sure enough it works great. You can download it from the forum post here.

If you don’t know how to install it, do a bit of a google and you should find a few pages that will walk you through it, be sure to have drives in the Microserver ready to be formatted, as the installation will do that soon as you upload the pat file via Synology Assistant.

Will post back further thoughts once I reinstall it after I have copied off my data from my existing 3 x 2Tb raid5 array.

xpenology-web-logon

MediaWiki page edit issues on shared hosting provider

It appears I am still having MediaWiki page edit issues on my shared hosting provider. It appears that when you edit a page (can be any page) and insert the wiki syntax for the page. When you attempt to save it, something must be going wrong with the parsing of the content, as the edit of the page will fail as per the screen grab below.

Unable to resolve this, and do not want to waste any more time on resolving it. No errors are even displayed in error logs for the web server itself and the permissions are fine.

mediawiki-1.21.2-page-edit-save-shared-hosting

Mediawiki site generating Warning: Invalid argument supplied for foreach() in LocalisationCache.php on line 390

Had to blog about this, as I had a problem with one of my MediaWiki sites that I moved onto a shared hosting provider.

Every page when loaded would generate the error below displayed somewhere on the page. i.e in my case at the top in my header region.

Warning: Invalid argument supplied for foreach() in /path/to/file/includes/cache/LocalisationCache.php on line 390

The fix for this is easy, just run the rebuildLocalisationCache.php script in maintenance folder and if you don’t have access to run it via a shell you can add the following line into your LocalSettings.php file instead;

$wgLocalisationCacheConf['manualRecache'] = true;

Check out the page here for more specific details on the script use etc.

RasPBX, FreePBX Trunk setup for MyNetFone

As per my previous posts, I use MyNetFone as my SIP provider and I run a Raspberry Pi with RasPBX (which is FreePBX for the Raspberry Pi ready to install/tweak and configure).

Below is a quick run down on how you can configure your SIP Trunk for MyNetFone on this device, which is working for me currently.

General Settings:

Trunk Name: mynetfone
Outbound CallerID: [configure based on your 09nnnn number or your DID if you have one]

Outgoing Settings:

Trunk Name: mynetfone-sip-out
Peer Details: (as below)
disallow=all
allow=alaw&ulaw
authname=09nnnn
canreinvite=no
dtmfmode=rfc2833
fromuser=09nnnn
host=sip00.mynetfone.com.au
insecure=very
nat=yes
pedantic=no
qualify=yes
secret=password
type=friend
username=09nnnn

Registeration String:

09nnnn:password@sip00.mynetfone.com.au/09nnnn