Bug 767284

Summary: -- Running analyze_RetraceServer --- Querying server settings Preparing an archive to upload Uploading 24808 bytes Upload successful Retrace job started Initializing virtual root Initializing virtual root Initializing virtual root Retrace job failed Retra
Product: [Fedora] Fedora Reporter: akshay vyas <akshayvyas29>
Component: retrace-serverAssignee: abrt <abrt-devel-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: abrt-devel-list, dvlasenk, dwmw2, iprikryl, jmoskovc, kklic, mmilata, mtoman, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-21 14:13:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
a text file of the process failure none

Description akshay vyas 2011-12-13 17:42:35 UTC
Created attachment 546307 [details]
a text file of the process failure

Description of problem:Initializing virtual root OK
Generating backtrace Error
Unable to chmod the executable

(exited with 1)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:server retracing failed


Expected results:


Additional info:it says unable to chmod the executable

Comment 1 Michal Toman 2012-01-05 09:02:36 UTC
I've pushed an update to the Retrace Server. In this case the retrace should either succeed or show a better error message.

Comment 2 akshay vyas 2012-01-05 17:31:56 UTC
i found out something interesting but im not sure why it happens......when during the installation you make normal use,if you give admin powers to normal user...ie adding the user in admin group...then only it will show this error and if you dont include the user in admin/root's group it wont give this error