Install Plesk Billing standalone on win2008

There are steps that allow to install Plesk Billing standalone on win2008 server with installed on it Plesk 9.X.X

1.Create site via Plesk admin interface
Home>Domains ->Create domain ->
with enabled PHP support ->Version 5.x ->run as CGI Application
with enabled "Use dedicated pool" option
the rest parameters for own consideration
2.Make sure that is installed Zend or Ioncube support
check
C:\Program Files\Parallels\Plesk\Additional\PleskPHP5\php.ini file
for zend_extension_ts
for example I have installed Ioncube dll to C:\Program Files\Parallels\Plesk\Additional\PleskPHP5\ext\ so in php.ini should be at the beginning
zend_extension_ts= "C:\Program Files\Parallels\Plesk\Additional\PleskPHP5\ext\ioncube_loader_win_5.2.dll"
3.Download PleskBilling installation archive http://www.parallels.com/download/plesk/billing/
and extract Plesk Billing to home folder of created site
how example
C:\inetpub\vhosts\pppbs.com\httpdocs
4.Login to Plesk admin CP interface,
Go to Home>Database Servers> Local MySQL server ->WebAdmin
create for pleskbilling mysql user and database via phpmyadmin (with privileges according to installation guide http://download.ppb.parallels.com/6.0/doc/parallels-plesk-billing-6.0-for-windows-installation-guide/index.htm)
5.Start installation of Plesk Billing by usinghttp://download.ppb.parallels.com/6.0/doc/parallels-plesk-billing-6.0-for-windows-installation-guide/index.htm
Latest step - creating of database , so it can fail due to timeout reason, for this please increase values of
default_socket_timeout and mysql.connect_timeout in C:\Program Files\Parallels\Plesk\Additional\PleskPHP5\php.ini
After installation Plesk Billing database can have 214 tables with ~4,601 records.

Anonymous account name you may find in properties of PleskBilling site ->Feature View-> Authentication->Anonymous authentication ->Edit , via IIS Managenment, if will be problems with NTFS permissions this account you may add to the TEMP directory with modify permissions

How to enable SSHd on LinkSys wrt54gl

LinkSys wrt54gl Router provides few ways how to setup and administrate it.

- web interface (http://your-router-ip)

- telnet (Run > CMD > telnet your-route-ip > root > root_pass)

- ssh (by default this feature is disabled)

So to enable this feature download DD-WRT firmware be sure that you download Standard Generic firmware.

After that install it (from web interface Administration > Firmware Upgrade)

!!!!NOTE Please make back up of your curent configuration and backup of you previous firmware!!!!!

After successful installation go to Services > services and enable SSHd

Now you will be able to connect to router via ssh

Removing stored passwords in Windows XP

The Problem

Users have stored user ID and password information on their computer. When visiting a site, the stored IDs and passwords grant access without the user having to reenter information.

The Solution

1.      Click Start and select Run.

2.      Type in rundll32.exe keymgr.dll, KRShowKeyMgr and click OK.

3.      The Stored User Names And Passwords Window will appear.

4.      You can remove an entry by selecting it from the list and clicking Remove.

5.      Click Close.

How To - Reset administrator username and password in SmarterMail

How To - Reset administrator username and password in SmarterMail

Applies to: SmarterMail (all versions)

To reset the primary administrator login and password in SmarterMail, follow the instructions below:

1. Stop the SmarterMail Service
2. Open Windows Explorer (My Computer)
3. Go to C:\Program Files\SmarterTools\SmarterMail (or wherever you installed SmarterMail)
4. Open the Service subdirectory
5. Make a backup copy of the file MailConfig.xml
6. Right-click on MailConfig.xml and choose Open With -> Notepad
7. Find the section that looks like this:
** System Admin ***************************
** To reset admin password, delete these items **
** and then restart the SmarterMail Service. **
*****************************************
< sysadminusername> ... < / sysadminusername>
< sysadminpassword> ... < / sysadminpassword>
*****************************************
8. Delete those lines and save the file
9. Start the SmarterMail Service

You should now be able to log in to SmarterMail by using the following:

Email: admin
Password: admin

Changing MySQL Root Password

1. Login as root to the box with the MySQL server.
2. Stop MySQL server.
3. Open the mysql server startup script. This is the file you have just executed to stop MySQL server.
4. Find the line that contains the mysqld_safe command and add --skip-grant-tables as its parameter.
5. Start MySQL server.
6. Login as the mysql user and connect to the mysql user/permission database and run the update queries:
# mysql -u root mysql
mysql> UPDATE user SET Password=PASSWORD('newrootpassword') WHERE User='root';
mysql> FLUSH PRIVILEGES;
replacing newrootpassword with the new root password to the box with the MySQL server.
7. Exit mysql database by typing \q.
8. Exit mysql user console by typing exit
9. Stop MySQL server.
10. Open the mysql server startup script and remove the --skip-grant-tables parameter you added above.
11. Start MySQL server.
12. Open the file ~mysql/.my.cnf and update the password in the corresponding line.

Helm 4.0.x upgrade to 4.1.x

there is some additional information to this topic: http://forums.webhostautomation.com/showthread.php?p=182350#post182350

Upgrade Instructions
4.0.x to 4.1.1 Upgrade

1. The upgrade to Parallels Helm 4.1.1 requires a valid license with Upgrade Protection, or, in terms of Parallels licensing, a license that provides Software Update Service (SUS) which entitles you to version upgrade licenses throughout the life of your SUS. Read more about SUS: http://www.parallels.com/en/support/sus.
   You can validate your license by going to the Parallels Helm member area: http://www.webhostautomation.com/members.
   If you have a license without SUS, go to http://www.parallels.com/store/support/helm/ and reinstate your license. Otherwise, you will not be able to upgrade to Parallels Helm 4.1.1
2. Download the Parallels Helm 4.0 to 4.1.1 Upgrade Tool from the following location: http://helm.download.webhostautomati...pgradeTool.exe.
3. Run the tool and follow its instructions.

=========

First of all make sure that you have .net framework sp2 installed (for all versions) and your Helm is running. If no http://kb.parallels.com/en/5996 you should patch your helm, and re run helm upgrade

Second you should have ready to upgrade licenses for all your servers (SUS)

If you are ready you can run upgrade tool. Usually upgrade procedure takes about 30-40 mins.

NOTE!!! UPGRADE FROM HELM 3.0 TO HELM 4.0 IS ALMOST IMPOSSIBLE, IF YOU WANT TO SAVE YOUR TIME AND MONEY DO NOT PERFORM UPGRADE.

mod_dphpbb3_last_topics php warnings

 

Today after installing such pretty tool as  mod_dphpbb3_last_topics I received a ton of such errors

Warning: cannot yet handle MBCS in html_entity_decode()! in helper.php in line 130

After googling I found this article. I tried to replace:

$title = html_entity_decode($title, ENT_QUOTES, 'UTF-8'); with $title = utf8_decode($title);

but it brakes UA/RUS lang. After brainstorm I made following changes in code:

Was:

$title = html_entity_decode($title, ENT_QUOTES, 'UTF-8');

Become:

$title = html_entity_decode($title);

pf changes

List:       openbsd-misc
Subject:    pf changes
From:       Henning Brauer 
Date:       2009-09-01 15:12:37
Message-ID: 20090901151237.GA11326 () nudo ! bsws ! de
[Download message RAW]

I have just committed a monster pf diff that is basically a rewrite of
the entire NAT part.

seperate rules for nat, rdr etc are gone.

nat and rdr become actions on regular rules.

simple rulesets are converted like this:

nat on $ext_if to ($ext_if)
becomes
match out on $ext-if nat-to ($ext_if)

more complex rulesets require some thought. since the weird
difference in matching order is gone (nat/rdr were first match) you
might have to reverse things and use your brains :)

the new NAT code is very very very flexible. every matching "match"
rule changes the adress on the fly (not really, but that is what it
looks like for subsequent rules), and you can nat or rdr multiple times.
for pass rules, only the last matching one matters.

so given
match out on $ext_if nat-to 1.2.3.4
match out on $ext_if to 1.2.3.4 nat-to 5.6.7.8
both rules will match and 5.6.7.8 will be the new src address.
however, with
pass out on $ext_if nat-to 1.2.3.4
pass out on $ext_if nat-to 5.6.7.8
ONLY the second one matters for NAT. same semantic that match rules
have for a lot of other stuff (altq, rtable, log, scrub).

the core logic, that relies on the big state table rewrite ryan and I
(with help from otehr developers of course) did last year, allows for
nat and rdr in any direction, but for now we prevent that in pfctl and
force nat outbound and rdr inbound, there are nontrivial implications
for the routing afterwards - if you rdr outbound, the packet will go
out on the interface it was seen on, even if the route for the address
rdr'd to actually points to a different interface. with NAT there are
similiar implications for the return traffic. since they are useful
nontheless I tend to remove the check in pfctl and document the
implications, but one thing after each other.

the diff is over 3000 lines, and makes pf about 800 lines smaller
than it was before. more cleanup is possible on top of this, but as
said before, one step at a time.

to add another data point how important hackathons are... this was
almost entirely written at c2k9 in edmonton and "finished" (minus a
few bugs fixed later) the week thereafter on bob's couch. while the
diff was almost entirely written by me, getting this actually into the
tree was a concerted effort by many developers. claudio adjusted ftp-proxy,
sthen ported that adjustment over to tftp-proxy, reyk adjusted relayd.
many people were testing a lot, I'm sure I forget a few, but at least
krw, sthen, claudio, reyk, dhill and dlg (who was insane enough to
throw this on production firewalls with significant importance) helped
a lot. igor did most of the manpage work. theo helped getting it in, a
lot. thanks guys.

and now it is your time. test this as much as you can, to avoid
surprises in 4.7, and bugs showing up after release... we really want
to find them beforehands, right?

henning

--
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam

http://marc.info/?l=openbsd-misc&m=125181847818600&w=2

Add favicon to joomla 1.5 site

 

1. login into admin section
2. go to template management
3. upload favicon into  image folder of your site
4. edit HTML of your tamplate
5. add following code:

<link rel="shortcut icon" href="images/favicon.ico" />

6. refresh your browser.

Have fun :)

Встановлення Xen на Debian Etch 4.0

Основна стаття http://mediakey.dk/~cc/installing-xen-on-debian-etch-40/
Переклад Михайло "veselujm" Веселовський

Протягом довгого часу я випробуав багато технологій віртуалізації: Xen, VMWare, і Microsoft VM. Я з впевненістю можу сказати що всі вони придатні для використання, але VMWare і Microsoft’s VM є більш вялими ніж Xen. Цих вихідних я розгорнув свій перший сервер на базі Debian Etch 4.0 і Xen. І все запрацювало з "коробки"

Тут я опишу кроки які я зробив щоб поставити Xen на Debian Etch:

sudo apt-get install xen-linux-system-2.6.18-4-xen-686 libc6-xen bridge-utils

Грузимось в нове ядро з встановленим Xen

sudo reboot

Потім настроюємо настройки мережі в /etc/xen/xend-config.sxp. Вмикаємо network bridge:

(network-script network-bridge)

Встановлюю xen-tools:

apt-get install xen-tools

Xen tools це пакет який включає в себе різноманітні утиліти для Xen, утиліта для створення віртуальних машин тощо.

Редагуємо настройки ядра і initrd в /etc/xen-tools/xen-tools.conf, так щоб вони були подібними до ваших системних.

Взнаємо як ядро і initrd називаються у вашій системі:

ls /boot/vmlinuz*
/boot/vmlinuz-2.6.18-4-686 /boot/vmlinuz-2.6.18-4-xen-686

і

ls /boot/initrd*
/boot/initrd.img-2.6.18-4-686 /boot/initrd.img-2.6.18-4-686.bak /boot/initrd.img-2.6.18-4-xen-686

Змінюємо рядки:

#
# Default kernel and ramdisk to use for the virtual servers
#
kernel = /boot/vmlinuz-2.6.18-4-xen-686
initrd = /boot/initrd.img-2.6.18-4-xen-686

В наступному кроці змінюємо наступні рядки в xen-tools.conf

dir = /home/xen
debootstrap = 1
size = 4Gb # Розмір диску
memory = 128Mb # Память
swap = 128Mb # Своп
fs = ext3 # використовувати файлову систему EXT3 для створення дисків
dist = etch # Стандартиний дистрибутив для встановлення
image = sparse # Визначаємо тип диску повний чи частинами

Створюємо домівки для наших віртуальних машин:

mkdir /home/xen
mkdir /home/xen/domains

Тепер ми готові до створення віртуальної машини

xen-create-image -hostname=mailserver -ip=10.0.0.21 -netmask=255.255.255.0 -gateway=10.0.0.1 -passwd

Після чого новостворену віртуалку можна запустити:

xm create mailserver.cfg

У випадку появи наступної помилки:

Error: Device 0 (vif) could not be connected. Backend device not found.

Потрібно перевірити чи ви увімкнена підтримка network bridge, “(network-script network-bridge)”, в /etc/xen/xend-config.sxp після додавання потрібно пергрузити демон xen /etc/init.d/xend restart. Здопомогою команд “xm list” чи “xentop” можна подивитись яка віртуалка зараз крутиться:

debian5:# sudo xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 874 1 r----- 657.9
mailserver 3 128 1 -b---- 8.0

Базуючись на моєму досвіді використання і впровадження технолоїй віртуалізації , а думаю що Xen це саме те для впровадження Linux і Linux-based технологій і це показує що вони готові до використання вже тепер. Технології віртуалізації вже тепер готові до впровадження в великих компаніях і дата центрах, і вони допомагають спростити настроювання, впровадження і встановлення працівникам, І я думаю що найближчі роки технології віртуалізації будуть грати важливу роль на серверному ринку.