[root@rdesc db]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/sda1     ext4     5039616   3946896    836720  83% /
tmpfs        tmpfs     8165184         0   8165184   0% /dev/shm
/dev/sda7     ext4     4619200    140364   4244188   4% /home
/dev/sda5     ext4     2015824     36296   1877128   2% /tmp
/dev/sda6     ext4     2015824    272884   1640540  15% /var
/dev/sda2     ext4     5039616    145312   4638304   4% /var/log
/dev/sda3     ext4     5039616    146416   4637200   4% /var/log/audit
<IP Add>:/ifs/projects/rdesc
               nfs   1073741824  87446528 986295296   9% /projects/rdesc
<IP Add>:/pic/projects/rdesc
               nfs   2984680110080 2446048684032 466115743744  84% 
/pic/projects/rdesc

my vituoso-t is at "/usr/local/.........." so its FS is ext4
but my .db file is on mounted area "/projects/rdesc......" which is NFS


I send dump of "ps -ef" in previous reply , please see that to confirm if there 
is any nsflock daemon. i see "nfsoid" and "locked" process.

thanks for your help
sumit 

________________________________________
From: Patrick van Kleef [[email protected]]
Sent: Monday, March 25, 2013 5:38 AM
To: Purohit, Sumit
Cc: Hugh Williams; Kingsley Idehen; [email protected]
Subject: Re: [Virtuoso-users] Unable to connect to virtuoso : Connect failed to 
localhost:1111

Hi Sumit,

> [root@rdesc db]# /usr/local/virtuoso-opensource/bin/virtuoso-t -f -c 
> /usr/local/virtuoso-opensource/bin/virtuoso.ini
>
>                Sun Mar 24 2013
> 20:15:51 { Loading plugin 1: Type `plain', file `wikiv' in 
> `/usr/local/virtuoso-opensource/lib/virtuoso/hosting'
> 20:15:51   WikiV version 0.6 from OpenLink Software
> 20:15:51   Support functions for WikiV collaboration tool
> 20:15:51   SUCCESS plugin 1: loaded from 
> /usr/local/virtuoso-opensource/lib/virtuoso/hosting/wikiv.so }
> 20:15:51 { Loading plugin 2: Type `plain', file `mediawiki' in 
> `/usr/local/virtuoso-opensource/lib/virtuoso/hosting'
> 20:15:51   MediaWiki version 0.1 from OpenLink Software
> 20:15:51   Support functions for MediaWiki collaboration tool
> 20:15:51   SUCCESS plugin 2: loaded from 
> /usr/local/virtuoso-opensource/lib/virtuoso/hosting/mediawiki.so }
> 20:15:51 { Loading plugin 3: Type `plain', file `creolewiki' in 
> `/usr/local/virtuoso-opensource/lib/virtuoso/hosting'
> 20:15:51   CreoleWiki version 0.1 from OpenLink Software
> 20:15:51   Support functions for CreoleWiki collaboration tool
> 20:15:51   SUCCESS plugin 3: loaded from 
> /usr/local/virtuoso-opensource/lib/virtuoso/hosting/creolewiki.so }
> 20:15:51 OpenLink Virtuoso Universal Server
> 20:15:51 Version 06.01.3127-pthreads for Linux as of Mar  5 2013
> 20:15:51 uses parts of OpenSSL, PCRE, Html Tidy
> 20:15:51 Virtuoso is already running (pid 0)
> 20:15:51 Server exiting
>

When virtuoso starts it attempts to get an exclusive lock on the .db file to 
make absolutely sure it is the only process using this file.

If it fails to get this lock, this normally means the pid of the process that 
holds the lock is printed.

In your case however it appears to be unable to ask for a lock since your 
filesystem type does not support it.


I will fix the code to make sure we report this condition in a more 
understandable way.


Since your earlier emails indicated it was working on the same location before 
your reboot, it could be that the system failed to restart an appropriate lock 
manager for your fs, for instance when you use NFS, the nfslock daemon should 
be running.


Can you tell me what filesystem type you are using for the filesystem that 
contains:

  /projects/rdesc/virtuoso-opensource/var/lib/virtuoso/db/virtuoso.db




Patrick


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Virtuoso-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to