| Summary: | razor-report failed when reporting spam message... | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Franck MAHE <mahe> |
| Component: | RPM Packages | Assignee: | Jerome Quelin <jquelin> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mahe, marja11 |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | perl-Razor-Agent-2.850.0-9.mga4 | CVE: | |
| Status comment: | |||
|
Franck MAHE
2015-04-04 15:05:31 CEST
CC:
(none) =>
mahe @ jquelin The above means nothing to me, assigning to you because you're the maintainer of perl-Razor-Agent and you'll understand and be able to see whether it is a bug for us, an upstream bug or something else. CC:
(none) =>
marja11 Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
NEW =>
RESOLVED |
Hi All, Strange but after the registration to Razor Network, everything is working fine except the razor-report component. When I tried to report a spam to Razor Network, it fails with.... Apr 04 14:32:11.554189 report[23564]: [ 2] [bootup] Logging initiated LogDebugLevel=5 to file:/var/log/razor/razor-agent.log Apr 04 14:32:11.554476 report[23564]: [ 5] computed razorhome=/etc/razor, conf=/etc/razor/razor-agent.conf, ident=/etc/razor/identity-ruDOtG3G1b Apr 04 14:32:11.554526 report[23564]: [ 2] Razor-Agents v2.84 starting razor-report --home=/etc/razor -f Apr 04 14:32:11.554665 report[23564]: [ 5] read_file: 2 items read from /etc/razor/identity-ruDOtG3G1b Apr 04 14:32:12.491485 report[23564]: [ 5] read_file: 1 items read from /etc/razor/servers.discovery.lst Apr 04 14:32:12.500752 report[23564]: [ 5] read_file: 4 items read from /etc/razor/servers.nomination.lst Apr 04 14:32:12.518905 report[23564]: [ 5] read_file: 3 items read from /etc/razor/servers.catalogue.lst Apr 04 14:32:12.519304 report[23564]: [ 5] read_file: 29 items read from /etc/razor/server.n003.cloudmark.com.conf Apr 04 14:32:12.519415 report[23564]: [ 5] read_file: 29 items read from /etc/razor/server.n003.cloudmark.com.conf Apr 04 14:32:12.519513 report[23564]: [ 5] read_file: 27 items read from /etc/razor/server.n001.cloudmark.com.conf Apr 04 14:32:12.519603 report[23564]: [ 5] read_file: 27 items read from /etc/razor/server.n001.cloudmark.com.conf Apr 04 14:32:12.519703 report[23564]: [ 5] read_file: 29 items read from /etc/razor/server.n002.cloudmark.com.conf Apr 04 14:32:12.519798 report[23564]: [ 5] read_file: 29 items read from /etc/razor/server.n002.cloudmark.com.conf Apr 04 14:32:12.519846 report[23564]: [ 5] 170013 seconds before closest server discovery Apr 04 14:32:12.520746 report[23564]: [ 5] 168103 seconds before closest server discovery Apr 04 14:32:12.520834 report[23564]: [ 5] Connecting to n003.cloudmark.com ... Apr 04 14:32:12.881522 report[23564]: [ 4] n003.cloudmark.com >> 25 server greeting: sn=N&srl=22167&a=l&a=cg Apr 04 14:32:12.881802 report[23564]: [ 4] n003.cloudmark.com << 25 Apr 04 14:32:12.882301 report[23564]: [ 4] n003.cloudmark.com << 46 Apr 04 14:32:13.248338 report[23564]: [ 4] n003.cloudmark.com >> 36 Apr 04 14:32:13.248927 report[23564]: [ 4] n003.cloudmark.com << 43 Apr 04 14:32:13.457038 report[23564]: [ 4] n003.cloudmark.com >> 7 Apr 04 14:32:13.457205 report[23564]: [ 5] Authenticated user=ruDOtG3G1b Apr 04 14:32:13.457584 report[23564]: [ 4] n003.cloudmark.com << 32 Apr 04 14:32:13.635846 report[23564]: [ 4] n003.cloudmark.com >> 9 Apr 04 14:32:13.636293 report[23564]: [ 4] mail 1.0, eng 8: got err 221 for query: HASH - HASH(0x1435b10),3 keys a => r e => 8 s => ARRAY - ARRAY(0x135ab68),1 items YH7y1SGhx0AA Apr 04 14:32:13.636398 report[23564]: [ 3] Finished report. Apr 04 14:32:13.636464 report[23564]: [ 5] disconnecting from server n003.cloudmark.com Apr 04 14:32:13.636561 report[23564]: [ 4] n003.cloudmark.com << 5 After several search on the net, err 221 stands for Attempt to revoke unknown content (received after submitting vr4 sig with ep4 uninitialized) When I tried to submit the sig manually, it worked but when I tried to report a spam on the fly with spamassassin -r or cat mail | razor-report --home=/etc/razor -f, I've the above error 221. Other question, the official vipul website stands that the 2.84 is the latest release, and the RPM Package stands for 2.85, so...