This post is more than 5 years old

2 Intern

 • 

1.3K Posts

1169

June 17th, 2008 12:00

Errno: 45 - Lockf deadlock detection

My SE commands or sym* commands are just hanging. Here is what is see the symapi logfile.

Any one familiar with this errors?

[26800 GKMgt] Jun-16 15:51:40 pdsFileLock #3067 : Unable to lock file (LockFileEx/fcntl) [Errno:
45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 : [ldb_commit] Failed to commit changes to the 'gk_devs' table, DB: 'storapid_db
': [PDS/File] Error locking file [Errno: 45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 pdsFileLock #3067 : Unable to lock file (LockFileEx/fcntl) [Errno:
45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 : [ldb_commit] Failed to commit changes to the 'remote_syms' table, DB: 'storapi
d_db': [PDS/File] Error locking file [Errno: 45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 pdsFileLock #3067 : Unable to lock file (LockFileEx/fcntl) [Errno:
45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 : [ldb_commit] Failed to commit changes to the 'array_db' table, DB: 'storapid_d
b': [PDS/File] Error locking file [Errno: 45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 pdsFileLock #3067 : Unable to lock file (LockFileEx/fcntl) [Errno:
45 - Lockf deadlock detection]
[26800 GKMgt] Jun-16 15:51:40 : [ldb_commit] Failed to commit changes to the 'config' table, DB: 'storapid_db'
: [PDS/File] Error locking file [Errno: 45 - Lockf deadlock detection]

56 Posts

June 18th, 2008 03:00

Try using a temporary SYMAPI database, and see if the problem persists:

# export SYMCLI_DB_FILE=/tmp/symapi-tmp.db (make sure /tmp is large enough)
# symcfg discover
# ... try some symcli commands here

If this works fine, the problem is likely with your normal SYMAPI database file. Is the file on a local filesystem, or on NFS or another networked filesystem?

If this also fails, perhaps storapid has a problem. Try restarting storapid.

You could try lsof or fuser to see which process has the file open, or see which files the storapid process has open.

(All this assumes you're running some sort of Unix.)

6 Operator

 • 

2.8K Posts

June 17th, 2008 13:00

Please refer to the following page for a brief description of locks and deadlocks with locks ..

http://www.cs.rpi.edu/academics/courses/fall04/os/c10/index.html

The messages you quoted comes directly from your kernel .. There is something wrong with the different daemons trying to lock some files.

Unfortunatly I didn't find anything regarding the messages in our Primus.

2 Intern

 • 

1.3K Posts

June 19th, 2008 10:00

/usr/symcli/storbin/stordaemon shutdown storapid
/usr/symcli/storbin/stordaemon start storapid

that worked.

0 events found

No Events found!

Top