Life is Feudal Official Forum

[TiTANSTORM]

I have noticed some slight server lag now and then with rows of "outdated RecordSet" warning in the console window. For example:

Code: Select all

WARN 2015-11-27 02:40:47.813 {00} <NOSCOPE> # Warning: found an outdated RecordSet (1562) inside DBI (1188 dbi). Time elapsed: 2400 sec / Warn counter: 4

Any idea what is causing this?

[Custodian]

Any idea what is causing this?

You are using one of mods which executes sql queries to the database.
Most likely, thats LiFDS-CP (Control panel), since its does not work correctly with record sets. I made a pull request fix those issues.

[TiTANSTORM]

Thanks for the reply. The lifds-cp should only be reading information and the tree removal scripts do not work from what I have read. I also used the LiFAdmin tool to view stats, inventory, etc. and have written things to the database. I have tried not running any mods/admin tools and these warnings still come up. Is there any way to fix this or is a wipe the best solution? The error message I pasted above will scroll across the screen for hundreds of rows which typically causes server lag when that happens.

[Custodian]

I have tried not running any mods/admin tools and these warnings still come up.

If it was related to lifds-cp, it was caused by 'online players' check and update.
Disable lifds-cp (dont execute file lifdscp_stats.cs) for a while and restart server. There should be no such messages.

[TiTANSTORM]

This is still happening even without lifds-cp running. Also, the "RecordSet (xxxx)" is always varying but "inside DBI (1188 dbi)" is always the same.

[Custodian]

This is still happening even without lifds-cp running. Also, the "RecordSet (xxxx)" is always varying but "inside DBI (1188 dbi)" is always the same.

Share your server log.

[KhaimovMR]

This is still happening even without lifds-cp running. Also, the "RecordSet (xxxx)" is always varying but "inside DBI (1188 dbi)" is always the same.

Share your server log.

Yep. I've merged your pull request and tested it on my server.
The problem is still there.
I've restarted my server now after complete excluding lifdscp_stats.cs from main.cs. Will see if this problem is still there.

Could you review the latest version of lifdscp_stats.cs with your pull-request merged?

https://github.com/KhaimovMR/lifds-cp/b ... p_stats.cs

Thanks for your help )

PS: By the way - here is the log with lifdscp_stats.cs included in main.cs - S_KHAIMOVMR-PC_2015-11-30-04-28-33_p6092.log

[Custodian]

By the way - here is the log with lifdscp_stats.cs included in main.cs - S_KHAIMOVMR-PC_2015-11-30-04-28-33_p6092.log

When you got message about outdated recordset, you can:
1) dbi.listObjects();
to check if there are any attached child recordsets
2) (from your log):
# Warning: found an outdated RecordSet (13508) inside DBI (1188 dbi). Time elapsed: 600 sec / Warn counter: 1
Call "13508.dump();" and try to call "echo(13508.getSQL());" to get source of the troubles.

[KhaimovMR]

By the way - here is the log with lifdscp_stats.cs included in main.cs - S_KHAIMOVMR-PC_2015-11-30-04-28-33_p6092.log

When you got message about outdated recordset, you can:
1) dbi.listObjects();
to check if there are any attached child recordsets
2) (from your log):
# Warning: found an outdated RecordSet (13508) inside DBI (1188 dbi). Time elapsed: 600 sec / Warn counter: 1
Call "13508.dump();" and try to call "echo(13508.getSQL());" to get source of the troubles.

Thanks, Cust!
I'll try it today at evening.
I've excluded lifdscp_stats.cs from main.cs - and there is no problem right now in logs.

Today/tomorrow i'll release a new version of lifds-cp with fixed script.

[KhaimovMR]

I've fixed this problem in version 0.9.8

LiFDS-CP thread

PS: Big thanks to Custodian for intro into the lif script debugging.

[KhaimovMR]

By a mistake new lifdscp_stats.cs file wasn't included in v0.9.8.
That's why i've released a hotfix version 0.9.8.1 right now.
This version at last fixed that bug.