Bug #4289
closed
Invalid alias using a numerical name causes a filter reload error
Added by Dmitry Gnoevoy almost 10 years ago.
Updated over 9 years ago.
Description
Jan 25 16:09:02 php-fpm55157: /rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:25: syntax error - The line in question reads [25]: 1 = "{ 21 }"
Files
Please attach a copy of your config.xml and /tmp/rules.debug. A sanitized version of config.xml can be copied from opening /status.php in the GUI.
- Status changed from New to Confirmed
- Priority changed from Very High to Low
You have an invalid alias named "1". Remove it or rename it.
"The alias name must be less than 32 characters long, may not consist of only numbers, and may only contain the following characters a-z, A-Z, 0-9, _." (emphasis added)
Though the backend should skip these as well to avoid a problematic ruleset, so I'll leave this open.
I Remove it and rename it. But after filter reload error the same # User Aliases
1 = "{ 21 }"
- Subject changed from error after upgade from 2.1.5 to 2.2 to Invalid alias using a numerical name causes a filter reload error
It may be an older notice that hasn't cleared, make sure the alias is gone and then force a filter reload from Status > Filter reload.
If that doesn't help, follow up on the forum.
What config look older alias?
- Status changed from Confirmed to Resolved
fixed, a notice is filed and the alias skipped if its name is only numeric.
Also available in: Atom
PDF