Backups are important, every hard disk, every motherboard, every piece of hardware will fail.  Remember this if you don’t have a backup system.

Step 1. Install required software

enable epel repo

yum install wget

wget http://ftp.rediris.es/mirror/fedora-epel/6/i386/epel-release-6-7.noarch.rpm
rpm -i epel-release-6-7.noarch.rpm

yum install BackupPC

Step 2:enable Apache webserver

edit apache config file

vi /etc/httpd/conf/httpd.conf

and make apache run as backuppc user

User backuppc

edit BackupPC apache config

vi /etc/httpd/conf.d/BackupPC.conf

should be like these

<IfModule !mod_authz_core.c>
# Apache 2.2
order deny,allow
allow from all
allow from 127.0.0.1
allow from ::1
require valid-user
</IfModule>

chkconfig httpd on

/etc/init.d/httpd start

Step 3: Configure Backuppc password

htpasswd -c /etc/BackupPC/apache.users backuppc

Step 4: Enable BackupPC Service

chkconfig backuppc on

/etc/init.d/backuppc start

Step 5: Verify installation

open a browser and navigate to

http://<Backupchost>/backuppc

I din’t found a Webinject package for Fedora 17, so I decided download the source.

For get webinject working You’ll need install these packages
yum install perl-Crypt-SSLeay
yum install perl-XML-Simple
yum install perl-Tk-ProgressBar-Mac
yum install perl-Tk-Stderr
yum install perl-Tk

Now you only will need execute ./webinjectgui.pl

I needed to add a new user into sudoers file into several debian machines, i didn’t want open a terminal in each machine and add the line manually, the other option was append a new line into the file like echo “new line”>> /etc/sudoers .But I don’t like edit sudoers file without using visudo, I don’t feel safe.

Reading the debian documentation I found a magical directive for append external files #includedir /etc/sudoers.d, that’s mean if I add a new file  with 0440 permisions and the permissions are important will be appended into our sudo config.

Removing the hash character is a inherited custom ok don’t remove the hash character  is not a comment indicador withouth the hash character, includedir /etc/sudoers.d is a bad line and visudo show an error.

I decided maintain a copy of the actual M0n0wall config, bougth a new compact flash was the quick option.

Download pfSense

First I downloaded the version for my router, in this case it’s and ALIX Board without VGA,, that means that i need to choose the nanobsd version and my compactFlash size is 4Gb, if I had a bigger campactFlash I just only need to take the 4gb versión.

wget http://files.nl.pfsense.org/mirror/downloads/pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz
wget http://files.nl.pfsense.org/mirror/downloads/pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz.md5

wget http://files.nl.pfsense.org/mirror/downloads/pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz.sha256

Verify downloaded image:

md5sum pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz

and check if output it’s the same that content in /pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz.md5

sha256sum pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz

and check if output it’s the same that content in /pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz.sha256

Dump pfSense into the compact flash

In my case as fedora user i need to detect what device file is linked to my compactFlash i make this

open a root cosole and write

mount >mountedBefore

this generate a file with actual mounted files

i attach the compact flash and execute

mount >mountedAfter

now i write

diff mountedBefore mountedAfter

and the output will be like:

> /dev/sdd1 on /run/media/luzem/753C-3741 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage=cp437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks2)

It said that my compact flash is on /dev/sdd file

first i need to umount it

umount /dev/sdd1

now i decompress and dump pfSense into compact flash writing

zcat pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz | dd of=/dev/sdd bs=16k

you should get and output like these

244138+1 records in
244138+1 records out
3999969792 bytes (4.0 GB) copied, 226.826 s, 17.6 MB/s

Putting pfSense into alix board

Now plug the compactFlash on your board

connect your board , power, ethernet ….

enjoy reconfiguring yout new router

first I installed Gitlab and then I installed Jenkins using the web page tutorial ( http://jenkins-ci.org/ ).

you need to have enabled EPEL repos http://fedoraproject.org/wiki/EPEL and rpm Fusion repos http://rpmfusion.org/ .

when you have Jenkins installed you will need install the needed packages open a root terminal and write:

yum install ant php php-phpunit-phploc php-pdepend-PHP-Depend.noarch php-phpmd-PHP-PMD.noarch php-phpunit-phpcpd.noarch php-phpunit-phploc.noarch php-pear-PHP-CodeSniffer.noarch php-phpunit-PHP-CodeBrowser.noarch

The next step is add the php template into Jenkins CI

• cd /var/lib/jenkins/jobs
• mkdir php-template
• cd php-template
• wget https://raw.github.com/sebastianbergmann/php-jenkins-template/master/config.xml
• cd ..
• chown -R jenkins:jenkins php-template/
• /etc/init.d/jenkins restart

now we can create a new php project based on the php-template

I follow my classic fedora installation method.

1. Download install DVD x86_64 version iso image.
2. Burn a blank DVD
3. Boot my computer from the DVD

these are my normal steps but my boot DVD shoa lot of errors like:

SQUASHFS error: Unable to read page, block xxxxxxxF, size xxxF

I read some info from forums and they say that the problem was with the dvd, Because after install fedora in my desktop I was installed Hasefroch 7  and burned Fedora ISO in the same computer.

After Downloaded Sha256 for windows and check that I have the correct image, i go to bed and leave the computer checking a new recorder DVD.

When I get up I observer tat new DVD has errors too, so i decided to download a live cd iso and try with live CD, this method works and i could install fedora but i saw a small number of errors but it was thinking the live cd  too small for support everything. so i decide install my system from the live cd hopping that errors disappears at first boot.

After install a bad behavior appear in the screen and system appears to frozen in moments with unexpected X restarts. I decide to check running process using top et voila. My Phenom computer only has one processor working . After that I remember that when change the hard disk some wires from the pow source stopped the CPU fan for a moment, 20 secs approx, a disaster has coming i burn my cpu and  need to buy a new processor, but when i reboot on haseforch  saw four cores working, that not was a CPU problem so I check the dmesg output.

[    0.006467] ACPI: Core revision 20120111
[    0.009031] ftrace: allocating 22596 entries in 89 pages
[    0.017650] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.028157] CPU0: AMD Phenom(tm) 9850 Quad-Core Processor stepping 03
[    0.028998] Performance Events: AMD PMU driver.
[    0.028998] ... version:                0
[    0.028998] ... bit width:              48
[    0.028998] ... generic registers:      4
[    0.028998] ... value mask:             0000ffffffffffff
[    0.028998] ... max period:             00007fffffffffff
[    0.028998] ... fixed-purpose events:   0
[    0.028998] ... event mask:             000000000000000f
[    0.028998] NMI watchdog enabled, takes one hw-pmu counter.
[    0.028998] Booting Node   0, Processors  #1
[    0.028998] smpboot cpu 1: start_ip = 93000
[    6.975648] CPU1: Not responding.
[    6.976466]  #2
[    6.976475] smpboot cpu 2: start_ip = 93000
[   14.279079] CPU2: Not responding.
[   14.281137]  #3
[   14.281146] smpboot cpu 3: start_ip = 93000
[   21.143977] CPU3: Not responding.
[   21.144993] Brought up 1 CPUs
[   21.145004] Total of 1 processors activated (5022.87 BogoMIPS).
[   21.147104] devtmpfs: initialized
[   21.147356] PM: Registering ACPI NVS region at cfcf0000 (12288 bytes)

I try changing kernel boot parameters without acpi with NOACPI and a lot of things and every time that my computer reboot my Linux only show one core.

Finally i found the guilty element it doesn’t was the CPU it was the motherboard

I update the bios using the last version but it doesn’t work, finally I download a BIOS beta version , mb_bios_ga-ma785gm-us2h_f12a, from gigabyte web page and it works.

[    0.026770] CPU0: AMD Phenom(tm) 9850 Quad-Core Processor stepping 03
[    0.026998] Performance Events: AMD PMU driver.
[    0.026998] ... version:                0
[    0.026998] ... bit width:              48
[    0.026998] ... generic registers:      4
[    0.026998] ... value mask:             0000ffffffffffff
[    0.026998] ... max period:             00007fffffffffff
[    0.026998] ... fixed-purpose events:   0
[    0.026998] ... event mask:             000000000000000f
[    0.026998] NMI watchdog enabled, takes one hw-pmu counter.
[    0.026998] Booting Node   0, Processors  #1
[    0.026998] smpboot cpu 1: start_ip = 93000
[    0.038014] NMI watchdog enabled, takes one hw-pmu counter.
[    0.038094]  #2
[    0.038095] smpboot cpu 2: start_ip = 93000
[    0.050011] NMI watchdog enabled, takes one hw-pmu counter.
[    0.050083]  #3
[    0.050084] smpboot cpu 3: start_ip = 93000
[    0.062009] NMI watchdog enabled, takes one hw-pmu counter.
[    0.062032] Brought up 4 CPUs
[    0.062034] Total of 4 processors activated (20091.79 BogoMIPS).

Now all the cores are available. Screen doesn’t works yet and I’m downloading a new DVD copy because i don’t like liveCD install.

Enjoy

After install and configure Windows XP, Fedora take his turn, but when the install process ended an out of range message appears into my screen. Fortunately network was working and ssh was runing .

First I take my laptop and  discover the nvidia computer ip, you can check your router ip or use nmap.

ssh <nvidia_ip> -l root

vim /etc/default/grub

and append in your  GRUB_CMDLINE_LINUX  this text “rhgb quiet rdblacklist=nouveau nouveau.modeset=0″

GRUB_CMDLINE_LINUX=”rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True rd.luks=0 LANG=es_ES.UTF-8  KEYTABLE=es rhgb quiet rdblacklist=nouveau nouveau.modeset=0″

and finally run

grub2-mkconfig -o /boot/grub2/grub.cfg

reboot your computer

reboot && exit

now your screen is working , not fluent  but working .

 [exec] TEST: tests/stkmngtest... (pid=13754)
     [exec]
     [exec] Gtk-WARNING **: cannot open display:
     [exec] aborting...
     [exec] FAIL: tests/stkmngtest

that makes my test suite were aborted  and also makes Jenkins useless, and useless things are my competitors because the only useless thing allowed at home is me .

The basic problem is that there no are a XOrg session running, first I change runlevel to 5 and expect see test runing  a big FAIL was the result.

after reading a bit of literature I discover a thing called Xvfb

for install follow these steps

su

yum install Xvfb

yum install mesa-dri-drivers

the next step was try to install Xvfb plugin in jenkins but i doesn’t work it give these exception

FATAL: null
java.lang.NullPointerException
	at org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.decorateLauncher(XvfbBuildWrapper.java:165)
	at hudson.model.AbstractBuild$AbstractRunner.createLauncher(AbstractBuild.java:525)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:452)
	at hudson.model.Run.run(Run.java:1434)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:239)

I found a quick and dirty solution that is put a xvfb-run call in commands that need a xserver like this

<target name=”runtest” description=”run glib test”>
<exec executable=”xvfb-run”>
<arg value=”gtester”/>
<arg value=”tests/stkmngtest”/>
<arg value=”–keep-going”/>
<arg value=”-o=Tests.xml”/>
</exec>
</target>

the solution for solve these problem is configure Jenkins plugin BIG BIG BIG THANKS TO Tomasz Wysocki, he show me the missing configuration options.

Here for global settings

And here for project settings

After install Gitlab the next step  was install Jenkins and start to work with a continuous integration server. I installed Jenkins following doc and create a new project for one of my repos. and i get this output

Building in workspace /var/lib/jenkins/jobs/PFC/workspace
Checkout:workspace / /var/lib/jenkins/jobs/PFC/workspace – hudson.remoting.LocalChannel@1aba936a
Using strategy: Default
Cloning the remote Git repository
Cloning repository origin
ERROR: Error cloning remote repo ‘origin’ : Could not clone gitolite@git.luzem.com:pfc.git
hudson.plugins.git.GitException: Could not clone gitolite@git.luzem.com:pfc.git
at hudson.plugins.git.GitAPI.clone(GitAPI.java:245)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1117)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1059)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1059)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1421)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: hudson.plugins.git.GitException: Command “git clone –progress -o origin gitolite@git.luzem.com:pfc.git /var/lib/jenkins/jobs/PFC/workspace” returned status code 128:
stdout: Initialized empty Git repository in /var/lib/jenkins/jobs/PFC/workspace/.git/

stderr: Host key verification failed.
fatal: The remote end hung up unexpectedly

at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:779)
at hudson.plugins.git.GitAPI.access$000(GitAPI.java:38)
at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:241)
at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:221)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.plugins.git.GitAPI.clone(GitAPI.java:221)
… 12 more
Trying next repository
ERROR: Could not clone repository
FATAL: Could not clone
hudson.plugins.git.GitException: Could not clone
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1129)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1059)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1059)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1421)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)

When you install Jenkins from the repos one problem is configure ssh keys for jenkins user, the first thing to configure ssh keys was su jenkins and run ssh keygen but it failed because i can’t log with Jenkins user.

i open a terminal as root on server machine as root and start writing:

vim /etc/passwd

changing jenkins line

jenkins:x:492:486:Jenkins Continuous Build server:/var/lib/jenkins:/bin/false

for

jenkins:x:492:486:Jenkins Continuous Build server:/var/lib/jenkins:/bin/bash

after changuing this line you can do

su jenkins

cd

ssh-keygen

cat .ssh/id_rsa.pub

now you have the key for your jenkins user and it can pull from your repos

for more security edit again /etc/passwd and pul false in jenkins shell

jenkins:x:492:486:Jenkins Continuous Build server:/var/lib/jenkins:/bin/false

Step 1: Install needed packages

you will need remove installed ruby because repo version is 1.8.7 and we need 1.9 at least

yum remove ruby

yum install wget

enable epel repos

wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm

rpm -Uvh epel-release-6-5.noarch.rpm

install required libraries

yum install readline-devel  libyaml-devel gdbm-devel  ncurses-devel  redis openssl-devel zlib-devel gcc gcc-c++ make autoconf readline-devel curl-devel expat-devel gettext-devel  tk-devel  libxml2-devel libffi-devel libxslt-devel libicu-devel httpd httpd-devel gitolite git-all python-devel python-pip sqlite-devel sendmail vim mysql-devel

Step 2: Install Ruby 1.9.3

wget http://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p0.tar.gz

tar xzvf ruby-1.9.3-p0.tar.gz

cd ruby-1.9.3-p0

./configure

make

make install

Step 3: Install gitolite

Create gitolite-admin user

    useradd -d /home/gitolite-admin gitolite-admin

generate RSA key pair for gitolite-admin user

su gitolite-admin
ssh-keygen
exit

Move generate public key to gitolite home dir

cp /home/gitolite-admin/.ssh/id_rsa.pub /var/lib/gitolite/id_rsa_gitolite_admin.pub
chown gitolite:gitolite /var/lib/gitolite/id_rsa_gitolite_admin.pub

complete gitolite and gitolite-admin users pairing

su gitolite
gl-setup /var/lib/gitolite/id_rsa_gitolite_admin.pub

a editor will opened changue repo permissions to 0007

$REPO_UMASK to 0007
exit
su gitolite-admin
cd
git clone gitolite@localhost:gitolite-admin

in the last command you clone the gitolite-admin repo on gitolite-admin’s home. Gitolite-admin repo is gitolite config

before continue we need configure gitolite-admin git profile

git config –global user.email “gitolite-admin@localhost”
git config –global user.name “gitolite-admin”
exit

add gitolite-admin to gitolite group

usermod -a -G gitolite gitolite-admin

changue gitolite-admin password

passwd gitolite-admin

Step 6 Launch Redis

chkconfig redis on

/etc/init.d/redis start

Step 7 GitLab

Clone GitLab sourcecode

cd /var/www

git clone git://github.com/gitlabhq/gitlabhq.git

chown -R gitolite-admin:gitolite-admin gitlabhq/

cd gitlabhq/

Install phython dependencies

pip-python install pygments

Install required gems

gem install bundler

bundle install

su gitolite-admin

bundle install

Prepare config files

cp config/database.yml.example config/database.yml

cp config/gitlab.yml.example config/gitlab.yml

Prepare production enviroment

RAILS_ENV=production rake db:setup
RAILS_ENV=production rake db:seed_fu

you will get these login data

login………admin@local.host
password……5iveL!fe

Config gitolite gitlab link

vim config/gitlab.yml

your  git_host: section must be like this

# Git Hosting congiguration
git_host:
system: gitolite
admin_uri: gitolite@localhost:gitolite-admin
base_path: /var/lib/gitolite/repositories/
host: localhost
git_user: gitolite
# port: 22

fix gitolite permissions

chmod -R 770 /var/lib/gitolite/repositories/

try your installation launching webrick

bundle exec rails s -e production

open a web broser, write  yourhost:3000 and check if everything is working if you get an error send me a comment

Install passenger for Apache

gem install passenger
passenger-install-apache2-module

follow screen instructions

edit apache config file

vim /etc/httpd/conf/httpd.conf

and append these lines at the end

LoadModule passenger_module /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.11/ext/apache2/mod_passenger.so
PassengerRoot /usr/local/lib/ruby/gems/1.9.1/gems/passenger-3.0.11
PassengerRuby /usr/local/bin/ruby

enable apache service

/etc/init.d/httpd start

chkconfig httpd on

Sources

http://wasil.org/en/gitlab-installation-on-fedora-16-with-gitolite

http://rickfoosusa.blogspot.com/2011/08/gitolite-tutorial-senawario.html