• Minimal.iso = It contains minimum package that requires to a functional Linux system. Doesn’t contain GUI.

• Dvd.iso= It contains minimal packages plus some utility packages, basic development packages and contains GUI. It’s size is 3.7 GB that can fit in DVD.

Boot the system with the boot device and continue installation with selecting Install AlmaLinux 8.

Continue the installation with selecting the system language.

After choosing the system language, the setup page like the one below will appear.

The first thing to do is to set up the network. AlmaLinux needs an active internet connection to download base packages and other necessary files.

If connection can not be established with automatic dhcp settings, dhcp settings should be switched to manuel mode and ipv4 settings should be arranged according to the user’s information.

Next step is setting the root password, keyboard layout , time-date and disk partitioning. After the root password is set, set up time, date and keyboard layout. Inside the disk partitioning settings , select the disk that is going to be used and then click the Done button.

Next, before clicking the Begin Installation button, it should be chosen which packages are going to be installed in the Software Selection section.

If everything has been set correctly, there should be no warnings under the sections. After the steps are completed, you can start your installation by clicking the Begin Installation button. A proper setup page is as follows.

After the installation is complete, it is important to download the basic network packages as well. These packages can be installed with a single command. Other essential packages can be added to this command.

# yum install vim bind-utils net-tools wget rsync netctl openssh-server dnsutils atop

If problems are encountered while installing atop, it should be downloaded with the wget command.

# wget http://www.atoptool.nl/download/atop-2.1-1.i586.rpm

After the download process is completed, it can be seen which group packages of AlmaLinux are installed on the system with the following command and the missing ones should be downloaded in line with the user needs.

# yum group list

There is no GUI in the system due to minimal installation, if a GUI is needed: Download should be done with the Workstation option. This option will provide the user with the Gnome Desktop Environment, as well as most packages that should be on a Workstation.

# yum  group install workstation

After the download is completed, the desktop can be activated with the following command.

# startx &

The post How to Install AlmaLinux 8 appeared first on VeriTeknik.

To install mod_python, we need the EPEL repositories:

rpm --import https://fedoraproject.org/static/0608B895.txt
wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-7.noarch.rpm
rpm -ivh epel-release-6-7.noarch.rpm
yum install yum-priorities

Now edit the /etc/yum.repos.d/eped.repo file and add priority=10 to the [epel] section.

After that follow the steps below and you’ll have mod_python installed and active.

yum install mod_python
service httpd restart

Now you should configure your httpd.conf files so that apache nows where and when to interpret your Python scripts. If you have installed you system with our LAMP installer, then go to /etc/httpd/conf.d and edit you websites .conf file (starting with a z_)

vi /etc/httpd/conf.d/z_castmator.com

Make sure you add the following lines in the <Directory …> </Directory> statements.

AddHandler mod_python .py
PythonHandler mod_python.publisher
PythonDebug On

Don’t forget that PythonDebug is for debug mode. When you’re done developing it may be a good idea to turn it off.

Also don’t forget to add your DirectoryIndex handlers so that Apache knows you can also have Python Index files. You can add this right after the </Directory> statement.

DirectoryIndex index.html index.php index.py

Since we’ve altered with the configuration files of Apache, we should restart it again, then you are ready to go.

service httpd restart

The post Install mod_python on Centos 6 appeared first on VeriTeknik.

Just get the copy from ioncube webpage itself, http://www.ioncube.com/loaders.php
We will download the 64-bit version for our example.

Then extract the file, copy the shared object file that matches your PHP version to an appropriate folder.
To learn your PHP version you can simple grep the php -i output.

After copying the shared object, add a few lines to your php.ini and that’s it.

wget http://downloads2.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.tar.gz
 tar -xvzf ioncube_loaders_lin_x86-64.tar.gz
# learn php version
 php -v
# let's say it's 5.2
 mkdir /usr/local/ioncube
 cp ioncube/ioncube_loader_lin_5.2.so /usr/local/ioncube
# locate your php.ini file
 php -i|grep php.ini

Add the lines below at the end of your php.ini file.
[ code lang=”bash” ]
zend_extension = /usr/local/ioncube/ioncube_loader_lin_5.2.so
[ /code ]

The post Installing IonCube Loader on Linux appeared first on VeriTeknik.

DO you ever wanted to set-up a testing server with
– Apache virtual config, logs, paths setted,
– MySQL server with password set,
– FTP Server (Vsftpd),
– PHP and PhpMyAdmin installed & configured on your server or VPS in seconds?

If you answer “yes” to the question, you are in the right place, what does this script do in basic:

– Installs http, PHP, MySQL, phpMyAdmin, rpmforge repo and other related packages
– Sets apache configs, mod_deflate, virtual hosts, create user, cgi-bin directory
– Sets time with ntpdate, disables iptables & selinux, mysql password and
– Updates the system

What is needed?
– A clean minimal install of CentOS/Redhat 6.X

How can I download the script?

wget http://www.plugged.in/downloads/plugged.sh

or just download it.

[wpdm_file id=1]

How to use the script?

chmod 755 plugged.sh
./plugged.sh -u username -p password -d domain.com

You can reach phpMyAdmin by typing domain.com/phpMyAdmin/

If you have suggestions or requests please write down!

The post Download Plugged.in LAMP installer for CentOS 6.x appeared first on VeriTeknik.

Below I’ll describe how to achieve this in Debian based and Red Hat based distros seperately.

Using Debian based distros (Ubuntu, Mint etc.), setting multiple IP addresses on a single network interface is simple.

What we will do is to edit the /etc/network/interfaces file.
If you are using DHCP, then your file should look similar to this,

auto eth0
iface eth0 inet dhcp

auto eth0:0
iface eth0:0 inet dhcp
iface eth0:0 inet6 dhcp

Here, the eth0:0 is how we get the secondary IP address on the eth0 device.

If you’re using a static IP address instead of DHCP, then your interfaces file should be like,

auto eth0
iface eth0 inet static
address 10.20.30.40
netmask 255.255.255.0
network 10.20.30.0
broadcast 10.20.30.255
gateway 10.20.30.1
dns-nameservers 8.8.8.8

iface eth0 inet6 static
address 2f00:7300:100::10
netmask 64

auto eth0:0
iface eth0:0 inet static
address 10.20.30.41
netmask 255.255.255.0

iface eth0:0 inet6 static
address 2f00:7300:100::11
netmask 64

You can add as many as you want, such as eth0:1, eth0:2 …

Sometimes when adding multiple IPv6 addresses on Debian systems, it is possible that you get an error. The current workaround for that is to enable and disable the device a couple of times. You can find the solution to that problem here.

In Red Hat based distros (CentOS, Fedora etc.), the interfaces are edited through the directory /etc/sysconfig/network-scritps. Here we have multiple files, each pointing for a device. For instance, to have 2 additional IP’s on a single ethernet device (totaling 3 addresses) we should have 3 files as follows,

/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth0:1
/etc/sysconfig/network-scripts/ifcfg-eth0:2

The main device file would be just a standard one, we don’t have to change anything with it.
On the other hand, the ifcfg-eth0:1 file should be similar to this,

NAME=""
BOOTPROTO=static
MACADDR=""
IPV6INIT=no
DEVICE=eth0:1
NETMASK=255.255.255.0
MTU=""
BROADCAST=10.20.30.255
ONPARENT=yes
IPADDR=10.20.30.41
NETWORK=10.20.30.0
IPV6INIT=yes
IPV6ADDR=2f00:7300:100::11
IPV6_DEFAULTGW=2f00:7300:100::1
ONBOOT=yes

This would suffice. Don’t forget to restart your network services after adding the lines (or files) to with your appropriate settings.

For Debian : $ /etc/init.d/networking stop && /etc/init.d/networking start
For Red Hat : $ service network restart

For additional IPv6 addresses you should need to add IPV6ADDR_SECONDARIES=”” line to /etc/sysconfig/network-scripts/ifcfg-eth0 file

IPV6INIT=yes
IPV6ADDR=2f00:7300:1::2/64
IPV6ADDR_SECONDARIES="2f00:7300:1::3/64 2f00:7300:1::4/64 2f00:7300:1::fff4/64 2f00:7300:1::fff5/64"

The post Bind Multiple IP Addresses on a Single Network Card IPv4 & IPv6 appeared first on VeriTeknik.

The main goal is to check whether we get any response from the FTP server while we try to connect anonymously. Don’t forget that this script probably won’t work if the FTP server allows anonymous connections.

We simply use the ftplib module to establish the FTP connection. After the successful (or failed) connection, we can report the status of the server via email, to achieve this we use the smtplib module.

The first lines seem simple,

#!/usr/bin/python
import ftplib, smtplib
server_ip='10.20.30.40'
sender='sender@email.com'
receivers=['john@email.com','doe@email.com']

Above, after importing our modules, we’ve defined the ip address of our FTP server. After that, the sender email address is defined, and then a list containing the receivers.
Now we can define our messages. We’ll have two messages, one for the UP status, and one for the DOWN.

message_up="""
 From: FTP Status DAEMON 
 To: John , Doe 
 Subject: FTP Service Running
The FTP Service on %s is running.
 """ % server_ip
message_down="""
 From: FTP Status DAEMON 
 To: John , Doe 
 Subject: FTP Service DOWN!
The FTP Service on %s is DOWN!!!
 """ % server_ip

Now we can actually start the checking. The first try clause is checking if we can establish any kind of connection with the server. If the server is somehow down, or if only the FTP service is shut down, this will return some sort of error, which we will catch with the except clause, handle it with our smtp commands, then raise a system exit.

try : ftp=ftplib.FTP(server_ip)
except :
 print "FTP DOWN !!!"
 smtpObj = smtplib.SMTP('localhost')
 smtpObj.sendmail(sender,receivers,message_down)
 raise SystemExit

And here’s the second check, if we somehow get to this line, it means that we’ve passed the system exit above, so our connection attempt with the server worked, but we’re not sure if the FTP service is actually running without a login attempt. When we try to login, and if anonymous connection isn’t allowed, we’ll get a permission error, handling it with an exception we can email the recievers that the server is running.

try : ftp.login()
except ftplib.error_perm :
 print "FTP Up, Permission Denied."
 smtpObj = smtplib.SMTP('localhost')
 smtpObj.sendmail(sender,receivers,message_up)

Now simply connect the dots and add the whole script to your crontab, then you’re good to go!

The post A Simple FTP Status Daemon appeared first on VeriTeknik.

As it turns out, it’s a very simple task limiting the file size you want with the output of the find tool.

The -size argument will define the borders of your output. Let’s say you want to find the files smaller than 50 MB on your server,

find / -type f -size -50M

Well, this will print out the full path and the file names, you won’t know which file is at what size. So to improve this, we can execute an ls command on each output,

find / -type f -size -50M -exec ls -lh {} \;

On this command, the {} refers to the output of each find command, and the \; is mandatory since we need to tell find where our -exec line ends, hence the escape character. (\)

Even though this looks good, we can keep improving by printing out the file size all in the same units. (Let’s say, megabytes) The problem with that is, the ls command can printout with the specified block size limit but it will take that block size quantised, meaning the output will only be the exact multiplicands of that block size. So if our block size is set to 1 MB and a file is 900 KB, ls will output it as 1 MB.

Although this is not so accurate, we can always work it around using awk to calculate the numeric values for us. Since ls normally prints out the file size in bytes, we can divide them to become actual megabytes. The line below will printout ls with actual megabytes.

ls -l | awk '{print $1 " " $2 " " $3 " " $4 " " $5/1048576 " " $6 " " $7 " " $8 " " $9}'

Well, we only need the 5th column and the 9th column which are the size and the path respectively, so the command below will suffice :

ls -l | awk '{ print $5/1048576 " " $9 }'

As you can see, we had to use a pipe to get things done here. So we need to use this pipe in our exec part of our find command, which is another problem. Well, the work around for this is to -exec a shell instance and pass the whole ls and awk line including the pipes so that new shell instance will handle things for us.

find / -type f -size -50M -size +20M -exec sh -c "ls -l '{}'|awk '{print \$5/1048576 " MB: " \$9}'" \;

Ok, let’s have a look at the command above. As you can see we narrowed our limits further, by getting only the files smaller than 50 MB and larger than 20 MB. We also passed our whole command with a shell instance. On this instance, the argument for ls was passed with the {} method. We apostrophized it (”) due to the possibility of having spaces in the filename, which would have caused a problem. After that, we’ve piped our output to awk, divided the bytes, and added a string ” MB: ” right before printing the 9th column which is the file path. Don’t forget that we should escape the $5 and $9 using the escape character \ since we don’t want the whole find line to process it before our awk does.

Well, the good thing is we have necessary output, the bad thing is that, it isn’t in order! So let’s make things even prettier and sort them, while making the output of each “MB:” bold to get some eye candy.

find / -type f -size -50M -size +20M -exec sh -c "ls -l '{}'|awk '{print \$5/1048576 \" \033[1mMB:\033[0;0m \" \$9}'" \; | sort -nr -k1

As you can see here, we’ve piped the find command to the sort, not the shell instance that we invoked in the find command, that’s why the pipe is right after our \; character.

On this command, find will also search inside /proc directory, which is a living directory, so during the search some files will be created and destroyed rapidly, which will cause some annoying outputs saying “file not found”. To avoid that, let’s tell find NOT to search the /proc directory using the -prune argument.

find / -path '/proc' -prune -o -type f -size -50M -size +20M -exec sh -c "ls -l '{}'|awk '{print \$5/1048576 \" \033[1mMB:\033[0;0m \" \$9}'" \; | sort -nr -k1

You can add new directories to prune with the -path ‘/new/directory/to/prune’ -prune -o method.

Hope this helps.

The post Find the Largest Files appeared first on VeriTeknik.

You must download the setup file from DirectAdmin site:

Download DirectAdmin setup file & run:

mkdir /root/DA
cd /root/DA
wget http://www.directadmin.com/setup.sh
sh setup.sh

Steps to follow:

DirectAdmin setup will ask you your account number & your license number, if you mistype accidentally just press CTRL+C to quit and restart setup. You need to wait ten seconds after restarting setup.

After that step the setup will ask you your domain name (hostname) bare in mind that wirte your hostname as subdomain + domain + tld as we offer the subdomain part should better be “mail”. Such that your domain name is myserver.com then write your hostname as “mail.myserver.com”, this way your mail server inside DirectAdmin should work better.

After that step, follow the directives, (we offer apache 2, php5 installation and “yes” to all questions) and finish the installation. Always consider selecting the second option,

You should better restart the server but restarting DirectAdmin is enough with the command:

service directadmin restart

After the installation you can enter to your admin site by typing http://SERVERIP:2222 to your favorite browser. Don’t panic if some of the services is not responding after setup, this is because you need to make some DNS configurations and you need to enter your master domain name to the control panel(cp).

DirectAdmin setup creates a log file called setup.txt where all your passwords for your server is present:

less /usr/local/directadmin/scripts/setup.txt

Go to Step three for making post installation tasks.

The post Step II: DirectAdmin Setup appeared first on VeriTeknik.

But adding a job in your bash script is not that simple, because what you have to do is, to get the entire list of the jobs, append your new job and save them as a whole.

Here’s a snippet of how to do that. Here, we assume that we want to run a script called “myscript.sh” every 5 minutes and the full path of the script is “$my_path/myscript.sh”. Don’t forget that in everycase, adding a job to crontab you have to specify the full path!

So basically, add these lines to your script.

command="$my_path/myscript.sh" > /dev/null 2>&1"
job="* /5 * * * * $command"
cat <(grep -i -v "$command" <(crontab -l)) <(echo "$job") | crontab -

Note that this is for BASH, not SH, since the syntax with the brackets is only available in BASH.

As you can see, the last line is the critical one. In the first brackets using the grep tool, we catch everything currently in the crontab “except our command”, so this will prevent from adding the $command even if it is already in crontab. After that, we echo our job to the end of the current jobs, and redirect it to cat as a standart input. Since the standart output of cat will be the whole crontab list “with our new job”, we can use crontab with its “-” option to get the arguments from the stadart output.

Hope this helps.

The post Adding Job to Crontab Using BASH appeared first on VeriTeknik.

Whilst doing that, we realized the server was getting a lot of incoming mails as forgery. So, it is possible to get the IP list of the possible forgerers.

To do this, we need to check the lines that indicate an INCOMING message, and that claims it uses our mail server itself as a sender, but actually connects through a different IP address.

Exim uses the notation for incoming messages, so it is easy to catch.
It also uses the notation H=IP.ADD.RE.SS to state the IP address (or the hostname) of the incoming message. The beauty in this is that, it also gets the real IP address and checks if they match, if they don’t match, then it brackets the H= value like this H=(IP.ADD.RE.SS) and right after that, gives the real IP address with boxed brackets. [REAL.IP.ADD.RESS]

To detect forgeries done in a time period, and getting ONLY the IP address is crutial when you want check those IP addresses with others tools and scripts. So here’s an example grep line :

grep -ohP "(?

The example above, assumes that your mailserver’s IP Address is 10.1.31.33, of course this won’t be the case since it’s a local ip, so change that with yours.
It also checks for attempts in March 2012, you can also edit this, since we’re using the Perl compatible regular expressions (the -P option of grep) than we can use .. as wildcards for 2 characters (the day indicator).
Since we’re checkig for more than 1 file, (mainlog*) grep will output the filenames too, the -h option is to suppress that.
Also, we’re piping the output to uniq, so that we don’t get multiple results for the same IP address.
Now you can simply redirect these IP addresses to your script/tool or save them for other purpose.

The post Detecting Possible Mail Forgers in EXIM appeared first on VeriTeknik.