After more than three years of using Suse 9.3 with Plesk 8.1 on one of my VPS, I decided that it is time to update to OpenSUSE 11.1 with Plesk 9.2.1 control panel. The update process went very well, here are the steps involved:

1. create a full backup of your vps (databases, websites, accounts, emails, ...). I have used "tar" command for that.
2. in plesk 8.1 control panel, do a complete backup (you need plesk backup module to be installed), or if you prefer the command line you can use the following command:

# /usr/local/psa/bin/pleskbackup all

Since version 9.x, the structure of Parallels Plesk Panel backup has been changed. Plesk backup created with Plesk Backup Manager is not just one file but a number of files and directories under backups directory /var/lib/psa/dumps. So, you will need to convert your backup file created in plesk 8.1 to be compatible with plesk 9.x. It's a very simple process, see step 3.

3. convert the created backup file to be compatible with plesk 9.x

# /usr/local/psa/bin/pre9-backup-convert -v convert -d /var/lib/psa/dumps/

where /var/lib/psa/dumps/ is backups directory on the server with Parallels Plesk Panel 9

4. restore the backup files to use them with plesk 9.x. It can be done using the web interface, Home -> Backup Manager -> Server Repository, click the backup name to enter the backup details page and select the required restoration options and click Restore to start the restoration process.

If you would like to use command line to restore your domains, clients, server configuration, ... then you can use the following command:

# /usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/ -level server -verbose -debug

You can restore only clients or domains, for more options see:

# /usr/local/psa/bin/pleskrestore --help

Note: I had a small problem and I found that it is not possible to have a client with the same name as your name in Plesk Admin Profile. Maybe it is stupid, but I had some errors and only after I changed the name in Admin Profile (in Plesk control panel) to be different, I could restore without any problem everything.

I think that's all what I did, from what I remember. If something is missing I am sure you can find a lot of useful stuff using our friend google.

Other useful stuff:

1. Plesk 9.x support as well postfix, so if you want to change from qmail to postfix, try that:

# /usr/local/psa/bin/autoinstaller --select-release-current --install-component postfix

if you are not happy, you can switch back to qmail:

# /usr/local/psa/bin/autoinstaller --select-release-current --install-component qmail.

If you are not sure if you are using qmail or postfix there are many ways to find that, one is to look in Plesk Control Panel on the Services management page {Home -> Services Management} if you have SMTP Server (Postfix) or SMTP Server (QMail)

If you decide you want to switch back, simply, do it, the emails are not lost, don't worry.

2. Replace Horde webmail with AtMail

One of the many new features of Plesk 9, is the option to choose a different webmail client. The default webmail client Horde can be replaced if you are looking for something a bit lighter, AtMail. You need to install from Plesk Control Panel, both webmail clients, and to switch between them:

• Log into Plesk.
• Chose the domain which you want to use another webmail, enter on “Mail Accounts” page
• Click the “Mail Settings” icon
• Switch the “WebMail” to “AtMail (default is Horde)
• Click “OK”

If you decide you want to switch back, simply reverse the procedure, the emails are not lost, don't worry.

That's all.

References:

http://kb.parallels.com/en/5819
http://kb.parallels.com/en/5801
http://kb.parallels.com/en/952
http://kb.parallels.com/en/5969
http://kb.parallels.com/en/5864

I wrote a small article for a internal magazine and few of my friends wanted me to post it to this blog.

This is for people who are new to GDB and still exploring itz features. So if you’ve used GDB for more than few weeks please ignore and skip

GDB – Scripting

A good majority of novice programmers tend to use printf functions to trace function calls and to printout the debug data. This forces you to change the code and compile again and again. To eliminate these superfluous tasks from your day-to-day work, use GDB. The GDB has facilities for scripting and helps in saving plenty of your time.

Tracing Function Calls

If you want to know whether a function is called or not, create a break point and write a simple script.

<code>

#Set the breakpoint

(gdb) b mapi_sync

Breakpoint 1 at 0x7fffd75f36e2: file camel-mapi-folder.c, line 741

#Tell GDB what to do when the breakpoint is reached

(gdb) commands

Type commands for when breakpoint 1 is hit, one per line.

End with a line saying just “end”.

> continue

> end

(gdb)

</code>

continue – Come out of break and continue

end – terminate command list

Run the program now. The GDB prints the function name when the breakpoint is hit and automatically continues running the program.

Breakpoint 1, mapi_sync (folder=0xc9c1a0, expunge=0, ex=0xf3a0c0) at camel-mapi-folder.c:741

741             CamelMapiStore *mapi_store = CAMEL_MAPI_STORE (folder->parent_store);

Using the GDB Scripts for Analyzing the Data

Suppose that you have a singly-linked list that has strings in it. At some point, you might want to know the contents of the list. To do this, use the GDB scripting instead of adding the debug statements in your code.

<code>

#Example for gslist traversal.

define p_gslist_str

set $list = ($arg0)

while ((GSList *)$list->next != 0)

p (char *)(GSList *)$list->data

set $list = (GSList *)$list->next

end

end

document p_gslist_str

p_gslist_str <list>: Dumps the strings in a GSList

end

</code>

Add the above snippet into a file and load it into the GDB as follows:

<code>

(gdb) source /home/jjohnny/scripts/gdb/gslist.gdb

</code>

Now, anywhere you want to take a look in the GSList, simply break and

<code>

(gdb) p_gslist_str server_uid_list

$17 = 0x7fffd81101b0 “7666BC1E000000015870BD1E00000001”

$18 = 0x7fffd810e330 “7666BC1E000000015970BD1E00000001”

$19 = 0x7fffd810cbe0 “7666BC1E000000015C70BD1E00000001”

</code>

Simple scripts thus can save you a lot of time from adding or removing the debugging statements from your code. Now go ahead and create a suite of scripts to aid the library you are writing.

More cool developer tricks later. Have fun !

— End —

Thanks to Radhika for editing the article.

Btw when is Archer branch  (Python scripting) getting into GDB ? I’ve been using it a bit .

Nowadays more and more organisations will use an intercepting proxy to give you access to internet. Last week I had the pleasure to use again such a system. To use is an exaggeration as my opensuse 11.1 box with kde4.3 rc1 connected to the wireless network (network manager) but refused to give me access to the authentication page in the browser.

I did all the decent tests that my brain and time allowed me. Checked the ip, checked gateway and checked dns. They seemed ok.

To make frustration even bigger I was able to connect to th very same network with a kde4.3 beta1.

Woohoo ! After a long delays and issues (in the last few days) I’ve managed to install openSUSE 11.1 in my PS3.  Running a full blown desktop is very sluggish. Reminds me of my first computer (amdk6 500mhz). Some screenies :

Now onto get the Cell SDK running … Synergetic Processing Elements (SPE) here i come !