I recently setup a Cassandra environment for a customer, the easiest approach was to utilize the DataStax Yum repository which is detailed below. As detailed previously there is a compatability issue with the OpenJDK default in CentOS so first follow my previous post on installing the Oracle JDK.
As root create /etc/yum.repos.d/datastax.repo:
name= DataStax Repo for Apache Cassandra
- To install Cassandra, for Apache Cassandra 1.2.x:
sudo yum install cassandra12
- Install a copy of JNA jar just for Cassandra
Note: JNA from base repo is 3.2.4 while Cassandra requires 3.2.7+
sudo wget https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/3.5.1/jna-3.5.1.jar
sudo chown cassandra:cassandra jna-3.5.1.jar
sudo chown 755 jna-3.5.1.jar
- Fix permissions
sudo chown -R cassandra:cassandra /var/lib/cassandra
sudo chown -R cassandra:cassandra /var/log/cassandra
- Create /etc/profile.d/cassandra.sh
- Load into current session:
- Edit the following settings in /etc/cassandra/conf/cassandra.yaml:
- seeds: ""
Note: for more details about configuring and optimizing a multi-node cluster, see sources.
- Open ports
7199 for JMX
9160 for Cassandra Thrift
7000 for Cassandra Gossip
- Start cassandra:
sudo service cassandra start
- Start cassandra on boot:
sudo chkconfig cassandra on
I encountered an issue recently where the four Cisco Aironet wireless access points deployed at a bus depot in South Yorkshire were not providing sufficient coverage and data downloads from the buses not completing, despite all tests showing it should be excellent.
After some frustration I eventually discovered that some (all?) TGX150 ticket machines are equipped with US and not EU wireless chipsets which means they only work with channels 1-11 and not 1-13 as one would expect in the UK.
If you have having issues with your depot wireless LAN and TGX150 data download I would recommend checking what channels the access points are configured to operate on and adjust accordingly.
Continuing my experience of migrating from Windows Server 2003 to Windows Server 2012 Essentials I came across a problem configuring the Email Alert Notification. In Small Business Service the SMTP server would be the same machine, however with Exchange cloud hosting on Office 365 this isn’t as straight forward and you must configure an SMTP relay instead as follows:
Step 1: Obtain the SMTP server setting
To obtain the SMTP server setting, follow these steps:
- Sign in to Outlook Web App.
Take one of the following actions:
In Office 365, click Settings , and then click Options.
In Office 365 pre-upgrade, click Options, and then click See All Options.
- Take one of the following actions:
In Office 365, in the left navigation pane, click Account, and then click Settings for POP and IMAP access.
In Office 365 pre-upgrade, in the left navigation pane, click Account, click My Account, and then, in the Account Information area, click Settings for POP, IMAP, and SMTP access.
Note the SMTP server setting information that’s displayed on this page.
Step 2: Create a user who has an Exchange Online mailbox
To do this, use one of the following methods:
- If you’re in a hybrid deployment or if you’re using directory synchronization, create the user in Active Directory, Exchange Management Shell, or either Exchange Management Console or Exchange Admin Center (depending on your version of Exchange Server). Run directory synchronization, and then activate the user by using an Exchange Online license.
- Note The user must not have an on-premises mailbox.
Create the user by using the Office 365 portal or by using the Windows Azure Active Directory Module for Windows PowerShell, and then assign the user an Exchange Online license.
Step 3: Set up the Internet Information Services (IIS) SMTP relay server
To set up Internet Information Services (IIS) so that your LOB programs can use the SMTP relay, follow these steps, as appropriate for your situation.
- Start Server Manager, click Features, and then click Add Features.
- On the Select Features page, select the SMTP Server check box. If you’re prompted, click Add Required Role Services. Note This step automatically installs all prerequisite roles and features, including IIS (if they’re not already installed).
- On the Select Features page, click Next. Then, on the Web Server (IIS) page, click Next.
- On the Select Role Services page, make sure that the following role services check boxes are selected, and then click Next:
The ODBC Logging check box under Health and Diagnostics
The IIS Metabase Compatibility check box in IIS 6 Management Capability under Management Tools
The IIS 6 Management Console check box in IIS 6 Management Capability under Management Tools
- On the Confirm Installation Selections page, click Install.
- After the SMTP Server installation is completed, click Finish.
- Open IIS 6.0 Manager, right click Default SMTP Virtual Server, and then click Properties.
- Click the Access tab, and then click Relay.
- In the Select which computers may relay through this virtual server area, click Only the list below, and then enter the IP addresses of the on-premises LOB devices and application servers that will relay through the SMTP server.
Warning Make sure that you enter only the IP addresses of the devices and servers that you trust. This setting lets you relay mail that’s coming from these sources to any destination. In effect, this makes the on-premises server that’s running IIS an open relay.
- On the Access tab, click Authentication, make sure that the Anonymous access check box is selected, and then click OK.
- Click the Delivery tab, click Advanced, and then, under Smart host, enter the fully qualified domain name (FQDN) of the SMTP server from the “Step 1: Obtain the SMTP server setting” section.
- On the Delivery tab, click Outbound Connections.
- In the TCP Port box, type 587, and then click OK.
- On the Delivery tab, click Outbound Security, and then follow these steps:
Click Basic Authentication.
In the User name box, type the user name of the Office 365 user that you created in the “Step 2: Create a user who has an Exchange Online mailbox” section.
In the Password box, type the password of the Office 365 user.
Select the TLS encryption check box, and then click OK.
So now I have now been without working hot water on my new boiler since 21st December. This is unexpected as our boiler was only fitted in February, but ‘luckily’ it came with 2 years Warmsure cover – or so I thought.
After an engineer visit on the 23rd December, just to diagnose the issue and not do anything further and numerous further phone calls to chase the repair we were told it’s a van stocked part and would be fixed on the 3rd January.
So the engineer turned up, but didn’t phone in advance like he was suppose to and as only he was a contractor so didn’t carry the part and he wasn’t allowed to aquire one from a plumbers merchants. So more waiting till a part is ordered and another engineer is dispached..
Worse part is the engineer manually moved the diverter valve so we could get hot water, however central heating which did work is no longer working..genius..
Good deal on at the moment for Domino’s Pizza, £10 off a spend £25 or more when using the code YAKBYWBX.
I know what I will be having Saturday as a takeaway…
Well, I’ve finally taken the plunge and set up a blog, look forward to more interesting postings…