[BUG] new test grid

[andsim]

Steps to reproduce

1. setup grid
2. setup sim
3. land detail
4. or estate

Expected behaviour

load detail of land
name owner
setting
Tell us what should happen

Actual behaviour

owner of land should be owner for estate at start but it didnt
if u try set estates level it reverse to default setting

Server configuration

Operating system:
win 10 pro
Web server:
none
Database:
mysql 8
WhiteCore version:
git master

Logs

Please make sure that WhiteCore has made an log-file and include a link to it here
WhiteCore_Grid_20190519.log
WhiteCore_Sim_20190519.log

[andsim]

May 20 03:52:10 - [Land management] unable to find parcelID -1
May 20 03:52:18 - [Land management] unable to find parcelID -1
May 20 03:52:29 - [Gods]: God level set for Andsim AnSky, level 250
May 20 03:52:32 - [Land management] unable to find parcelID -1
May 20 03:52:45 - [ConnectorBase]: Failed to get valid number of parameters to send in remote call to b__0, expected 1, got 3
May 20 03:52:48 - [ConnectorBase]: Failed to get valid number of parameters to send in remote call to b__0, expected 1, got 3
May 20 03:53:25 - [Land management] unable to find parcelID -1
May 20 03:53:27 - [Land management] unable to find parcelID -1
May 20 03:53:28 - [Land management] unable to find parcelID -1
May 20 03:53:29 - [Land management] unable to find parcelID -1

[greythane]

Hmm.. a tad unusual :)

I am checking this out to see what is happening

[andsim]

yes i notices on standalone of it have this issues, same grid version

[greythane]

So far I am not able to reproduce this problem.

New setup...
Run up grid server ... answer all questions with the default answers except for grid owner and estate
Run up region server..
Create a new region using default answers
Assign to the grid owner estate when asked

Fire up viewer (Firestorm)
About land... no problems
View region ... no problems

[emperorstarfinder]

I tested this issue this morning on my team's internal testbed system. Unfortunately, the results I got are similar to greythane's results here. I also noticed you are using MySQL 8.0.x. I suspect the problem is not WhiteCore but is your MySQL server. In MySQL 8.0.x Oracle made changes to MySQL that previous versions of MySQL and MariaDB have been using such as the various charsets, etc. It is possible these changes in how MySQL works itself could be the culprit. I recommend testing against an older version of MySQL or use MariaDB 10.1 and see if that resolves the issue. I know if your running a full-on grid that can be a headache but it might be the issue.

[andsim]

ah i see so nothing can be done with mysql 8.0.x. i am testing on my pc before decide on a server

[greythane]

Hmmm...
I did miss the MySql 8 :(
It does appear that the latest MySql has changed the default encoding (should not be a problem but...), has added a couple more 'admin' functionality (not used anyway) and maybe dropped support for some 'old' types which may or may not be a problem.
I personally (and for business) have used MariaDb in preference to MySql as there are shown performance benefits which still appears to be the case even when comparing to MySql 8.

I will fire up a MySql 8 db to test this.

[andsim]

hmm looking mysql saying 5.5.61
i going test this again. i am thin this was filebase issues

[andsim]

ihave redo db and running 5.5.61

[andsim]

oik i have redo it db yet not 8.0.x but 5.5.61 mysql, still getting different issues than at first open but same issues as in picture

[andsim]

also to note this i am using fs 5.1.7 and now using latest Mariadb

[emperorstarfinder]

Try using the latest Firestorm for OpenSim. There have also been some recent updates in the land management tools. Also, set your console log levels to debug. This will hopefully show any potential errors that are coming up but not shown when the log level is info. To do this use the command set log level debug. Usually, it is best to do it both in the grid and region server this way you can see if there is a problem with communications between the grid and region as well as the region obtaining assets.

This might be caused by how the information is getting stored in the DB. For the viewer to get the about land information it relies on things being sent to it that are in the DB. So there is something likely not getting stored correctly. This is the price of change sometimes.

[andsim]

please note earlier post is not shown to public as set a outdated.

[greythane]

Just to confirm....
I have been using MySql V8 (windows installation) for the past week and have not observed any issues.

[andsim]

hmm. could i be using older version?

[greythane]

Andsim,
...do you build from source or are you using a binary package?
I think I did build a Win package for you quite a while ago?

[andsim]

maybe build one cant remember

[greythane]

I have put up a development snapshot build at
https://drive.google.com/file/d/1jplvJyOAbW7fPPF_LeNqzhlabc9bWKci/view?usp=sharing
Testing, comments and particularly errors are appreciated.

This is a 7z package of the WhiteCoreSim folder, built using .Net 4.7.2 with x64 architecture.

Note: The Config structure has changed but is compatible with an existing configuration (0.9.4+)

[andsim]

all dlls files
detected norton

[andsim]

it delete on me

[greythane]

Just to clarify....
This is a know 'false positive' and there are many posts to the fact of it being an annoyance, particularly for software that is custom or not 'mainstream'.

To bypass... (from Norton's somewhat sparse information
https://www.symantec.com/connect/forums/how-disable-wsreputation1-detection

"On the Action tab you can set the Action for unproven files to Leave alone (log only) or Ignore. This will leave UNproven files alone (not detected)"

From https://www.nsoftware.com/kb/xml/11011701.rst

Symantec/Norton Products detecting WS.Reputation.1
Symantec/Norton products, especially Symantec Endpoint Protection, may incorrectly detect "WS.Reputation.1" when you run one of our installers.
Date Entered: 11/01/2017 Last Updated: 11/01/2017

Customers using a Symantec or Norton product will occasionally run into an issue where "WS.Reputation.1" is detected when one of our installers is executed (Symantec Endpoint Protection, in particular, is well-known for doing this). This detection is a false positive.

WS.Reputation.1 is not a real virus category, it is just the name that Symantec uses for files that "have a low reputation score". It is important to understand that all of that information used to produce the WS.Reputation.1 detection is based completely upon what Symantec calls "the wisdom of crowds". While the exact information factored into the reputation analysis is known only to Symantec, we do know that it is not based upon the detection of any specific, known threats, which is likely why it has a high rate of false positives.

WhiteCoreSim_Eset_scanlog.txt

[andsim]

ok complete wipe it untouch get this

Aug 13 09:06:35 - [Base HTTP server]: Error - Failed to listen on prefix 'http://+:8002/' because it conflicts with an existing registration on the machine.

[andsim]

same that one code base issues not ini
i look grid,
not standalone

[emperorstarfinder]

It might be a case of rebooting the machine as it sounds like that is being caused by a port not getting closed by windows even though you have nothing currently running on that port.

[greythane]

The 'Failed to listen...' error is probably due to another instance running that already has control of port 8002.
(maybe you ran the grid and sim bat files that were supplied without changing configuration? This would run a grid server AND a standalone setup trying to use the same port)

Run the 'cmd' prompt as administrator and enter ...

netstat -an | find "8002" to show if the port is in use
netstat -abn to show the program that has the port open.

WhiteCoreSim is supplied configured as a standalone instance. This is for testing and immediate run up to check things.
If grid operation is required then you (currently) need to edit the 'WhiteCore.ini' setting in the 'Config' folder. Details to change to the grid mode of operation are at the top and involve commenting the 'Include-Standalone...' and uncommenting the 'Include-Grid...' lines.

If you have a recent configuration this can be used 'as is' by just deleting the 'bin' folders in your setup and copying in the 'bin' folder of the updated package.

The next release package will ask for to reconfigure or confirm the current configuration on startup.

[andsim]

ok it was whitecore.ini. hmm it dsidnt ask for admin user, when i get in land owner is unknown user but no more error

[andsim]

also had to set my avatar userlevel to 250

[andsim]

is this normal?

[andsim]

dont like it ask do you really want to quit. is there away bypass that?

[greythane]

On initialising a new database the system will request the 'grid owner' name. This is the admin user and is automatically set to level 250. This user's estate will also be created.
If you are using an existing database then this will not happen.
If you add another user who you want to be an admin then you will need to elevate their level.. as you did.

The 'missing texture' shown on your avatar implies that the textures for the avatar were not saved/loaded.
Did you load this avatar from an IAR file?
If so and this loads correctly in Opensim then if possible I would like to have a look at it to see why the textures are not being loaded correctly. As far as I am aware (my own tests) loading an avatar IAR works as expected.

As for the 'quit' command... The quit and confirm was arrived at to ensure that the grid manager did not inadvertently kill everything accidentally, say be typing exit etc.

[andsim]

hmm
didnt ask for grid owner it ask owner estate on start might try again,i know it should have ask grid own name and such

[andsim]

i didn't know, i have to upload iar? normally it default

[andsim]

https://pastebin.com/MT5RUFdv it never ask about who is estate user on sqlite or throu MariaDB 10.4.7

[emperorstarfinder]

It looks to me like the system is trying to create an estate for the Grid Owner account. The Grid Owner account technically should not need an estate unless you really want the Grid Owner account to actually own a region.

I would be looking at whether or not the 'unknown user' it references is really the Grid Owner account it is looking for to associate an estate with. If so then you know the grid owner account is in fact not getting created.

Personally, I would not by default be assigning an estate to the Grid Owner account in a production level grid. I would let that be something that can be decided by the user during the initial setup of WC. Some grids may not want their grid owner account owning regions to avoid potential conflicts or some of the foolish accusations we have seen other grid owners (using other architectures) being accused of in the past.

[andsim]

i understand your point emperorstarfinder, finding strange it didnt add them or ask it,
it look like it didnt create region owner either
i had to create grid user as my self

[greythane]

If grid owner and estate details were not requested at startup then a previously installed database was most likely being used.

Attached is a complete log from a clean startup ... i.e. the very first run.
The only changes were to change the grid name and the IP address. This was done using the startup configurator with the default responses selected.

Using SQLite as my Win MySql V8 server has crashed and burned... back to MariaDB :)
WhiteCore_Grid_20190815.log

[andsim]

i wipe out tables but not delete them but didnt ask expect estate name

[greythane]

Hmm.. I have just re-installed MySql v8, rebuilt and run up a new grid setup on my Windows 10 system and it appears that the creation of the system users is being missed, I suspect due to speed problems whilst running on Windows :(

I will look at this immediately to find out why this critical step is being skipped.

[andsim]

not using mysql 8 i using new db that recommend to use

[emperorstarfinder]

I am not so sure that the speed of windows which we all know is notoriously slow, after all, someone thought you all would like those evilly slow bells and whistles at Microsoft (kidding) LOL. Would be the cause itself. This reminds me of the troubles we had when we added the sink accounts for the builtin economy as a system account but the system skipped right over creating it.

[greythane]

I have just pushed through a heap of corrections and updates.
I have rebuilt a Win x64 package for you to checkout. It can be found here...

https://drive.google.com/file/d/1Xunx_w7agntFq0fr5eCEdcI4MyBVLZro/view?usp=sharing

Any feedback is welcome.
Greythane