Kane Hart Posted January 28, 2017 Share Posted January 28, 2017 Not sure what to say more then she is dead :( http://pastebin.com/s6w2Sezy The fixing the issue of deleting the last sectors to load works. But why I crashed and why the all broke I got no clue but if anyone googles this there you go :P Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 28, 2017 Boxelware Team Share Posted January 28, 2017 This is a start up crash, please also post the log from the original crash, if it was a crash. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 28, 2017 Boxelware Team Share Posted January 28, 2017 Looks like one of your sector files is corrupt. It's probably file 305_-184v. Try deleting it, if that works, your server should start back up again. Link to comment Share on other sites More sharing options...
Kane Hart Posted January 28, 2017 Author Share Posted January 28, 2017 Looks like one of your sector files is corrupt. It's probably file 305_-184v. Try deleting it, if that works, your server should start back up again. Got dozens of them going through them now thanks :) Don't have the original logs since you store only 10 and prune them and it was auto rebooting on a crash. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 28, 2017 Boxelware Team Share Posted January 28, 2017 Gotcha. Fixed. I'd still like to know what caused the crash in the first place. Link to comment Share on other sites More sharing options...
Kane Hart Posted January 28, 2017 Author Share Posted January 28, 2017 Here is the files I had to prune: http://stonelegion.com/kane/frack.zip Suggestions: 1) If a bad system happens can you rename and regen it? 2) Create a logs folder 3) Allow option to set option to keep how many logs. Link to comment Share on other sites More sharing options...
Kane Hart Posted January 28, 2017 Author Share Posted January 28, 2017 Might of found the issue: I ran out of space or I think I did. I had full logging enabled since was not working before. Since the update it was on. I just noticed after 20min checking logs it was up to 2gigs. It would actually make sense and why those files got corrupted due to lack of HD space. I turned off the trace now hehe. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 28, 2017 Boxelware Team Share Posted January 28, 2017 Tracing should NOT be enabled during normal runs, it spams the HDD with incredible speed. I added a new cmd line option for amount of logs that are kept. Renaming things after a crash is basically impossible. While I can detect the crash, everything that happens after the crash is theoretically undefined behaviour. You don NOT want undefined behaviour when renaming files. Link to comment Share on other sites More sharing options...
Kane Hart Posted January 28, 2017 Author Share Posted January 28, 2017 Just had another crash this time I got the log: http://pastebin.com/HDsZ5h53 Not detailed logging since :P file size haha Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now