# Conflicting "out of date" vs "up to date" statuses
**URL:** https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339
**Category:** Support
**Created:** [20 maart 2016 om 18:23 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339 "2016-03-20T18:23:13Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [20 maart 2016 om 18:23 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/1 "2016-03-20T18:23:13Z")
At the top of the Admin screen, I am told `Your Discourse installation is out of date. Click here to upgrade.` But when I click, each item is `Up to date`.
Also on the Admin screen: `A check for updates has not been performed lately. Ensure sidekiq is running.` However, in the Processes list, I see `sidekiq 4.0.1 discourse [0 of 5 busy]`.
What’s going on here? I suspected that Discourse was running out of memory on my Linode 2048 because it was using swap. (Perhaps this is why `sidekiq` wasn’t up?) So, I just finished upgrading it to a 4096 MB instance. Now no swap is being used, but I am still unable to upgrade.
Is this something to worry about or should I just leave it be? Thanks in advance!!
(I tried to include a second screenshot, but `new users can only put one image in a post`, so just trust me that my Discourse install says all upgradeable items are `Up to date`.)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [20 maart 2016 om 20:12 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/2 "2016-03-20T20:12:31Z")
Have you tried rebooting?
---
### Author:  [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [21 maart 2016 om 17:42 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/3 "2016-03-21T17:42:13Z")
Jeff, thanks for your response.
The Linode VPS rebooted when I resized it to a 4096 MB instance. I am assuming this is what you mean?
Btw I checked the admin screen again just now, thinking the situation may have corrected itself overnight due to the new extra 2 GB of RAM. However, I am still seeing the same symptoms.
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [21 maart 2016 om 20:00 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/4 "2016-03-21T20:00:51Z")
Try to visit `/sidekiq` – do you see Sidekiq’s dashboard there? If so, can you post a screenshot?
---
### Author:  [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [21 maart 2016 om 20:21 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/5 "2016-03-21T20:21:02Z")
Hi Felix, thanks a lot. Yes, I can see the dashboard. Here it is:
Note that the high number of failed jobs is from 2 months ago, when every `Jobs::UserEmail` failed with `Jobs::HandledExceptionWrapper: Wrapped SocketError: getaddrinfo: Name or service not known`. I fixed that by doing an upgrade + restart, which is good but makes me uneasy since I don’t know _how_ I fixed it! No jobs have failed since then.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [21 maart 2016 om 21:21 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/6 "2016-03-21T21:21:17Z")
What’s with the “9,999 Dead”? Pretty sure that’s not normal…
---
### Author:  [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [21 maart 2016 om 22:56 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/7 "2016-03-21T22:56:19Z")
Hi Kane, those are many failed `Jobs::UserEmail` from when it was messed up 2 months ago:
I do not think they are related to my current problem, but I may be wrong.
---
### Author:  [@markplindsay](https://meta.discourse.org/u/markplindsay)
#### Post date: [1 mei 2016 om 01:54 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/8 "2016-05-01T01:54:01Z")
`/var/discourse/launcher rebuild app` successfully updated Discourse for me. I am just gonna do it that way from now on.
FWIW, I suspect I have a weird Linode-specific Docker install on my Linode instance. This may or may not be the cause of my inability to update within the Discourse UI, [and some other problems](https://meta.discourse.org/t/jobs-handledexceptionwrapper-wrapped-socketerror-getaddrinfo-name-or-service-not-known/42652/3).
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1 mei 2016 om 03:11 UTC](https://meta.discourse.org/t/conflicting-out-of-date-vs-up-to-date-statuses/41339/9 "2016-05-01T03:11:38Z")