[stormyfacts] No meaningful error message when shared memory isn't writable

Bug #1230486 reported by m4v on 2013-09-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu IRC Bots

Bug Description

When shared memory isn't writeable, editing factoids with regexs just fails silently.

Error log
INFO 2013-09-25T17:09:57 supybot Stormyfacts: regexpEdit(8.04) called by 'm4v!~znc@ubuntu/member/m4v' at #ubuntu-es-ops
ERROR 2013-09-25T17:09:57 supybot Uncaught exception in inFilter:
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/supybot/irclib.py", line 815, in feedMsg
    m = callback.inFilter(self, msg)
  File "/home/m4v/kubot/plugins/Stormyfacts/plugin.py", line 1062, in inFilter
    rt = getattr(self, cmd)(irc, msg, channelStore)
  File "/home/m4v/kubot/plugins/Stormyfacts/plugin.py", line 1995, in regexpEdit
    self._regexpEdit(irc, *args, **kwargs)
  File "/home/m4v/kubot/plugins/Stormyfacts/plugin.py", line 2030, in _regexpEdit
    m = multiprocessing.Value('i', 0)
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
    return Value(typecode_or_type, *args, **kwds)
  File "/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 103, in Value
    lock = RLock()
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
    return RLock()
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
    SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied

m4v (m4v) on 2013-09-25
tags: added: junior-task
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers