Bug 1131276

Summary: Server responded with an error: 'Invalid JSON file'
Product: [Fedora] Fedora Reporter: lejeczek <peljasz>
Component: satyrAssignee: Martin Milata <mmilata>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: abrt-devel-list, jfilak, mmilata, peljasz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:03:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
another one
none
reporter-ureport -vvv none

Description lejeczek 2014-08-18 20:56:47 UTC
Description of problem:

abrt tries to report kerneloops and:

--- Running report_uReport ---
Server responded with an error: 'Invalid JSON file'
reporter-ureport failed with exit code 1
('report_uReport' exited with 1)

in /var/tmp/abrt/oops-2014-08-16-08:26:15-718-0
I do  reporter-ureport -vvv
and I get:

Loaded option 'URL' = 'https://retrace.fedoraproject.org/faf'
Failed to parse operating system release string


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lejeczek 2014-08-19 06:16:33 UTC
Created attachment 928176 [details]
another one

Comment 2 Martin Milata 2014-08-19 13:48:20 UTC
Thank you for the report. Can you please post the "reporter-ureport -vvv ..." output for the kerneloops crash if you still have it? What is the name-version-release of satyr?

Comment 3 Martin Milata 2014-08-19 14:06:54 UTC
Sorry, I did not realize you already included the whole output in the description.

Can you attach the file "os_info" from /var/tmp/abrt/oops-2014-08-16-08:26:15-718-0?

Comment 4 lejeczek 2014-08-19 18:31:15 UTC
interesting fact is the os_info file is missing
but other dirs would have it, and it would look like:

AME=Fedora
VERSION="22 (Rawhide)"
ID=fedora
VERSION_ID=22
PRETTY_NAME="Fedora 22 (Rawhide)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:22"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=Rawhide
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=Rawhide

but! sometimes I see it is empty

Comment 5 lejeczek 2014-11-06 15:30:38 UTC
Created attachment 954501 [details]
reporter-ureport -vvv

Comment 6 lejeczek 2014-11-06 15:31:35 UTC
here is one(reporter-ureport.1.txt) the fails and has os_info:

NAME=Fedora
VERSION="22 (Rawhide)"
ID=fedora
VERSION_ID=22
PRETTY_NAME="Fedora 22 (Rawhide)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:22"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=Rawhide
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=Rawhide

Comment 7 Martin Milata 2014-11-07 09:09:01 UTC
The last failure seems to be caused by bug #1141549 (notice the squares in the json report), which should be fixed in abrt-2.3.0-4.fc22.

Can you still reproduce the bug where os_info is empty?

Comment 8 lejeczek 2014-11-07 14:03:00 UTC
with os_info empty it sill fails.

Comment 9 Martin Milata 2014-11-07 14:15:26 UTC
I apologize for stupid wording of my last question. Let me rephrase:

Does it still happen that crashes create directories under /var/tmp/abrt, and those directories have no os_info?

Comment 10 lejeczek 2014-11-08 18:11:36 UTC
no, it seems that all dirs now have os_info

Comment 11 Jaroslav Reznik 2015-03-03 17:03:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 12 Fedora End Of Life 2016-07-19 19:03:10 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.