Hosted Projects - FS2 Required > Phoenix

Database inconsistency detected

(1/3) > >>

Announcements:
Message #1181422 not found.  Running diagnostics...

System scan... SUCCEEDED.  System status nominal.
Data integrity check... SUCCEEDED.  No unanticipated errors detected.
Archival scan... FAILED.  Message no longer exists in database.

Running dynamic timeline analysis...

>>> Temporal waveforms have de-synchronized.  Message lock lost.  Attempting to reacquire...

Phase variance exceeds ability to compensate.  Program halted.  Software restart scheduled for next phase alignment.

Estimated synchronization offset:

Grizzly:
It begins!

JSRNerdo:
Message 1181422 is probably an actual message on HLP. Anyone gonna take a crack at trying to find it?

e: That countdown seems to go by the second. It'll be ~10 days or so.

Mongoose:

--- Quote from: JSRNerdo on September 03, 2017, 04:00:44 am ---Message 1181422 is probably an actual message on HLP. Anyone gonna take a crack at trying to find it?

--- End quote ---
Is there any way to single out a message ID without knowing the thread ID it's associated with, or would you just have to brute-force it by digging backwards?

The E:
Okay, so I think I narrowed it down a bit.

This is message 1181421. So we're looking at something during that time period, maybe?

Navigation

[0] Message Index

[#] Next page