Konversation: Error 65 and 3

I haven't used Konversation for a few weeks, and when I did.. Konversation returned this error:
Server sent error 65: Access to restricted port in POST denied.
and
Server sent error 3: Could not start process Unable to create io-slave: klauncher said: Unknown protocol ". .



It's been like this for three weeks and I was forced to rely on IRSSI and IceApe's Chatzilla. My cravings for Konversation grew stronger that I finally ranted about this at #ubuntu-ph. I gave Jucato and Ahmuck this error:

0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbf909888 in ?? ()
#2  0xb79f1ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3  0xbf909874 in ?? ()
#4  0xb793ee96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5  0xb793eca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6  0xb744cad9 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4
#7  0xb74634de in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4

and this

Failed to open device
konversation: WARNING: Cannot execute call to system.login: empty server URL
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
konversation: ERROR: <qt>Server sent error 3: <b>Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
.</b></qt>
konversation: ERROR: <qt>Server sent error 3: <b>Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
.</b></qt>
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.search: empty server URL
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.categories: empty server URL
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.customfields: empty server URL
dax@knightlust:~$ QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
KCrash: Application 'konversation' crashing...

It was Jucato who asked the maintainer of Konversation (Sho) what's happening.

Jucato: That has something to do with the KAddressBook integration, from the looks of it
Jucato: My guess is that he's using eGroupWare or IMAP to store his address book on a server, and something goes wrong in KIMProxy
Jucato: If it's a dialog box, you can be fairly sure it's not Konversation, we don't use them
Jucato: "kresources/egroupware/kabc_resourcexmlrpc.cpp: QString msg = i18n( "Server sent error %1: %2" ).arg( error ).arg( errorMsg );" btw
from kdepim
Jucato: Perhaps he set up eGroupware, but removed eGroupWare again but forgot to remove the resources in Kontact/KAddressBook

So there it is.... the solution to my problem. Sho was right.. I used (past tense) eGroupware and forgot to delete any reference to it from KAddressbook.

I deleted it.. and it worked. Ha! I said my goodbye to Chatzilla (no.. I'm still fond of IRSSI) and went to bed. This all happened last night.

For those curious how to remove the XML-RPC entry in KAddressbook, just go to Settings > Show Extension > Address Books. That's where you delete it.

Blogged with Flock

Gutsy - Firefox is disappointing

Since Gutsy Tribe 3, Firefox never really worked. Oh sure, the Addons installs and allows me to surf, but that's it. Everytime I open the Preference window, Bookmark a site, or even download a file... it just crashes. As long as I open a window in Firefox (except Organize Bookmarks and Download windows), I really can't stop Firefox from crashing.

It's been over two months now, and frankly, I'm disappointed. I have Flock installed, but I'm still craving for the red fox! Today, after working on a few (around 15) tabs, it crashed again... and lost 2 hours of work. I keep on forgetting that working in a browser is a bad idea. I'm fed up! I just uninstalled it and will probably wait for the Beta release before I try it out again. I'm now working with IceApe as my primary browser and glad that it's stable enough for me to do my thing.

Come to think of it, it's been a while (like more than a month) since I last saw any updates on Firefox.... I don't know what the hell the Mozilla Team's doing, but I just signed up on their list and will help on my free time. Need my addiction satisfied.

Blogged with Flock

Confused and Irritated

Recent life-changing events forced me to contemplate on my life and my priorities. After being a bum for a few months - with funds fast depleting - I decided it's now time to get myself a day job. I'm well rested and very much eager to interact with the corporate world again. Let's get it on!

The confused and irritated part was caused by a surprise. This shit happens, and I'm just a victim of synchronicity. But I'll also face it head on!

When I need think, I usually get a piece of paper and a pencil and write down what I can and cannot do. And since I'm stuck in front of my laptop, I'll be doing that right here, right now. I've been using the SWOT method for a long time now, but this time I'll just focus on strengths and weaknesses and my computing and management skills.

Strengths:
System Administration

• LAMP
• eGroupware and PHPGroupware
• Dovecot
• Postfix
• Sendmail
• Dancer IRCD
• Subversion
• Installation and Configuration of Debian, Ubuntu, and Fedora
• IRC Bots (Eggdrop and Supybot)
• DNS Administration via EditDNS and DynDNS
  
• SSH and FTP Configuration
• Samba
• Drupal, Joomla, Mambo, e107, PHP-Fusion
• Wordpress
• Moodle
• Search Engine Optimization
• Software Testing and Quality Improvement
• Exposure to Open Source Processes
• LAN Networking
• Software/Computer Forensics
• PGP and SSH
  

Programming

• C++
• PHP & HTML
  
• KDevelop
• NetBeans
• Anjuta
• Geany
• MS Visual C++ 6
  

Management

• Managing Accelerated Performance (MAP)
• Knowledge Management
• Project Management
• Performance Management
• Six Sigma Training
• Risk Management
  

Weakness:
System Administration

• Cyrus and Courier Email Servers
• Kolab, Scalix, and Zimbra
• Jabber
• Asterisk
• BIND
• JBoss
• Novell/SUSE and Red Hat
• LDAP
• Kerberos
• SpamAssasin
• ClamAV
  
• Squid
• IPTables
• Sugar CRM (or any CRM Applications)
  
• Tiny ERP (or any ERP Applications)
• Chrooted/Jailed Accounts
• Virtual Email Accounts using MySQL
• Clustering
• Solaris
• WebSphere and Domino
• MSSQL
• LTSP
• WAN Installation and Management
  

Programming

• MS Visual C++ 6, I've relied heavily on this.
  
• C++ skill not enough, at least for Linux.
  
• PHP skill not enough
• Java
• Any Scripting Language
  

Management

• Not enough experience
  

So there it is.... based on the list above, I guess I'll have more chances of getting a Sys Admin job. But also based on the list above, there's a lot more stuff I need to learn before I consider myself qualified to be a Sys Admin.

Now the hard part, it's Baguio. There's very, very few companies who use Unix/Linux for their servers, much less for their workstations. I'll see what I can do. But for now, and the next couple of days, I'll be very busy studying and working on my skills.

Blogged with Flock

Limits.conf

Setting limits on what processes can be very helpful for those testing out various distributions - Gutsy in my case. There will always be rogue applications spawning tens, sometimes hundreds, of same processes due to bugs. And this almost always happens on Alpha versions. So beware. If you're not up to it, DO NOT INSTALL AN ALPHA VERSION!

Here's one of the tips I learned. You see, a bug in KMail caused it to create multiple KMail processes. If you don't set a limit, it'll slow down your system. Worse, your system would freeze rendering it unusable. Here's how you set limits on running processes.

Edit /etc/security/limits.conf as root and append the following lines.

* soft nproc 200
* hard nproc 300

When you hit the 200th process, it'll warn you.
And your system won't allow you to go beyond 300 processes.

This is very, very useful for shell providers. You can even limit a user to 5 or even 2 processes. But for a tester like me, 300 processes is enough. It'll make sure I can run all the programs I need without worrying about rogue apps going nuts all over my system.

Blogged with Flock

Setting up Subdomain in Apache2 and EditDNS

So, you want to setup a sub-domain? There's 2 things you need to do.

• Configure Apache2
• Add a Sub-domain to your EditDNS account (or your domain providers' control panel)

Configuring EditDNS
You should setup a subdomain on EditDNS first. Why, because it'll take time to propogate. That'll give you enough time to edit Apache's configuration files.

Before doing anything, make sure you can access your domain. If you can, then let's go ahead and create a sub-domain.

In the Record Name, type in subdomain.yourdomain.com
In the Type, select CNAME
Leave AUX and TTL alone
In the IP/Host, type in yourdomain.com
Click Add
Repeat as needed

Here's my EditDNS Entry. I added blog, bugs, forum, learn, and wiki to my account.



Apache2 Configuration
Launch your favorite text editor and edit the default file as root. The file is in the /etc/apache2/sites-available.

sudo nano /etc/apache2/sites-available/default
kdesu kate /etc/apache2/sites-available/default

And append this to the file:
<VirtualHost *>
        DocumentRoot "/var/www/subdomain/kb/"
        ServerName kb.knightlust.com
        ServerAdmin dax@knightlust.com
        ErrorLog /var/log/apache2/kb.log

        <Directory /var/www/subdomain/kb/>
                Options Indexes FollowSymLinks MultiViews +Includes
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>
</VirtualHost>

Explanation:

• The DocumentRoot should be pointed to the directory where you installed your site or script. And it should be enclosed in quotation marks. Don't forget that.
• ServerName should have your subdomain
• ServerAdmin and ErrorLog is optional.
• The <Directory> should also be pointed to where you installed your site or script.

Here's mine:



And here's for my other subdomains. So you see, just edit the entry above to fit your configuration.



Now before you reload Apache2, you need to make sure that the default file is linked in /etc/apache2/sites-enabled. Otherwise, it just won't work.

If there's no linked file there, issue this command:
sudo a2ensite default



Once everything's done, go ahead and reload Apache:
sudo /etc/init.d/apache2 reload

Blogged with Flock