Closed
      
        Bug 914039
      
      
        Opened 12 years ago
          Closed 12 years ago
      
        
    
  
[stage] Internal server error(500) on https://crash-stats.allizom.org/  
    Categories
(Socorro :: Webapp, task)
        Socorro
          
        
        
      
        
    
        Webapp
          
        
        
      
        
    Tracking
(Not tracked)
        VERIFIED
        FIXED
        
    
  
        
            59
        
    
  
People
(Reporter: AlinT, Unassigned)
References
()
Details
(Whiteboard: [fromAutomation])
Attachments
(2 files)
Accessing https://crash-stats.allizom.org/ returns 500 Internal Server Error
| Reporter | ||
          Updated•12 years ago
           
         | 
      
Whiteboard: [fromAutomation]
          Comment 1•12 years ago
           
         | 
      ||
I wasn't able to consistently reproduce a 500 error on stage but they do indeed exist and are playing havoc with our automation. Can we please make stage stable again. Noming to blocker.
[09:03:17.583] GET https://crash-stats.allizom.org/topcrasher/products/Firefox/versions/26.0a1?days=7 [HTTP/1.1 500 INTERNAL SERVER ERROR 122304ms]
Not sure which error is most helpful but here are a few from errormill that occurred during the timeframe I was reproducing AlinT's experiences.
https://errormill.mozilla.org/webtools/socorro-stage/group/97549/
https://errormill.mozilla.org/webtools/socorro-stage/group/99799/
https://errormill.mozilla.org/webtools/socorro-stage/group/97559/
Severity: normal → blocker
          Updated•12 years ago
           
         | 
      
Target Milestone: --- → 59
          Comment 2•12 years ago
           
         | 
      ||
Issue was caused by failed Postgres database stage refresh.
I applied passwords this morning, reset crontabbers config and stage started working again.
Depends on: 914155
          Comment 3•12 years ago
           
         | 
      ||
so this this resolved now?
          Comment 4•12 years ago
           
         | 
      ||
(In reply to Chris Lonnen :lonnen from comment #3)
> so this this resolved now?
Stage appears to be in a healthier state; are we still waiting for the bug 914155 to be resolved?
          Updated•12 years ago
           
         | 
      
Flags: needinfo?(sdeckelmann)
          Comment 5•12 years ago
           
         | 
      ||
Working now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Reporter | ||
          Comment 7•12 years ago
           
         | 
      ||
This is reproducible again.
I've attached a screenshot of the issue
| Reporter | ||
          Updated•12 years ago
           
         | 
      
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
          Comment 8•12 years ago
           
         | 
      ||
Bumping to resolved fixed - stage is up again and we were able to get a passing build - http://qa-selenium.mv.mozilla.com:8080/view/Socorro/job/socorro.stage/172/
We are tracking a different behavior where we're seeing spurious 500's on the reports as well as a potential perf regression on queries (unconfirmed & still investigating). Tracker bug is bug 922662.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Flags: needinfo?(sdeckelmann)
Resolution: --- → FIXED
          Updated•12 years ago
           
         | 
      
Flags: needinfo?(alin.trif)
| Reporter | ||
          Comment 9•12 years ago
           
         | 
      ||
It seems this is fixed.
I cannot longer reproduce 500s on the stage site
Bumping to VF
Status: RESOLVED → VERIFIED
Flags: needinfo?(alin.trif)
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•