Jump to content
  • 0

Server keeps rolling back... Please help!

Nola

Asked by Nola,

 Share

Question

Nola Newbie

Nola

Posted
Posted

     So, I have my own dedicated server that is just LAN for the moment (hopefully I explained that right). Whenever I log back on it has rolled back anywhere from 30min-1hour. I log out like this...Disconnect myself through admin menu in game, close out tadst, then I close out start-redis.cmd. I don't see the point in leaving the server running since its private, but then again, I don't know how it all works.

 

     I am also under the impression that every time I shut everything down I'm restarting the server.. I have added two new vehicles (Ifrit and ghost hawk) and they never show up after I log back on. The ghost hawk showed up once and I logged out and haven't seen it since! 

 

     So, I guess my questions here are, is there a way to save the db as it is right before logging so I don't have to worry about rollbacks? And is my server being restarted correctly? 

 

     Thanks for taking the time to help me out, this is super frustrating for me, and the only problems that are keeping me from moving forward.

 

                                      And yes, I have used the search function for hours and have found nothing that helped me so please save it. 

 

 

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 1
RC_Robio Newbie

RC_Robio

Posted
Posted

You can adjust you save times in Redis.conf if you want faster saves to the database.

For instance what in redis.conf looks like:
save 900 1
save 300 10
save 60 1000
that means, save after 900 seconds if there is at least 1 change to the dataset, and after 300 seconds if there are at least 10 changes to the datasets, and 60 seconds if there are 1000 changes.
Link to comment
Share on other sites
  • 0
nedfox Newbie

nedfox

Posted
Posted

Redis only safes every 15 mins or so.. Make sure you see a dump.rdb appearing in your DB folder, and redis console is running without any errors.

 

When you start Redis it will read dump.rdb; if it isn't there it will start a fresh DB.

 

Shutting down Redis is something you do once per month when you're hosting; Windows patch day :)

Link to comment
Share on other sites
  • 0
Nola Newbie

Nola

Posted
  • Author
Posted
  On 2/28/2015 at 7:02 AM, Robio said:

 

You can adjust you save times in Redis.conf if you want faster saves to the database.

For instance what in redis.conf looks like:
save 900 1
save 300 10
save 60 1000
that means, save after 900 seconds if there is at least 1 change to the dataset, and after 300 seconds if there are at least 10 changes to the datasets, and 60 seconds if there are 1000 changes.

 

 

     Oh, now I see how redis is working.. Makes sense now. Thanks!

Link to comment
Share on other sites
  • 0
SLooP Newbie

SLooP

Posted
Posted

Hey folks, I am just having this issue today...server is rolling back to a set point after restarts, to some time yesterday.  I have made no edits to anything recently, and have been running build 440 since it's release without issue.  By the way, I believe this is my first post, so I'd like to thank the community for all the great content on here.

Back to the server rollbacks, I have no idea how to handle this as I just leave the redis content alone.  Haven't changed the redis.conf and I'm wondering if I should try deleting the dump.rdb?  Not certain what to do here, any ideas would be greatly appreciated.

Link to comment
Share on other sites
  • 0
He-Man Newbie

He-Man

Posted
Posted

First of all you should check your rpt for errors!

Deleting the dump is deleting your DB (if you also restart redis). So do not do it...

What is the size of your dump file?

Have you changed something in your scripts yesterday?

Link to comment
Share on other sites
  • 0
SLooP Newbie

SLooP

Posted
Posted

He-Man, thx for the response.  Dump file is 855kb.  I do have some new errors in the rpt but uncertain how to address these 

  Reveal hidden contents

these errors continue in this fashion for what appears to be every part of the body.  there are a few other errors

  Reveal hidden contents

All of these are new and did not show up in previous rpt's, from what I can tell.  Weird, rpt just littered with this stuff, and no, I made no changes yesterday (to scripts or any other file associated with the server, db, BE, etc, none since before I left town last Sunday in fact.  Redis is always running, I've never touched that piece, deliberately, aside from the initial required config edits.  Every single restart rolls back to the same point in time and location, and all the respective gear and whatnot associated with that point in time.  Freaking bizarre.

Link to comment
Share on other sites
  • 0
He-Man Newbie

He-Man

Posted
Posted

Error Undefined variable in expression: epoch_server_setvtoken

epoch_server_setvtoken is a core epoch code. If this is not available, ther is something wrong.

It is defined in a3_epoch_server\init\server_securityfunctions.sqf

 

Only an idea:

You have installed "Sector-Addon". Now it could be, that this addon is loading before the core Epoch Codes.

- Open a3_epoch_sector\init\fn_init.sqf and change the code to: 

[] spawn {
uisleep 120;
call compile preprocessFileLineNumbers "x\addons\a3_epoch_sector\scripts\SUP_sector_init.sqf"
};

Now the sector addon will wait 120 seconds and let epoch parallel load.

 

Hope this will help! But as I said, only an idea!

Link to comment
Share on other sites
  • 0
SLooP Newbie

SLooP

Posted
Posted

Ok, that's a great tip...thank you!

Last night as I dug in a little deeper, I recalled I'd recently added steamcmd with appropriate startup parameters to FireDaemon.  I'd originally set this up to run as a Windows service via another route however, separate from FireDaemon.  I think the issue was that steamcmd was running twice and somehow competing for DB access and, oddly, it seemed as if with each consecutive restart, the rollback went progressively farther back in time.  I stopped that service in FireDaemon on this suspicion and the rollbacks are no longer occurring.  Rookie mistake. :ohmy:

I think I will implement your suggestion however, since that seems to make sense to me as a good practice for such an addon.  Thanks again for the assist He-Man!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to question listing

  • Discord

×
×
  • Create New...