Python error after starting

[Alexey Torkhov]

After startup I'm getting 4 same errors for different entities:

Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: Reporting python error
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: Traceback (most recent call last):
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: File "/usr/share/cyphesis/rulesets/mason/world/objects/elements/Fire.py", line 32, in tick_operation
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: self_ent=Entity(self.id,status=self.status)
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: File "/usr/share/cyphesis/scripts/cyphesis/Thing.py", line 13, in __getattr__
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: value = getattr(self.cppthing, name)
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: AttributeError: status
Dec 28 11:33:15 nat Cyphesis{cyphesis}[4120]: Script for "233913" has reported an error processing a tick operation. This entity is probably now inactive.

[Al Riddoch (alriddoch)]

I thought I had fixed this one. Are you sure up to date scripts and rule files are installed? If you are using a database, try running cyloadrules to load the latest copy of the rules files into the database before starting cyphesis.

The problem is that the script for Fire requires that the status attribute is set on all fire entities at creation, and this is handled in the latest rules files.

[Alexey Torkhov (atorkhov)]

Yes, it seems that I had rules from previous 0.5.14 version - fedora rpm does't do cyloadrules on upgrade.

[Wart (wart-kobold)]

Does cyloadrules only need to be called after upgrading to a new version of the cyphesis server, or is it safe to call it every time the cyphesis server process starts up?