Bug 767284 - -- 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
Summary: -- Running analyze_RetraceServer --- Querying server settings Preparing an ar...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: retrace-server
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 17:42 UTC by akshay vyas
Modified: 2012-09-21 14:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-21 14:13:33 UTC
Type: ---

Attachments (Terms of Use)
a text file of the process failure (1.12 KB, application/octet-stream)
2011-12-13 17:42 UTC, akshay vyas 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.