# עזרה בשחזור - המערכת נתקעה בחצות
**URL:** https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486
**Category:** Self-hosting
**Created:** [9 ביוני, 2022, 9:14am UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486 "2022-06-09T09:14:20Z")
**Posts on this page:** 7
**Page:** 2
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 ביוני, 2022, 12:42am UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/24 "2022-06-10T00:42:10Z")
[Rebake all posts matching a pattern](https://meta.discourse.org/t/rebake-all-posts-matching-a-pattern/48713)
---
### Author:  [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [10 ביוני, 2022, 1:44pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/25 "2022-06-10T13:44:49Z")
Sadly that did not work, the URL didn’t change after Rebuilding the HTML and it still leading a
> Oops! That page doesn’t exist or is private.
Any other ideas or thoughts?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 ביוני, 2022, 1:45pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/26 "2022-06-10T13:45:50Z")
Did rebuilding from the UX work or not?
---
### Author:  [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [10 ביוני, 2022, 1:54pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/27 "2022-06-10T13:54:25Z")
Clicking on the “Rebuild HTML” button didn’t work. The link didn’t change and it still leads to the error page.
There’s a second issue I noticed after the restore. I had a look at the error logs and I noticed this. The link isn’t the same as the one in the post I rebuilt:
`Failed to process hijacked response correctly : Errno::ENOENT : No such file or directory @ rb_sysopen - /XXXXX.s3.dualstack.us-east-1.amazonaws.com/optimized/1X/46728e07f9819907d1b18387bf02ea7fc25c7981_2_32x32.ico`
The odd thing is that when I put the above URL into the browser it does actually serve up the icon.
Here’s the backtrace
> Message (5 copies reported)
>
> Failed to process hijacked response correctly : Errno::ENOENT : No such file or directory @ rb\_sysopen - /XXXXX.s3.dualstack.us-east-1.amazonaws.com/optimized/1X/46728e07f9819907d1b18387bf02ea7fc25c7981\_2\_32x32.ico
>
> Backtrace
>
> /var/www/discourse/app/controllers/static\_controller.rb:160:in `read' /var/www/discourse/app/controllers/static_controller.rb:160:in `block (2 levels) in favicon’
> /var/www/discourse/lib/distributed\_memoizer.rb:16:in `block in memoize' /var/www/discourse/lib/distributed_mutex.rb:33:in `block in synchronize’
> /var/www/discourse/lib/distributed\_mutex.rb:29:in `synchronize' /var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize’
> /var/www/discourse/lib/distributed\_mutex.rb:14:in `synchronize' /var/www/discourse/lib/distributed_memoizer.rb:12:in `memoize’
> /var/www/discourse/app/controllers/static\_controller.rb:138:in `block in favicon' /var/www/discourse/lib/hijack.rb:56:in `instance\_eval’
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 ביוני, 2022, 2:00pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/28 "2022-06-10T14:00:47Z")
> [@RBoy](#):
>
> Clicking on the “Rebuild HTML” button didn’t work.
Then you didn’t need to figure out how to rebuild from the command line.
> [@RBoy](#):
>
> Failed to process hijacked response correctly : Errno::ENOENT : No such file or directory @ rb\_sysopen - /XXXXX.s3.dualstack.us-east-1.amazonaws.com/optimized/1X/46728e07f9819907d1b18387bf02ea7fc25c7981\_2\_32x32.ico
I’m not sure, but it sounds like it’s treating that as a filename rather than a bucket, but I’d need to look at the source to know for sure.
---
### Author:  [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [10 ביוני, 2022, 3:04pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/29 "2022-06-10T15:04:24Z")
Any other ideas/thoughts on how to fix the `/short-url` broken links?
---
### Author:  [@spamless](https://meta.discourse.org/u/spamless)
#### Post date: [13 ביוני, 2022, 8:45pm UTC](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486/30 "2022-06-13T20:45:46Z")
> [@RBoy](#):
>
> Well, atleast I figured out why my server crashed last night (and again today after a complete rebuild ☹ , see this topic for details: [Ubuntu 20.04 kernel update with docker causing a crash](https://meta.discourse.org/t/ubuntu-20-04-kernel-update-with-docker-causing-a-crash/229526)
That happened to me as well, on an Oracle Cloud server. The kernel panicked, and so did I. I thought I was toast. But after about six or eight reboots from the cloud console, some of which were “pull-the-plug” reboots, and after about half-an-hour of waiting, the server came up long enough for me to edit grub.cfg and revert to the previous kernel.
I was able to save my instance thereby. A day later, there was another new kernel update offered, and that’s when I grew more certain my theory about kernel trouble was true. And I found the bug description to confirm it. Yeah, pretty nasty.
I devised a Stupid Grub Trick, as I call it, that I will try to find time to post anon, so one would be able to avoid such a calamity in the future.
Good luck with your restore, @RBoy. I must say this thread is giving me a queasy stomach after my own near disaster last – when was it, Wednesday?
By the way, you said you regained access to your old server. If you still have it or can get access once more – for me it took some hard reboots and some waiting – well, go in and upgrade one more time, as there is another new kernel that doesn’t have the bug. Or revert to the previous kernel.
[Previous page](https://meta.discourse.org/t/help-restoring-system-hung-at-midnight/229486.md?page=1)