Weird LUA bugs in server logs

[solarisfire]

Avorion server Beta 0.16.7 r11165 4b472bf34ee5 running on Ubuntu 16.04.4 LTS

 

Getting errors such as:

 

2018-06-01 10-20-02| starting event traderattackedbypiratesstarter

2018-06-01 10-20-11| could not execute function 'onSectorEntered' in '"data/scripts/player/fakedistresssignal.lua"':

2018-06-01 10-20-11| data/scripts/player/fakedistresssignal.lua:72: attempt to call field 'createDisruptor' (a nil value)

2018-06-01 10-20-11| stack traceback:

2018-06-01 10-20-11|    data/scripts/player/fakedistresssignal.lua:72: in function <data/scripts/player/fakedistresssignal.lua:62>

 

and

 

2018-05-31 17-48-20| could not execute function 'updateServer' in '"data/scripts/entity/merchants/tradeship.lua"':

2018-05-31 17-48-20| vector::_M_range_check

2018-05-31 17-48-20|    [C]:-1: in function isDockFree

2018-05-31 17-48-20|    data/scripts/entity/ai/dock.lua:31: in function flyToDock

2018-05-31 17-48-20|    data/scripts/entity/ai/trade.lua:76: in function updateServerAI

2018-05-31 17-48-20|    data/scripts/entity/merchants/tradeship.lua:62: in function ?

 

and

 

2018-05-31 20-02-55| error constructing Entity: Entity with index Uuid doesn't exist at        [C]:-1: in function Entity

2018-05-31 20-02-55|    data/scripts/sector/factionwar/temporarydefender.lua:69: in function onShotHit

2018-05-31 20-02-55|    data/scripts/sector/factionwar/temporarydefender.lua:63: in function ?

2018-05-31 20-02-55| error constructing Entity: Entity with index Uuid doesn't exist at        [C]:-1: in function Entity

2018-05-31 20-02-55|    data/scripts/sector/factionwar/temporarydefender.lua:69: in function onShotHit

2018-05-31 20-02-55|    data/scripts/sector/factionwar/temporarydefender.lua:63: in function ?

2018-05-31 20-02-57| scheduled save for sector (-121:-180), 0x7efbf8f0e050, entities: 1303

 

It doesn't crash the server or seem to affect anything negatively, but are these errors normal?

[cepheni]

No, they definitely are not normal. They mean something in that script went wrong and the script is then terminated. The server isn't affected by this, but you as a player may be. So thanks for reporting, we will look into this :)