Bug #362
HLstats_Server->set: "map" is not a valid property name
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Daemon | |||
| Target version: | 1.6.2 | |||
| Affected Version: | Blocking Target Version: |
Description
I got "HLstats_Server->set: "map" is not a valid property name" on one of my daemons as error message.\r\n\r\nVersion: r1056
History
#1
Updated by Packhead almost 3 years ago
- Category changed from 1 to Daemon
- Priority changed from High to Normal
#2
Updated by Packhead almost 3 years ago
- Target version set to 2.0.0
#3
Updated by psychonic over 2 years ago
Need more information on this, log files, etc.
#4
Updated by psychonic over 2 years ago
- Target version changed from 2.0.0 to 1.6.2
#5
Updated by BoNzO over 2 years ago
- Status changed from New to Closed
Prob not an issue anymore since we haven't seen this for ~200 commits or so.
#6
Updated by BoNzO over 2 years ago
- Target version deleted (
1.6.2)
#7
Updated by R3M over 2 years ago
- File log_30040_20090924_10-01-48 added
#8
Updated by psychonic over 2 years ago
- Status changed from Closed to New
- Target version set to 1.6.2
Further feedback says that this bug still exists.
#9
Updated by psychonic over 2 years ago
After monitoring more servers, I've only see this error recently on Insurgency servers. It happens during the Loading map log line, although $s_addr is populated correctly. I'm not sure why the server object would be throwing this error.
#10
Updated by psychonic over 2 years ago
- File maperror.patch
added - Assignee set to psychonic
Can you try the changes from r1350 (also attached here as a patch) and see if you still receive this error on occasion?
#11
Updated by psychonic over 2 years ago
- Status changed from New to UserFeedback
#12
Updated by bo over 2 years ago
No errors anymore, looks like fixed. Thanks.
#13
Updated by psychonic over 2 years ago
- Status changed from UserFeedback to Closed
Bo Tribun wrote:
No errors anymore, looks like fixed. Thanks.
Thank you for testing. This has now been committed to the new trunk.