# 'Updating Last Seen' and 'hijack topics timings' and 'Track Visit' is still running after 90 seconds

**URL:** https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757
**Category:** Support
**Created:** [27.Март.2019 22:09:35 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757 "2019-03-27T22:09:35Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [27.Март.2019 22:09:36 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/1 "2019-03-27T22:09:36Z")

</div>

I’ve got the problem.

Several time a day my forum goes in situation where all updates process are delayed.

```
'Updating Last Seen' is still running after 90 seconds on db default, this process may need to be restarted!
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:110:in `report_to_store'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:101:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:52:in `add'
/usr/local/lib/ruby/2.5.0/logger.rb:545:in `error'
/var/www/discourse/lib/scheduler/defer.rb:92:in `block (2 levels) in do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:110:in `do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:38:in `block in initialize'

'hijack topics timings' is still running after 90 seconds on db default, this process may need to be restarted!
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:110:in `report_to_store'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:101:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.1.2/lib/logster/logger.rb:52:in `add'
/usr/local/lib/ruby/2.5.0/logger.rb:545:in `error'
/var/www/discourse/lib/scheduler/defer.rb:92:in `block (2 levels) in do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:110:in `do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:38:in `block in initialize'

'Track Visit' is still running after 90 seconds on db default, this process may need to be restarted!
/var/www/discourse/plugins/discourse-topic-previews/lib/topic_list_previews_helper.rb:13:in `create_topic_thumbnails'
/var/www/discourse/plugins/discourse-topic-previews/lib/cooked_post_processor_edits.rb:76:in `update_post_image'
/var/www/discourse/lib/cooked_post_processor.rb:42:in `block in post_process'
/var/www/discourse/lib/distributed_mutex.rb:40:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:10:in `synchronize'
/var/www/discourse/lib/cooked_post_processor.rb:35:in `post_process'
/var/www/discourse/app/jobs/regular/process_post.rb:24:in `execute'
/var/www/discourse/app/jobs/base.rb:230:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/rails_multisite-2.0.6/lib/rails_multisite/connection_management.rb:63:in `with_connection'
/var/www/discourse/app/jobs/base.rb:219:in `block in perform'
/var/www/discourse/app/jobs/base.rb:215:in `each'
/var/www/discourse/app/jobs/base.rb:215:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/sidekiq-5.2.5/lib/sidekiq/processor.rb:185:in `execute_job'

```

I see stange disk activity as well

or some peek on week

I have backup settings as “every 3 days”.  
I do have two plugins  
[discourse-whos-online](https://github.com/davidtaylorhq/discourse-whos-online)  
[discourse-topic-list-previews](https://github.com/angusmcleod/discourse-topic-previews)

What’s to check? Or logs to see?

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [27.Март.2019 22:21:24 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/2 "2019-03-27T22:21:24Z")

</div>

More errors:

```
Job exception: ERROR: deadlock detected
DETAIL: Process 22512 waits for ExclusiveLock on tuple (22418,9) of relation 16742 of database 16400; blocked by process 28074.
Process 28074 waits for ShareLock on transaction 1013165180; blocked by process 24391.
Process 24391 waits for ShareLock on transaction 1013163724; blocked by process 1150.
Process 1150 waits for ShareLock on transaction 1013156883; blocked by process 22512.
HINT: See server log for query details.

/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/rack-mini-profiler-1.0.2/lib/patches/db/pg.rb:110:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/rack-mini-profiler-1.0.2/lib/patches/db/pg.rb:110:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/mini_sql-0.2.1/lib/mini_sql/postgres/connection.rb:118:in `run'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/mini_sql-0.2.1/lib/mini_sql/postgres/connection.rb:90:in `exec'
(eval):6:in `exec'
/var/www/discourse/app/models/post.rb:646:in `block in calculate_avg_time'
/var/www/discourse/lib/freedom_patches/active_record_base.rb:45:in `retry_lock_error'
/var/www/discourse/app/models/post.rb:623:in `calculate_avg_time'
/var/www/discourse/app/jobs/scheduled/calculate_avg_time.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:230:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/rails_multisite-2.0.6/lib/rails_multisite/connection_management.rb:63:in `with_connection'
/var/www/discourse/app/jobs/base.rb:219:in `block in perform'
/var/www/discourse/app/jobs/base.rb:215:in `each'
/var/www/discourse/app/jobs/base.rb:215:in `perform'
/var/www/discourse/app/jobs/base.rb:277:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/mini_scheduler-0.9.1/lib/mini_scheduler/manager.rb:82:in `process_queue'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/mini_scheduler-0.9.1/lib/mini_scheduler/manager.rb:30:in `block in initialize'

```

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [28.Март.2019 00:18:20 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/3 "2019-03-28T00:18:20Z")

</div>

> [@Dmitry\_Krasnoperov](#):
>
> I do have two plugins  
> [discourse-whos-online](https://github.com/davidtaylorhq/discourse-whos-online)  
> [discourse-topic-list-previews](https://github.com/angusmcleod/discourse-topic-previews)

Disable these and rebuild and see if that helps things.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [28.Март.2019 12:00:43 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/4 "2019-03-28T12:00:43Z")

</div>

Do you have enough ram? I’d the cpu far enough?

How big is your database and how much ram do you have? Is swap enabled? Is it getting full?

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [29.Март.2019 23:27:26 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/5 "2019-03-29T23:27:26Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/3X/1/4/14bfb567c112a11507023040541f5e617de53bb3.png)

4CPU/8GB and 2GB swap enabled.  
But DB is large enough with a lot of images

```
   84.0GiB [##########] /uploads
   26.7GiB [###] /postgres_data
    4.7GiB [] /backups
    3.7GiB [] /log
  201.5MiB [] /redis_data
    1.7MiB [] /letsencrypt
  176.0KiB [] /postgres_run
   28.0KiB [] /state
   16.0KiB [] /tmp
   12.0KiB [] /ssl
e 4.0KiB [] /postgres_backup

```

I’ve just got this frozen status update and htop shows  
 ![image](https://global.discourse-cdn.com/meta/optimized/3X/7/5/75748cab41b2b2030a28307c0b8d779b382d4952_2_690x15.png)

and i got Error  
`'hijack topics timings' is still running after 90 seconds on db default, this process may need to be restarted!`

backtrace

```
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.3.0/lib/logster/logger.rb:110:in `report_to_store'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.3.0/lib/logster/logger.rb:101:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/logster-2.3.0/lib/logster/logger.rb:52:in `add'
/usr/local/lib/ruby/2.5.0/logger.rb:545:in `error'
/var/www/discourse/lib/scheduler/defer.rb:92:in `block (2 levels) in do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:110:in `do_work'
/var/www/discourse/vendor/bundle/ruby/2.5.0/gems/message_bus-2.2.0/lib/message_bus/timer_thread.rb:38:in `block in initialize'

```

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [30.Март.2019 00:06:36 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/6 "2019-03-30T00:06:36Z")

</div>

> [@codinghorror](#):
>
> Disable these and rebuild and see if that helps things.

Yep, will disable one by one and see.  
Thanks

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [30.Март.2019 06:59:15 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/7 "2019-03-30T06:59:15Z")

</div>

That’s a big database. What’s the value of db\_shared\_buffers in app.yml?

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [30.Март.2019 07:14:44 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/8 "2019-03-30T07:14:44Z")

</div>

```
  ## Set db_shared_buffers to a max of 25% of the total memory.
  ##
  ## On 1GB installs set to 128MB (to leave room for other processes)
  ## on a 4GB instance you may raise to 1GB
  db_shared_buffers: "2048MB"

```

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [30.Март.2019 12:02:13 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/9 "2019-03-30T12:02:13Z")

</div>

You might try bumping it and the other memory variable up a bit. You have fast ssd?

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [19.Май.2019 13:55:50 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/10 "2019-05-19T13:55:50Z")

</div>

Hi,

I’m in DigitalOcean SSD disk.  
Set db\_shared\_buffers: “3048MB”  
Disable plugins one by one.

but I’m still getting this disk activity peaks

 ![image](https://global.discourse-cdn.com/meta/original/3X/2/f/2f1f56ee2c17fb9da8e838d4f76f96d478ace880.png)

---

<div class="post-metadata">

### Author: ![wandagoner](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wandagoner/32/180530_2.png) [@wandagoner](https://meta.discourse.org/u/wandagoner)
#### Post date: [23.Май.2020 02:54:02 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/11 "2020-05-23T02:54:02Z")

</div>

Привет, Дмитрий,

У меня тоже возникает такая же комбинация ошибок. Удалось ли тебе уже решить эту проблему?

---

<div class="post-metadata">

### Author: ![Crius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crius/32/317214_2.png) [@Crius](https://meta.discourse.org/u/Crius)
#### Post date: [09.Октябрь.2024 08:45:58 UTC](https://meta.discourse.org/t/updating-last-seen-and-hijack-topics-timings-and-track-visit-is-still-running-after-90-seconds/112757/12 "2024-10-09T08:45:58Z")

</div>

1. Та же проблема. Общее то, что это большая база данных.

Есть ли у размещённого Discourse клиенты с большими базами данных?

```plaintext
sudo du -h --max-depth=1 /var/discourse/shared/standalone/
28K /var/discourse/shared/standalone/state
244K /var/discourse/shared/standalone/postgres_run
8.0K /var/discourse/shared/standalone/backups
1.2G /var/discourse/shared/standalone/uploads
531M /var/discourse/shared/standalone/log
4.0K /var/discourse/shared/standalone/postgres_backup
12K /var/discourse/shared/standalone/tmp
73M /var/discourse/shared/standalone/redis_data
---> 89G /var/discourse/shared/standalone/postgres_data <---
12K /var/discourse/shared/standalone/ssl
91G /var/discourse/shared/standalone/

```