-Feedback-

Hm, this might be tricky to find. Not sure if this sector export will conclude something. There's probably no logs from that period?
Was this immediately after the server updated to 0.19488? Was it the first time the sector got loaded after 0.19488?

It was neither, actually. I'd been working on the ship in the morning. Went and parked it in that sector to do a mid-day speed build thing on stream with Raiben in a different sector and then after he left the build/stream server and I returned from my lunch break I went back to that sector to retrieve and keep working on the ship (actually admin warped out to a pirate station for weapons testing and thats when I discovered the link issue). Warped the ship back and began re-linking logic which is about when Dalmont showed up on our TS server, heard what was happening and told me to stop and save things (this was also when I discovered that as Dalmont had predicted, the entire sector was unlinked). I can take a quick gander through the server logs though if you want, but who knows how deep anything relating to this would be buried if I have the logs.

I have a lot of server log files from the 10th, much is console 'Stop Effect' spam which would have been from weapons system testing prior to occurrence of the bug. Trying to widdle the logs down to a range closer to the issue, will upload to conpherence as soon as I get them off the server. It is my wife's day off, so my computer coverage is spotty, but I'm trying to get these files uploaded as soon as possible before they are more difficult to track down; sorry that I do not have the time at the moment to refine it to just 1 or 2 of the total logs.

Rough time range of log files for this occurrence posted to conpherence. Let me know if you need more from me or need me to try and refine the log range a bit better, I'll jump on it when I have the time a bit later today or something. Good luck with the bug hunting!

THis has been reported.
T755: Computers and logic all disconnect on their own.

It's rough to test, because we cant reproduce it.

@AndyP Should this task be merged into T280? Or perhaps T280 would be a task that blocks this one?

In T847#31136, @Chandler wrote:

THis has been reported.
T755: Computers and logic all disconnect on their own.
It's rough to test, because we cant reproduce it.

Well, T755 is closed as duplicate of T280 already, so picked the wrong reference :P

In T847#33624, @lancake wrote:

@AndyP Should this task be merged into T280? Or perhaps T280 would be a task that blocks this one?

Not sure, did this affect ALL entities in one sector, or mostly one big entity in a sector?
(If its a a´single connected entitiy, it could be a corruption of metadata, if its more than one, it should be something with the load/unload process and possible overlap.)

We had something like this in race conditions when a reload occured right in the moment the sector got unloaded, so the blockdata was present, and the metadata was not yet written and somehow this intermediate state got loaded and saved again. However, this only happened like a year ago, but got fixed.

I assume the sector was used by multiple people at the same time?
Can you remember the moment you noticed all was unlinked, were you alone or were others nearby? (possibly just left?)

It could help to narrow down the source in the "load" or "save" process.
If there are logs covering the timespan it happened, and you have a name of a station/entity in that sector I could look into this, and possibly find a related error.

• Andy

Last time it occurred it effected across sectors, mine at 2.2.3 and Klowns public gate 1-2 sectors away.

@AndyP

:) I still dont think that they are related :P.. The wireless one is pretty consistent.. (or at least it was when i was working with the wireless) The everything disconnecting all at once when it decides to is a crap shoot. We dont know when it will happen.. ;)

I just experienced this bug, I came back to my shipyard and discovered that all systems in the sector had unlinked. I was last in that sector a day or two before I returned so I don't know when it exactly happened.

I've included my client logs from today and 2 days before that, I also got the server owner to send me server logs and a sector export.

The sector had a bunch of things in it when it happened, I hope this bug gets fixed as soon as possible.

@PhaserArray
hm, the logs dont give any useful information.
(The server side ones are the wrong ones, but 3 days would be several hundred MB of logs to look through.)

@Chandler
If it was two gates, it may have other causes, we need to get some proper way to reproduce, as most of those issues with gates unlinking were from backup/restore scripts or players reloading one end of the gate after it got damaged.

Thanks to nalem, we got a new trail to this.

Does anyone having this issue on the server use the /delay_save command for backups?

Can't seem to reproduce by using /delay_save.

I've tried delaying the auto save for a long time, then unloading/loading sectors but existing links were still working fine.
I did the same for new structures and links, but even those were fine after loading the sector again.

Doesn't seem like it depends on location either, I've build links in all 8 octants and outside of the chunk containing the shipcore, still everything was fine.

I've experimented with shutting down the server when delaying save but no results either :(

Geez, too bad, hoped delay_save + creating links in that time, may cause those corrupted data that gets discarded on reload.
So, back to the investigation table.