Help decoding a log file?

I was using my Asp Miner to shuttle various modules around, arrived at a station, put my ship in the hangar, went to the outfitting screen, requested a bunch of modules be sent to the station, went to get myself a cup of coffee while they were transferred, got back and....

ooTHU6O.png

Would somebody like to have a stab at deciphering the netlog and explain why I died?

WNyTera.jpg

The highlighted line is me taking the "you're dead" screenie so, presumably, the stuff immediately prior to it includes whatever killed me. :S
 
The ILeftSession(3), appearing four times looks suspiciously like you had a disconnect that the game was trying to restore. Somehow you ended up undocked. And it killed the ship :(
 
Looks like your netlog file...isn’t the journal file completely different, and called, well, “journal”something-something-something?

Clicker
 
The highlighted line is me taking the "you're dead" screenie so, presumably, the stuff immediately prior to it includes whatever killed me. :S

i'm quite alien to elite logs but if i had to speculate, these stand out:

- Cancelling request fbb

no idea what fbb is, but this happens in the same second you get a 200 status response (meaning 'ok') for the third of three web requests ... possibly the module transfers? i also ignore what this means and why a successful request would have to be cancelled, if it is related at all.

- NeedToSendAck

is suspicious. happens 3s after the cancel thing. might indicate some synchronization problem going on.

- machines ...

looks like a network status update. appears above also, and values seem ok. no idea what triggers this.

from other reports i have seen, damage to your ship is usually logged, and nothing appears here. then again, i don't know if your logs were on verbose mode or not, neither what modes currently exist.

so ... i'm totally clueless but i'd call it a bug. send it to support.
 
Yep, just checked mine...you’ve cut-pasted contents of your netlog file.

Go find your journal file....it will be much more helpful.

If I was to hazard a guess, I’d say you probably accidently hit launch before walking away from the PC.
It then sat there for 5 minutes before the station blew you up.

Clicker

P.s. you might want to redact your IP address when uploading info to public forums !!!!
 
Last edited:
Yep, just checked mine...you’ve cut-pasted contents of your netlog file.

Go find your journal file....it will be much more helpful.

If I was to hazard a guess, I’d say you probably accidently hit launch before walking away from the PC.
It then sat there for 5 minutes before the station blew you up.

Clicker

Cheers.

Just had a look at the Journal.
qw5lE07.jpg

Bit odd.

It seems to suggest I docked at 01:54.40 and then "undocked" again at 01:55.51.

Not sure how that might have happened because, on my end, what I did was dock, enter the outfitting screen and request a couple of modules get transferred.
For it to be the result of "finger trouble" would require that I quit out of the outfitting screen, quit out of the starport services and then toggled down to select "launch".

Not that fussed about the rebuy.
The main thing is, I'm a bit worried it might happen again if I go AFK after parking a big ship.

I was hoping that, whatever happened, it might be prevented by entering, say, the outfitting page or the contacts page before going AFK.
That would seem not to be the case though. [sad]


*EDIT*

Just realised, the Journal does keep a log of when you access things like the outfitting page and it's not showing as having happened right after I landed.

I'm guessing that, perhaps, something happened to my connection just after I landed and, as a result, the server didn't "see" what I did after I landed and that's what somehow caused the "undocking".

The weird thing, there, is that the modules I transferred DID arrive so that would seem to suggest everything was working correctly when I made the transfers.
 
Last edited:
For it to be the result of "finger trouble" would require that I quit out of the outfitting screen, quit out of the starport services and then toggled down to select "launch".

mystery solved then: you're getting old.

or, ... any fancy voice attack macros?
 
Back
Top Bottom