Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Your lock is expiring soon. -

I've just installed version 1.10 and I'm getting this issue with every ticket...

Your lock is expiring soon.
The lock you hold on this ticket will expire soon. Would you like to renew the lock?


If I try to renew the lock, it just gets stuck there...

If I don't do nothing,  and just try to close the ticket, replying to the user,  I get an error:  

This action requires a lock. Please try again 


What to do ? 

Info:

PHP 5.6
Osticket 1.10 (latest version)
Apache 2.2.15
Mysql 5.5

This was an upgrade from version 1.9

Comments

  • I can think of a number of things that you could do.. but my question is why is this an issue?

    1. increase the lock timer at Admin panel -> Settings -> System -> Collision Avoidance Duration.
    2. set the timer to 0 to disable it.
  • It's an issue, because I can't reply to tickets - always getting an error - This action requires a lock. Please try again... 

    And the spinner keeps spinning every time i say I want to renew the lock...
  • Disabling the lock (0 in the timer) solved the issue ! Thank you
  • Have you tried either of the things I mentioned?
    Do your osticket, serverOS, and db timezones all match?

  • Hi, I can confirm that it is a problem with the time zones.

    In México we just ended Savings Time and I had this same issue.

    I fixed it by giving my lock a 63 min time instead of 3 min but still dont know why there is still a problem since I checked and my server already did the time change.

    I still have to check how to change the DB time zone but i dont know how to do that and dont have time for it right now. I ll be back with more info after I have time to fix it.
  • This github PR looks like it would solve many of the timezone problems: https://github.com/osTicket/osTicket/pull/3734

    I created a github issue for a similar but different issue and there is a quick 1 line fix mentioned too: https://github.com/osTicket/osTicket/issues/3991

Sign In or Register to comment.