TopShelf TG Fiction in the BigCloset!
Just a bit ago:
"Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 28046124
Varnish cache server"
Guru Meditation brings back fond memories I had two Amiga computers back in the day, a 1000 then a 2000. Good days.
Checks can be made out & sent to:
Joyce Melton
1001 Third St.
Space 80
Calimesa, CA 92320
USA
Note: $6000 is the operating, maintenance and upgrade budget. Amounts received in excess of the $6000 will be applied to long term debt accrued over the last 19 years.
If you prefer, you can donate through Patreon:
Become a Patron!
Thank you!
Comments
So What DOES That Mean...
...besides showing that whoever originated that code had a sense of humor?
Eric
Essentially it means the
Essentially it means the operating system encountered an error from which it was unable to recover, but it was able to stop and display an error code. Similar to a Windows blue screen ("blue screen of death"). And it does display the sense of humor of the Amiga OS developers.
DEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEFDEADBEEF
Programmers who worked on the IBM RS/6000 systems, Mac OS on 32-bit PowerPC processors and the Commodore Amiga (and maybe others) will recognize the above Hexspeak used to ease debugging. IIRC it originated on the Amiga.
Amiga developer's conferences were fun.
Kris
{I leave a trail of Kudos as I browse the site. Be careful where you step!}
0xDEADBEEF
In FreeBSD, someone protested the killing of BEEF in the debugging code and changed 0xDEADBEEF to 0xDEADC0DE instead. It's still used today to fill freed memory to highlight use-after-free bugs.
e.g. https://github.com/freebsd/freebsd/blob/master/sys/kern/uipc...
That's the 32 bit pattern. I think someone developed a different pattern for 64 bit values which need a value twice as long, but I can't remember offhand what it is.
Google Browser/Site Security
For the last 24 hours I've been tweaking code on BigCloset to meet new google standards for site security. BC is by default now served over 100% secured HTTPS/SSL encrypted sessions.
The 503 error was likely caused by me tweaking things. What the Varnish gateway error means is that you were able to talk to our varnish gateway server on Buttercup, but that one of our Apache front-end servers was having a 503 error because of my tinkering.
-Piper