Here, I was able to setup Huawei E1552 SMS Gateway in Raspbian using SMSTools3.
- Install/Burn Raspbian to your microsd card. Instructions here.
- After burning/installing the image to your SD card. Install it to your Raspberry PI and configure it so you can SSH into it properly. Sadly, SSH daemon is not automatically configured to start on boot.
- To Enable SSH to autostart on boot… do
:> update-rc.d ssh defaults
:> update-rc.d ssh enable
- Restart and try to login remotely
- If you can not login, sshd may be configured to deny any remote root connection
- Got to /etc/ssh/ and edit sshd_config
- Look for this line…
- And change it to…
Had a problem after an update that when I force a restart or a shutdown on my server, it hangs on the last part of the process.
To fix my problem, I had to edit the /etc/default/grub config file and added acpi=force apm=power_off to the config line, between the double quotation marks…
do a update-grub after saving then reboot one more time.. ( force sa restart when it hangs )
After the restart, try another reboot, it should work now without hanging.
Source of the fix is from Here
I wanted to setup my own Git repository locally and with an accompanying front end GUI. Before Gitorious, I installed Git from scratch and also installed Gitolite. That will be another post later on.
Initially I followed the script from http://blog.kyodium.net/2011/09/install-gitorious-on-ubuntu-1104.html but its based on Ubuntu 11.04, there are some missing packages that was not part of the installation script so I had to run the script manually and jump from one tutorial to the other, but the main flow I used is from that script. This is the documentation of the installation process.
Note: I added the PPA to Git’s updated source so I would be using their latest release not Ubuntu’s Git package. ( Google around for Git’s PPA repository, its easy enough 😉 )
Also I was not logged into root ( which I prefer, so I had to do a lot of sudo-ing =S )
Execute these line-by-line… please don’y copy everything then go pressing enter.
Update your Ubuntu server to latest patches and install the packages bellow.
sudo aptitude install build-essential zlib1g-dev libcurl4-openssl-dev postfix apg geoip-bin libgeoip1 sqlite3 libsqlite3-dev libgeoip-dev libpcre3 libpcre3-dev zlib1g zlib1g-dev libyaml-dev libmysqlclient-dev libonig-dev zip unzip memcached git-core git-svn git-doc git-cvs libreadline-dev openjdk-6-jdk sqlite3 libsqlite3-dev libmagick++3 libmagick++-dev libapache2-mod-xsendfile libxslt1-dev libreadline5 libxslt-dev libxml2-dev imagemagick apache2-dev activemq
Update Ruby Gems
Update: This will also work for 5.1 and 5.5.
Note, this is a WhiteBox setup so not all parts are officially supported by VMWare. Specs below…
- i7 2600K
- Gigabyte P67A-UD4 B3
- 8GB DDR3-1866hz 9-9-9
- 1TB Samsung F3 drives
- Intel Gigabit Network card
Now, the issue here is that after a clean install of VMWare Sphere 5, boot-up would take at least 5-9 min to complete from a clean power-on. Compared to an upgrade from VMWare Sphere 4.1U1 which will load all the necessary drivers right away after a restart/power-on. It seems like its not detecting the HDD at all at first glance but soon found its way. Further tests, experiments and research yielded that this is a side-effect on how VMWare handled their installation process in VMWare Sphere 5 compared to 4.1U1. In 4.1U1, it uses the MBR for the boot process by default, while in 5.0 it uses GPT. You can fixed this if you force the installer to use MBR during the installation phase.
Advance Configuration and Power Interface (ACPI) or APM ( Advance Power Management ) support for Ubuntu 10.04 was not installed by default after server installation. I needed this so that during power outage I can just press the power button to automatically shutdown the PC.
sudo aptitude install acpi acpi-support apm
This will install the power-button-power-off feature in you server.
82579 based Ethernet network cards are only supported in Kernel 2.6.36 and up, thus Ubuntu 10.04 LTS will not have out-of-the-box support for the network card. I needed this to work since I’ll be using this as my server and 11.04 is not LTS, I have no choice. To fix this with the motherboard I have from Intel, here are the steps that I did…
- Download the driver source from Intel driver webpage here, or the latest one they have. Double check if the driver supports the version of the network card, the one I have is 82579.
- Ready the Ubuntu server, install make gcc g++ and linux headers
aptitude install make gcc g++ linux-headers-`uname -r`
- Un-pack the src driver that you just downloaded, compile and install.
tar -xvf [filename].tar
- If everything goes well, no error should come out, then enable your new ethernet card.
- You can check your new network card via ifconfig
Note: If you update your kernel or linux image via aptitude safe-upgrade or dist-upgrade, you need to remove the e1000e module, re-compile the driver and install the newly compiled driver again.
These are the steps I took to install Jakarta Tomkat 5.5 in conjunction with Java 2 SDK in Ubuntu server.
- Login as root, you can also use “su” though I prefer to login as root.
- apt-get install sun-java5-jdk
apt-get install tomcat5.5 tomcat5.5-admin tomcat5.5-webapps
- This will install Java 2 SDK (1.5), ubuntu will start downloading packages that are not found in your system.
Now here’s the tricky part, location for Java and jakarta-tomcat
- Of course jakarta-tomcat 5.5, I’m using 5.5 since this supports java 1.5
Now, open .bashrc in your favorite text editor, I used vim
At the end of the file add these:
- Java’s location is in /usr/lib/jvm/java-1.5.0-sun
- Jakarta-Tomcat’s location is in /usr/share/tomcat5.5
- We will need these location for the export configurations to be written in the .bashrc
Now save the file and exit, then log back in. This is required for the export script to be set.
Before starting the server, the default port the installer set is 8180 instead of the 8080 port that Tomcat uses. To change this, go to /usr/share/tomcat5.5/conf/ and open the file server.xml. Locate the line:
...Connector port="8180" maxHttpHeaderSize="8192"...
and change 8180 to 8080. Save and exit. Now your ready to test the server.
Now try the server if it starts, /usr/share/tomcat5.5/bin/startup.sh You should see something like this:
Shutting down the server is just /usr/share/tomcat5.5/bin/shutdown.sh
Now, during installation of tomcat, Ubuntu automatically adds a startup and shutdown script for ubuntu to use as it starts up or shutsdown in /etc/init.d/ folder. Filename is tomcat5.5. As the server finishes starting up, you will notice tomcat isn’t running at all. One possible problem is that the script didn’t use the correct path for the java 2 sdk. You can check the boot log in /var/log/. Check if during boot up, tomcat5.5 encountered problems. For the problem stated above, you can fix this by going to /etc/default/ and edit the tomcat5.5 file. Locate the line:
Using CATALINA_BASE: /usr/share/tomcat5.5
Using CATALINA_HOME: /usr/share/tomcat5.5
Using CATALINA_TMPDIR: /usr/share/tomcat5.5/temp
Using JRE_HOME: /usr/lib/jvm/java-1.5.0-sun
remove the ‘#’ and change it to…
or wherever your java directory is.After that, restart the server and see if tomcat was successfully started.
Edit: Problem encountered:
- Tomcat does not load in Ubuntu 8.04
Found a little problem loading Tomcat 5.5 under Ubuntu 8.04, it either fails or white screen just appears. I don’t know what happened from 6.04 to 8.04 but once I compared the init.d/tomcat5.5 startup script from 6.04 and 8.04, there WERE changes to the scripts. I replaced the new tomcat5.5 script in 8.04 with the old one from 6.04 and the server started properly after a server restart. I don’t know why but this may have something to do with permissions and I have yet to trace the script.
- java.lang.ClassNotFoundException: org.apache.jasper.tagplugins.jstl.If
- The problem here is that the above name is incomplete… what it should have been is org.apache.jasper.tagplugins.jstl.core.*
- Now, to fix the problem, locate
/var/lib/tomcat5.5/webapps/jsp-examples/WEB-INF/tagPlugins.xml and open it with your text editor… I used vim. Now edit each line of code that has org.apache.jasper.tagplugins.jstl in it and add “.core” after jstl. What you will see after editing the code will be…
- SEVERE: The scratchDir you specified: [folder_path] is unusable.
- Sidenote: took me 2 days to figure out why this was happening (X_x)
- Based from the Catalina logs, the folders under webapps was not accessible by tomcat5.
- Now looking under all processes running ( ps command ), most bootup services were running under root (mysql, apache, etc ) but tomcat5 was not.
- If I start tomcat5 when I logged into the console as root, the problem disappears. This lead me to believe this might have been the Tomcat5 user was not given the correct privileges.
- Work-around 1: Elevate Tomcat5 user to root access level.
- Work-around 2: Go to /etc/init.d/ and open Tomcat5.5 under any text editor ( I used vim ). Locate the line TOMCAT5_USER=tomcat55 and change it to TOMCAT5_USER=root . Restart your server or you can also execute the restart command for Tomcat5.5 in init.d folder