Do you meet the system requirements?

– Clean OS FreeBSD 4.7, 4.8, 4.9, 4.10, 4.11, 5.0, 5.1, 5.2, 5.2.1, 5.3, 5.4, 6.0, 6.1

– At least one external IP address (NAT/LAN-based systems will NOT work)

– SSH installed, gcc installed (these are usually standard with 99% of systems)

Step 2: Make sure your license information is correct.

Sign into your client account at

*** https://www.directadmin.com/clients ***

and click the “view” link next to your license.

Verify that the server IP address and operating system is correct. Also make sure that the license is Active and Verified (if it isn’t, then the DA billing system hasn’t processed your order yet).

============================================================
**** THERE IS SPECIAL NOTICE FOR FreeBSD INSTALLATIONS ****
============================================================

1) If logging in as a user other than admin or root (using su to gain root access):

2) You *have* to add “AllowUsers username” to /etc/ssh/sshd_config before you log out from root or you’ll lose root on the server forever, and you’ll have to format.

3) Login as root and download the setup.sh file

Command

# wget https://www.directadmin.com/setup.sh

Hint: Use “fetch” instead of “wget” on FreeBSD systems.

so it will be

# fetch https://www.directadmin.com/setup.sh

5) Change permissions on the setup.sh file
Command

# chmod 755 setup.sh

6) Run the setup script!

# ./setup.sh

You will be prompted for a client ID number, license ID number, and hostname.

Important: The hostname should not be the same as the primary domain name. e.g. gary.com is not a good hostname, where server.gary.com is good. Having the same host/main domain name will cause e-mail and FTP problems. Also, please make sure the hostname resolves once you setup DNS.

That’s it! You are done with the above given procedure.

The post Install Direct Admin on FreeBSD appeared first on Hivelocity Hosting.

Cron file for RedHat: /etc/cron.d/directadmin_cron
Cron file for FreeBSD: /etc/crontab

Edit the cron file and locate the line that looks like the following:

10 0 * * * root echo ‘action=tally&value=all’ >> /usr/local/directadmin/data/task.queue
That means that the tally will be run 10 minutes after midnight every day.

If you’d like to (for example) run the tally every 4 hours, you’d change it to:

10 */4 * * * root echo ‘action=tally&value=all’ >> /usr/local/directadmin/data/task.queue

One important thing to remember is that for very large servers, with upwards of 1000 domains, the tally can take a significantly long time to run (up to 2 hours), so if you run a large server, you may not want to run the tally too often.

Once you’ve set the value you want, save the file and reload the cron daemon by runnin the command:

killall -HUP crond

The post Make diskuage, bandwidth and webalizer stats update more frequently appeared first on Hivelocity Hosting.

1) Restore the old httpd.conf file:

cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf

2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3. Then type

echo “action=rewrite&value=ips” >> /usr/local/directadmin/data/task.queue
echo “action=rewrite&value=httpd” >> /usr/local/directadmin/data/task.queue
echo “action=directadmin&value=restart” >> /usr/local/directadmin/data/task.queue

3) Now you can recompile apache 1.3

rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
./build clean
./build all

4) Fix the modules link:

cd /etc/httpd
rm -f modules
ln -s /usr/lib/apache modules

5) Restore the old boot script:
FreeBSD:

cp -f /usr/local/directadmin/customapache/httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd
/usr/local/etc/rc.d/httpd restart

RedHat:

cp -f /usr/local/directadmin/customapache/httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
/etc/init.d/httpd restart

The post Downgrade from apache 2 back to apache 1.3 appeared first on Hivelocity Hosting.

1) Restore the old httpd.conf file:

cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf

2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3. Then type

echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue

3) Now you can recompile apache 1.3

rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
./build clean
./build all
4) Fix the modules link:

cd /etc/httpd
rm -f modules
ln -s /usr/lib/apache modules

5) Restore the old boot script:
FreeBSD:

cp -f /usr/local/directadmin/customapache/httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd
/usr/local/etc/rc.d/httpd restart

RedHat:

cp -f /usr/local/directadmin/customapache/httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
/etc/init.d/httpd restart

The post How to downgrade from apache 2 back to apache 1.3 appeared first on Hivelocity Hosting.

wget https://files.directadmin.com/services/wget-1.8.2.tar.gz

tar xvzf wget-1.8.2.tar.gz

cd wget-1.8.2

./configure --prefix=/usr --with-ssl

make

make install

If you’re using FreeBSD, you’d need to use –prefix=/usr/local instead of /usr.
Obviously, if you don’t have wget to begin with, you’d need to use another tool to download the wget source code, like “fetch” or “lynx”.

The post How to compile wget for your system appeared first on Hivelocity Hosting.

Error setting up your web: /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.4: Undefined symbol “_flockfile”
or

Error setting up your web: /usr/libexec/ld-elf.so.1: Shared object
“libc.so.4” not found, required by “owsadm.exe”
then you’ll need to do the following:

pkg_add -r compat4x
cd /usr/lib
mv libc_r.so.4 libc_r.so.4.old
ln -s /usr/local/lib/compat/libc_r.so.4.compat4x libc_r.so.4


If pkg_add fails, try this:

cd /usr/ports/misc/compat4x
make deinstall
make clean
make install
cd /usr/lib
mv libc_r.so.4 libc_r.so.4.old
ln -s /usr/local/lib/compat/libc_r.so.4.compat4x libc_r.so.4


For FreeBSD 6.0, try this:

cd /usr/lib
ln -s /usr/local/lib/compat/libcrypt.so.2
ln -s /usr/local/lib/compat/libm.so.2
mv libc.so.4 libc.so.4.old
ln -s /usr/local/lib/compat/libc.so.4

The post Frontpage gives error on FreeBSD 5.x appeared first on Hivelocity Hosting.

Try removing –with-openssl from your configure.php file and recompile php.

cd /usr/local/directadmin/customapache
vi configure.php
#remove --with-openssl from the file, save, exit.
./build clean
./build php n


Possibly a mod_perl issue. Edit the /etc/httpd/conf/httpd.conf
change:

AddModule mod_perl.c
to

#AddModule mod_perl.c
and then restart apache.
This won’t affect files in the cgi-bin (I’ve seen very few people actually making use of mod_perl itself).

more info:

Previous workaround for the problem is to remove thp php flags from the httpd.conf files:

cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom
perl -pi -e 's/php_admin/#php_admin/' *
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d
/usr/local/etc/rc.d/httpd restart


One user reported that installing zend solved this problem as well, so try:

cd /usr/local/directadmin/customapache
./build zend

Possibly have to downgrade zend to 2.5.7 from 2.6.2 as well as the zend binaries may not be backwards compatible.

To downgrade to apache 1.3.33 and php 4.3.11, run:

cd /usr/local/directadmin/customapache
./build clean
perl -pi -e 's/1.3.34/1.3.33/' build
perl -pi -e 's/1.3.34/1.3.33/' configure.apache_ssl
perl -pi -e 's/2.8.25/2.8.24/' build
perl -pi -e 's/4.4.1/4.3.11/' build
./build update_data
./build all d

The post Apache is not starting after update on FreeBSD ? appeared first on Hivelocity Hosting.

1) Restore the old httpd.conf file:

cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf


2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3. Then type

echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue

3) Now you can recompile apache 1.3

rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
./build clean
./build all

4) Fix the modules link:

cd /etc/httpd
rm -f modules
ln -s /usr/lib/apache modules


5) Restore the old boot script:
FreeBSD:

cp -f /usr/local/directadmin/customapache/httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd
/usr/local/etc/rc.d/httpd restart


RedHat:

cp -f /usr/local/directadmin/customapache/httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
/etc/init.d/httpd restart

The post How do I downgrade from apache 2 back to apache 1.3? appeared first on Hivelocity Hosting.

check /var/log/cron. See if the dataskq is running every minute (logged every minute). If not, try running

chmod 644 /etc/cron.d/directadmin_cron
/sbin/service crond restart


make sure crond is running :
ps ax | grep cron

try restarting cron:
/sbin/service crond restart
Check /var/log/cron and /var/log/messages for possible problems with the /etc/cron.d/directadmin_cron file (/etc/crontab on FreeBSD).

If all of the above checkout but the task.queue is still not being processed, try running it manually:

/usr/local/directadmin/dataskq d

The post Why is the task.queue not being processed? appeared first on Hivelocity Hosting.

Cron file for RedHat: /etc/cron.d/directadmin_cron
Cron file for FreeBSD: /etc/crontab

Edit the cron file and locate the line that looks like the following:

10 0 * * * root echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue
That means that the tally will be run 10 minutes after midnight every day.

If you’d like to (for example) run the tally every 4 hours, you’d change it to:

10 */4 * * * root echo 'action=tally&value=all' >> /usr/local/directadmin/data/task.queue

One important thing to remember is that for very large servers, with upwards of 1000 domains, the tally can take a significantly long time to run (up to 2 hours), so if you run a large server, you may not want to run the tally too often.

Once you’ve set the value you want, save the file and reload the cron daemon by runnin the command:

killall -HUP crond

The post How do I make diskuage, and webalizer stats update more? appeared first on Hivelocity Hosting.

Do you meet the system requirements?

– Clean OS FreeBSD 4.7, 4.8, 4.9, 4.10, 4.11, 5.0, 5.1, 5.2, 5.2.1, 5.3, 5.4, 6.0, 6.1

– At least one external IP address (NAT/LAN-based systems will NOT work)

– SSH installed, gcc installed (these are usually standard with 99% of systems)

Step 2: Make sure your license information is correct.

Sign into your client account at

*** https://www.directadmin.com/clients ***

and click the “view” link next to your license.

Verify that the server IP address and operating system is correct. Also make sure that the license is Active and Verified (if it isn’t, then the DA billing system hasn’t processed your order yet).

============================================================
**** THERE IS SPECIAL NOTICE FOR FreeBSD INSTALLATIONS ****
============================================================

1) If logging in as a user other than admin or root (using su to gain root access):

2) You *have* to add “AllowUsers username” to /etc/ssh/sshd_config before you log out from root or you’ll lose root on the server forever, and you’ll have to format.

3) Login as root and download the setup.sh file

Command

# wget https://www.directadmin.com/setup.sh

Hint: Use “fetch” instead of “wget” on FreeBSD systems.

so it will be

# fetch https://www.directadmin.com/setup.sh

5) Change permissions on the setup.sh file
Command

# chmod 755 setup.sh

6) Run the setup script!

# ./setup.sh

You will be prompted for a client ID number, license ID number, and hostname.

Important: The hostname should not be the same as the primary domain name. e.g. gary.com is not a good hostname, where server.gary.com is good. Having the same host/main domain name will cause e-mail and FTP problems. Also, please make sure the hostname resolves once you setup DNS.

That’s it! You are done with the above given procedure.

The post How do I install Direct Admin on FreeBSD? appeared first on Hivelocity Hosting.