IPSec VPN Configuration on Ubuntu 18.04

This was something I had to do repeatedly on all my Linux laptops. I found that you must follow *both* 2 articles listed below in the same order, to get it working!

[1] https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#linux

[2] https://github.com/nm-l2tp/NetworkManager-l2tp/issues/38#issuecomment-303052751

The package to install in Ubuntu 18.04 can be found here.

HP and Windows - A Jealous Affair

I bought my HP laptop 3.5 years ago. It came pre-installed with Windows 8. As a primary Linux user, I installed Ubuntu with a intention of dual-booting with using Ubuntu primarily. However, HP always showed only Windows in the bootup, and by default it goes into Windows - never letting me sign in. Boot-repair-disk helped me fix this issue. Nevertheless, every time Windows upgraded, it broke the fix, and made the computer go into Windows by default. I tried to stop Windows upgrade after fixing this several times using Boot-repair-disk, as I got fed up with this. However, Windows upgrade worked on its own for "critical system/security updates". I was unable to turn these off. Guess what? These automated updates broke my boot as usual, leaving Windows the only option. 

It was not even possible to change the boot to Ubuntu, or to bring the menu at start up. By that time, I got to know that this was a bug (or a feature?) from HP that Windows was hard-coded. I also did not have this issue in my other new laptop. Why I did not completely uninstall Windows? Sometimes I need it: printer, a few wifi configurations, and some docx, pptx files sent by others - these are the reasons behind my occasional usage of Windows. But every time I go to WIndows, it breaks my grub, leaving it as the only option to log in to.

By this time, Boot-repair-disk stopped working. However, I have an earlier version stored in my pen drive, which luckily works well. So I assume that a later "fix" in Boot-repair-disk broke it. Even efibootmgr did not work as expected. All I was able to do was to change the option for the next boot. Not forever! Eventually, I had to follow this work-around to get this running.

First, find your current status:

$ sudo efibootmgr
[sudo] password for pradeeban:
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,3003,0000,0002,0004,2001,2002,2003
Boot0000* rEFInd Boot Manager
Boot0002* ubuntu
Boot0003* Windows Boot Manager
Boot0004* ubuntu
Boot0005* EFI USB Device (General UDisk)
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* Internal Hard Disk or Solid State Disk
Boot3001* Internal Hard Disk or Solid State Disk
Boot3003* Internal Hard Disk or Solid State Disk

Now, ideally you should be able to do the below:

$ sudo efibootmgr -o 0002,0004,3003,0000,2001,2002,0003
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0004,3003,0000,2001,2002,0003
Boot0000* rEFInd Boot Manager
Boot0002* ubuntu
Boot0003* Windows Boot Manager
Boot0004* ubuntu
Boot0005* EFI USB Device (General UDisk)
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* Internal Hard Disk or Solid State Disk
Boot3001* Internal Hard Disk or Solid State Disk
Boot3003* Internal Hard Disk or Solid State Disk

But, unfortunately, it was not working as expected. Rather, I had to follow a work-around of changing the boot order just for the next boot:

$ sudo efibootmgr -n 0002

Now add this below line to /etc/rc.local to repeat this same action every time Ubuntu loads:

sudo efibootmgr -n 0002

After this work-around, the grub loads successfully, and I can choose Ubuntu (among the many other options) easily as before. I did not log in to Windows after this fix. I am sure Windows will find a way to easily break this work-around once I log in to it.

Currently this work around makes sure that every time I log in to Ubuntu, Ubuntu sets the next boot to be Ubuntu/grub option. However, if I log in using the Windows entry in the grub, this bit won't be set. So the next time, it will log in to Windows directly, and thus breaking this cycle. However, when that happens, I just need to use Esc -> F9 sequence to just log in to Ubuntu once. After that, Ubuntu will be back as long as I keep using only it. In other words, Ubuntu boot will be fine as long as I do not log in to Windows.

You do not see Ubuntu upgrades breaking my Windows boot. Windows is such a jealous affair.

The new laptop and the elephant speaker..

The new Asus laptop and the elephant speaker

Being a student volunteer in a conference was a remarkable experience. I was able to involve deeply in organizing the conference event on-site, and experience how things are done. I was able to get a first hand experience and have a different perspective as I have never been in the other side of the table. I was always a participant. This 2nd of July, I also won a laptop in a lucky draw. It was interesting as I have never won any lucky draws before. :) Also all of the student volunteers received a beautiful elephant speaker.

Now it has Windows 10. I should probably install Ubuntu in a dual boot, or rather wipe Windows and install Ubuntu solely. But I am lazy to mess up with the computer yet. So letting it rest mostly. Currently I have 3 laptops for me, with the one that I am using - an HP with a dual boot of Ubuntu 16.04 and Windows 10, this new Asus with Windows 10, and my old one with Ubuntu 13.10 - if I remember correctly. Those days I was upgrading the OS for each Ubuntu releases. Now I like the stability and upgrading for only LTS.

Upgrade to Xenial Xerus, Virtualbox, and more..

Each time upgrading the Ubuntu is like taking a challenge. When I bought this laptop in 2014 February, I installed Ubuntu 13.10, and later upgraded it to the next LTS version in August (14.04.1). Now this is my second upgrade in this laptop, again to the next LTS version (16.04.1 - Xenial Xerus). While this is all exciting, all upgrades come with some breaks in previously working and stable software. This time, VirtualBox is broken. I am sure it is not the only one though.

So I got this error, when I tried to open an existing VM or create a new VM in the VirtualBox following my upgrade.

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.



When I tried to do as suggested:

root@llovizna:/home/pradeeban# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMSERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-4.3.0.crash'
Error! Bad return status for module build on kernel: 4.4.0-31-generic (x86_64)
Consult /var/lib/dkms/vboxhost/4.3.28/build/make.log for more information.
 ...failed!
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)

Finally, I had to uninstall and reinstall everything

 
sudo apt-get remove virtualbox-\*
 

Downloaded the relevant package for Xenial Xerus 64 bit and installed again.

Luckily, all the VMs and virtual hard disks were safe and ready to use (thanks to virtualization!)

Bad guy Windows and good guy Ubuntu

A few moments ago I upgraded my Ubuntu 14.04 LTS to Ubuntu 16.04.1 LTS (Xenial Xerus). I waited for the service pack 1 to be released in the end of July, and hence the delay. Everything was smooth, and my dual boot runs perfectly well with Windows and Ubuntu just as before. On the other hand, every time Windows does a minor upgrade (not just the Windows 8 to Windows 10 upgrade), it breaks my grub and makes Windows the default and only option, making Ubuntu unreachable. Luckily I have a Lubuntu-based software, named boot-repair-disk that can fix these boot issues. The current version of the software does not work for Windows 10. However, I have a previous version with me that just works fine.

I am not entirely sure why Windows made each upgrade to break the grub. Is it made intentionally, or is it that hard for the engineers to fix this minor bug (or may I say, feature?). This is so annoying and inconvenient. This makes Windows look like a big bully.

So now I have the latest LTS version, and I will upgrade again in 2018 August with 18.04.1 LTS. I made some interesting observations during the upgrade.

Configuring encfs ├──────────────────────────────────────────────────────────────────────────────────────────┐ 
 │                                                                                                                                                                                                        │ 
 │ Encfs security information                                                                                                                                                                             │ 
 │                                                                                                                                                                                                        │ 
 │ According to a security audit by Taylor Hornby (Defuse Security), the current implementation of Encfs is vulnerable or potentially vulnerable to multiple types of attacks. For example, an attacker   │ 
 │ with read/write access to encrypted data might lower the decryption complexity for subsequently encrypted data without this being noticed by a legitimate user, or might use timing analysis to        │ 
 │ deduce information.                                                                                                                                                                                    │ 
 │                                                                                                                                                                                                        │ 
 │ Until these issues are resolved, encfs should not be considered a safe home for sensitive data in scenarios where such attacks are possible.                                                           │ 
 │                                                                                                                                                                                                        │ 
 │                                                                                                                                                                                                    │ 
 │                                                                                                                        

So, EncFS is not secure after all.

The other prompt that caught my attention was the below:

 Configuring davfs2 ├──────────────────────────────────────────────────────────────────┐                        
                         │                                                                                                                                                         │                        
                         │ The file /sbin/mount.davfs must have the SUID bit set if you want to allow unprivileged (non-root) users to mount WebDAV resources.                     │                        
                         │                                                                                                                                                         │                        
                         │ If you do not choose this option, only root will be allowed to mount WebDAV resources. This can later be changed by running 'dpkg-reconfigure davfs2'.  │                        
                         │                                                                                                                                                         │                        
                         │ Should unprivileged users be allowed to mount WebDAV resources?                                                                                         │                        
                         │                                                                                                                                                         │                        
                         │                                                                                               []                                                 │                        
                         │                                                                                                                      

As of now, everything seems to work just fine after the upgrade. I will update further when I find out whether something is broken due to the upgrade, later.

Why you should wait more to upgrade to the next LTS..

Notify me for long-term support versions

There are still a few of us, who prefer to be safer. We often upgrade only when an LTS of Ubuntu is released. However, not most of us realize that we should wait till the point release is available, letting the critical bugs found by the users fixed. The point releases are usually made available around the end of July. Ubuntu 12.04.1 will be available this month. Update manager will list 12.04 as available for the 10.04 users, only when 12.04.1 is released. That means, it won't be shown to the users who have set their system to notify only when LTS is released, till the first point release is released.

However, if you are still in a haste to go 12.04 from your stable 10.04, you can do this by "update-manager -d" I tried above, and it was a failed attempt, and hence will discourage anyone else to go to 12.04, directly from their 10.04, for their mission critical systems. Once 12.04.1 is released, it will be listed as 12.04 in your update manager, and that will be the ideal time to upgrade. I tried as above, which successfully downloaded the upgrades (took 26 hours in a speed of 60 kB/s), installed, and restarted. But it failed to restart, even after attempting all the suggestions on the Internet. When I tried with the 11.10 DVD (I didn't have 12.04 DVD with me, and I didn't have time to download and burn one, or get one from someone else), it showed the current operating system as 10.04, and from there I picked the option to "Upgrade" using the DVD. My file system was safe, along with all my documents. Some of the applications I had in my 10.04, had to be reinstalled for my new 11.10. Anyway, I smoothly upgraded 11.10 to 12.04, as expected, within 5 hours. I then installed the missing applications. Everything is safe, and now I am with 12.04.

Now I am just analyzing what might have happened initially to cause failure in my upgrade. It seemed to be an issue that happened when upgrading the Operating System during the final restart, as the operating system was still detected as 10.04 when I inserted 11.10 DVD. (It considered it an upgrade from 10.04, and not an installation replacing 12.04). I like that installing on top of 10.04 option, without formatting the entire disk, or without leaving the previous data in another partition, wasting the space.

Post-mortem

The page started to show the below message after the restart.

The disk drive for / is not ready yet or not present. 

Continue to wait; or Press S to skip mounting, or M for manual recovery.

Clicking S complained missing /tmp. Further S lead me to an empty black screen that takes nowhere. Go for M 

Root filesystem check failed.

A maintenance shell will now be started.

CONTROL-D will terminate this shell and reboot the system.

Give root password for maintenance 

(or type Control-D to continue):

and the manual fsck attempts did no fix.

fsck -f /dev/sda1

vi /etc/fstab 

showed

/mnt/4096 Mb.swap none swap sw 0 0

and

vi /etc/mtab

showed

/dev/sda1 / ext3 rw 0 0

Copying the contents of fstab to mtab and restart did no help, though suggested in some forums.  

mount /dev/sda1 /

mount: /dev/sda1 already mounted or / busy

mount: according to mtab, /dev/sda1 is already mounted on /

Remounting with rw permissions to follow the below commands as suggested.

mount -w -o remount /

dpkg --configure -a

apt-get install -f

dpkg --configure -a

gave

dpkg: error: parsing file '/var/lib/dpkg/status' near line 28305 package 'xmind'.

blank line in value of field 'Description'.

Removed the paragraphs defining xmind from the files /var/lib/dpkg/status and /var/lib/dpkg/available. It also complained about virtualbox-2.2, which I eventually removed as well.

Further fix attempts took me to the below shell.

Gave up waiting for root device. 

Common problems: 722988907ca

-  Boot args (cat /proc/cmdline)

- Check rootdelay = (did the system wait long enough?)

- Check root - (did the system wait for the right device?)

ALERT

/dev/disk/by-uuid/c67309e6-6099-40db-8b1b-1722988907ca does not exist. Dropping to shell.

Removed the UUID definitions,

root=UUID=.....7ca

from the entries in

/boot/grub/menu.lst

Making 

/boot/vm......generic

root=UUID=.....7ca ro quiet splash

to 

/boot/vm.....generic

ro quiet splash 

in the entries, as discussed here.

However, these fixes eventually took me to the shell from all the kernel images, letting me explore further issues. I finalized, installing from DVD would be a smarter option, as nothing I will lose.

Conclusion 

Lack of documentation or help is surely a frustration for an average user, in case of a failure like this, though it is not so common. We should focus more on community documentation to avoid turning the users off. My suggestion for a normal user to take a backup before upgrading such, and in case of failure, try if you can fix it, and if not, go for reinstalling on the same partitions, without formatting.

run-init: /sbin/init" I/O error "kernel panic not syncing: Attempted to kill init!

My Ubuntu 10.04 LTS / 64 bit failed to start with the error message, "run-init: /sbin/init" I/O error "kernel panic not syncing: Attempted to kill init!", with the CAPSLOCK constantly blinking, all of a sudden. It was working very fine, till the day before, and all of a sudden this failure happened without any apparent reason. The recovery mode and the attempts to log in through the previous versions of the kernel were not successful either. When logging in through a Live CD, it suggested no error on disk and it had been mounted properly too.

So I tried to use "mkinitramfs" from /boot to build mkinitrd and rebooted. "update-mkinitramfs" (sudo, of course!) from the live CD didn't work either, as the drive was found to be read-only media just for that command! Similarly also tried to get initramdr from the LiveCD using the same command, and also downloaded from the relevant site, and restarted after adding the relevant menu entry to /boot/grub/grub.cfg and rebooted. Still no luck.

menuentry 'Ubuntu, with Linux 3.0.0-14-generic' --class ubuntu --class gnu-linux 
--class gnu --class os {
    recordfail
    set gfxpayload=$linux_gfx_mode
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set=root 890aebc7-6238-4ce9-99d1-356b3f0163a4
    linux    /boot/vmlinuz-3.0.0-14-generic root=UUID=890aebc7-6238-4ce9-99d1-356b3f0163a4 ro   quiet splash vt.handoff=7
    initrd    /boot/initrd.img-3.0.0-14-generic
}
menuentry 'Ubuntu, with Linux 3.0.0-14-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set=root 890aebc7-6238-4ce9-99d1-356b3f0163a4
    echo    'Loading Linux 3.0.0-14-generic ...'
    linux    /boot/vmlinuz-3.0.0-14-generic root=UUID=890aebc7-6238-4ce9-99d1-356b3f0163a4 ro recovery nomodeset
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-3.0.0-14-generic
}

There are many threads on "Kernel Panic". But only a very few comes to the point, and only a tiny bit of those sites actually suggests some fix to try, where many of those threads are still unanswered questions for years. From what I learned, this "Kernel Panic" seems to be one deadly issue that can happen for multiple reasons - and is not an easy fix - except by the means of compiling the kernel or simply reinstalling the operating system. After trying all possible attempts to fix this, and also after trying to compile kernel, I decided the time invested on this is a bit waste. Hence I backed up everything on my Ubuntu to my windows partition through the Live CD and re-installed Ubuntu.

I have installed Ubuntu 11.10 (Oneiric Ocelot), where I had 10.04 before. The first impressions were not so nice, thanks to the new Unity interface. However, "sudo apt-get install gnome-shell" followed by "sudo apt-get remove unity" resolved the issue, letting me switch to gnome3 interface. :) Now I am awaiting the release of Ubuntu 12.04 LTS to upgrade in a few months.

Apart from this Kernel Panic, there were a few other remarkable events too. One was the GSoC awareness session at the University of Jaffna (Presentation Slides). The WSO2 offsite at Avani Hotel, Bentota was remarkable as well. These were the remarkable events of the first fortnight of the year 2012. This year seems to be so eventful!

I concluded, my computer is asexual (or engaged with something else).

Just noticed the following as a friend's facebook status update.

Is Your Computer a Boy or a Girl?

It’s pretty easy to find out what gender your computer is.

Follow the instructions.
.........
1) Open your notepad
2) Type or copy paste: CreateObject("SAPI.SpVoice").Speak"I love you"
3) Save as computer_sex.vbs
4) Run the file. (just double click)

If you hear a male voice, congratulations, you have a boy if woman’s, well, it’s a girl.

I have a baby boy :)

What about you?

So I opened my gedit editor, and copy-pasted, and saved it in the desktop of my Ubuntu machine, and double clicked it. Instead of *saying* anything, it just opened the file in another gedit window with the warning header,

"This file (/home/pradeeban/Desktop/computer_sex.vbs) is already open in another gedit window. gedit opened this instance of the file in a non-editable way. Do you want to edit it anyway?"

I concluded, my computer is asexual or engaged with some other stuff (already open in another.. ;)).

Wait; at least you could have mentioned the fact that your sex-trick works only on a windows machine.. :D

Ubuntu and SLT ADSL

When it comes to Linux, most of the software for the commonly used peripherals remain unsupported in Sri Lanka. Sometimes the software can be downloaded from the community forums, though the remaining stuff still, is on your hands. Recently when I switched to Ubuntu 9.04 (Jaunty), completely from Windows XP, I had to replace my Prolink H9601 ADSL USB Modem with a router since SLT(Sri Lanka Telecom) explicitly mentions that the above modem suits for Windows only. There was a program named UbuDSL which works for Prolink modems *sometimes*, on Ubuntu.

Configuring the CT-5624 4 port ADSL Router was a piece of cake though.

[1]. Just open http://192.168.1.1 and enter both username - admin and password - admin.

[2] Quick Setup will take you to the web page where you will have to input the username and password given by SLT. After this click 'Save & Reboot'; wait for the router to reboot. After rebooting you will mostly be able to connect to the Internet.

The below describes the further configuration, if the above fails. Since the router comes preconfigured for SLT it should work without these though.

[3]. Configuring Computer [From the SLT Router guide - for Windows Operating System]

TCP/IP Properties (You will not need to do this mostly.) .

Use IP address in the range of 192.168.1.2 - 192.168.1.254

Subnet mask 255.255.255.0

Default gateway 192.168.1.1

Preferred DNS Server 203.115.0.46

Alternate DNS Server 203.115.0.47

[4]. Configuring CT-5624

After the initial configuration, as mentioned in [1], Select WAN under Advanced Setup tab, and Click Edit.

VPI = 8

VCI = 35

[Next]

Connection Type - PPP over Ethernet (PPPoE)

Encapsulation Mode - LLC / SNAP-BRIDGING

[Next]

Enter the username and password provided by SLT.

[Next]

Enable WAN Service

[Next]

Check the summary and Save if it is correct. Save/Reboot.

Wait for the router to reboot.

This should work by now.. :)

Click the DNS Server option under Advance Setup to set the DNS Server address.

Log in Screen Issue - Ubuntu

Last night I was working with some Localized applications in Tamil Language in Ubuntu 9.04.

For that I had changed my keyboard settings to ta-IN using System > Preferences > Keyboard, and choose Tamil India. For the first time, I forgot to switch back to the English Keyboard before I log out.

Today, at the log in screen, I tried to enter my user name. To my bad, it was entering Tamil characters, which made logging in impossible. I changed the language there at the log-in screen, but it just changed the log-in screen interface language, not the input language.

I tried to recover using CD, and failed. Similarly when I tried to go to the console using Alt+Ctrl+F1, still the keyboard input to the username field must have been in Tamil, thus giving diamonds instead of the letters. Finally in the Grub, I choose somewhat earlier version of gnome-terminal before the update to the later Ubuntu version, as the log in option, where I was unable to log in, yet still able to log in using the console (Alt+Ctrl+F1), as the keyboard was still EN-US there.

Then after some serious examination of the web and bugging my pals, I found the solution.

In /etc/default/console-setup

I found the two parameters were set to refer to India and Tamil.

sudo vi /etc/default/console-setup

I modified them to refer to EN-US.

XKBLAYOUT = "us"

XKBVARIANT = "en"

After saving the console-setup file, I restarted the computer. Then I was able to type in EN-US, and I successfully logged in.

Now I will make sure my keyboard settings is not Tamil or Arabic before I log out, to prevent this issue repeating again. Seems sticking to EN is mostly the safe.

[Update as on Nov 2009]

Since Ubuntu Karmic Koala has the input language and keyboard as a setting option in the log in window itself, it seems this issue has been fixed for Karmic Koala.

Gtk-WARNING

When I was running a GUI application in IDEA8, I was continuously getting the error message:
(:10099): Gtk-WARNING **: Attempting to add a widget with type GtkButton to a GtkComboBoxEntry (need an instance of GtkEntry or of a subclass)

(:10099): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

(:10099): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed

in the IDEA output window.

I later found that this issue is listed here in IntelliJIDEA bug database.

Finally I was able to fix the issue by simply switching back the operating system theme to the default one [Earlier I had Mac4Lin], though smarter solutions may exist.

Tracker Applet

Tracker Applet.
"There was an error while performing indexing: Index corrupted."

Since I upgraded to Ubuntu jaunty (9.04) from 8.10, I am getting the above message frequently. Which will stay there, asking for an indexing, where it will never disappear even if we positively respond to its query. So regardless of our response, this message thingy will be popping up again and again.

I found a temporary solution for this well known bug from web.
sudo apt-get install tracker-utils
tracker-processes -r # --hard-reset

This bug was not appearing after that for a long time, but appeared again today!
Had to do tracker-processes -r # --hard-reset again.

The terminal output follows:

pradeeban@pradeeban:~/c$ tracker-processes -r # --hard-reset
Found 157 pids...
Found process ID 3742 for 'tracker-applet'
Killed process 3742
Found process ID 3827 for 'tracker-indexer'
Killed process 3827
Found process ID 8746 for 'trackerd'
Killed process 8746
Setting database locations
Checking database directories exist
Checking database version
Checking database files exist
Removing all database files
Removing database:'/home/pradeeban/.local/share/tracker/data/common.db'
Removing database:'/tmp/tracker-pradeeban/cache.db'
Removing database:'/home/pradeeban/.cache/tracker/file-meta.db'
Removing database:'/home/pradeeban/.cache/tracker/file-fulltext.db'
Removing database:'/home/pradeeban/.cache/tracker/file-contents.db'
Removing database:'/home/pradeeban/.cache/tracker/email-meta.db'
Removing database:'/home/pradeeban/.cache/tracker/email-fulltext.db'
Removing database:'/home/pradeeban/.cache/tracker/email-contents.db'
Setting index database locations
Checking index directories exist
Checking index files exist
Removing all database index files
Removing database index:'/home/pradeeban/.cache/tracker/file-index.db'
Removing database index:'/home/pradeeban/.cache/tracker/email-index.db'