Lock expired - what could have happend?

Zaid Abdulla zaid at genieacs.com
Fri Jun 16 19:05:03 EDT 2017


On Wed, 2017-06-14 at 14:25 +0000, Simon Ryf wrote:
> Do you have any Idea why this could have happened?
> Restarting the whole server solved the issue (at least for now).
> Where do you think I should start looking if it happens again?
>  
> Thank you
> Br
> Simon
>  
> 2017-06-14T14:10:49.797Z [ERROR] Uncaught exception;
> exceptionName="Error" exceptionMessage="Lock expired"
> exceptionStack="Error: Lock expired
>       at Command.callback (/opt/genieacs/lib/cache.js:59:24)
>       at normal_reply
> (/opt/genieacs/node_modules/redis/index.js:721:21)
>       at RedisClient.return_reply
> (/opt/genieacs/node_modules/redis/index.js:819:9)
>       at JavascriptRedisParser.returnReply
> (/opt/genieacs/node_modules/redis/index.js:192:18)
>       at JavascriptRedisParser.execute
> (/opt/genieacs/node_modules/redis-parser/lib/parser.js:562:12)
>       at Socket.<anonymous>
> (/opt/genieacs/node_modules/redis/index.js:274:27)
>       at emitOne (events.js:96:13)
>       at Socket.emit (events.js:191:7)
>       at readableAddChunk (_stream_readable.js:178:18)
>       at Socket.Readable.push (_stream_readable.js:136:10)"

This can possibly be caused by Redis or Mongo not responding in time.
Perhaps the server was overloaded? If it persisted and was only
resovled after a full server reboot then I'd look at MongoDB, Redis,
and network/firewall.

-- 
Zaid Abdulla <zaid at genieacs.com>


More information about the Users mailing list