--force-lock option error

9 views
Skip to first unread message

Daniel Jung

unread,
Mar 28, 2014, 5:45:40 PM3/28/14
to nsscache...@googlegroups.com
Hi,

Running nsscache -c /etc/nsscache/nsscache.conf update -f --force-lock gave the following error, there is another nsscache job that that runs often with update option only.

I wonder if the pid written is not properly parsed?? Oddly, i cant seem to reproduce using -d -v hence no debug log so far..

Traceback (most recent call last): File "/usr/local/booking-python/2.7.2/bin/nsscache", line 33, in <module> return_value = nsscache_app.Run(sys.argv[1:], os.environ) File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/app.py", line 242, in Run retval = command_callable().Run(conf=conf, args=args) File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/command.py", line 235, in Run force_lock=options.force_lock) File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/command.py", line 253, in UpdateMaps if not self._Lock(path=conf.lockfile, force=force_lock): File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/command.py", line 144, in _Lock return self.lock.Lock(force=force) File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/lock.py", line 153, in Lock self.SendTerm() File "/usr/local/booking-python/2.7.2/lib/python2.7/site-packages/nss_cache/lock.py", line 177, in SendTerm pid = int(pid) ValueError: invalid literal for int() with base 10: ''

Jamie Wilkinson

unread,
Apr 29, 2014, 4:46:21 AM4/29/14
to nsscache...@googlegroups.com
Thanks for the report.  Can you show the contents of the pid file when you get this error?


--
You received this message because you are subscribed to the Google Groups "nsscache-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nsscache-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jamie Wilkinson

unread,
Apr 29, 2014, 5:42:10 AM4/29/14
to nsscache...@googlegroups.com
I've managed to reproduce this in test, it looks like a simple case of not handling bad pidfiles; rookie error!

Jamie Wilkinson

unread,
Apr 29, 2014, 8:45:20 AM4/29/14
to nsscache...@googlegroups.com, mimian...@gmail.com
This has been released as version 0.24; you can check it out of the git repository or fetch from Debian unstable, but google code has removed the optoin of uploading tarballs and I don't have a replacement for that.
Reply all
Reply to author
Forward
0 new messages