Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2.0
-
Labels:None
-
Story Points:1
-
Rank:6990
-
Sprint:2016#01
Description
Pre-conditions
Reproduction steps
- As an admin, I set a wrong db information in /etc/opush/opush.ini or /etc/obm/obm_conf.ini
- I restart opush
Current behavior
- NOK it listens on the port 8082
- NOK I can administrate opush using crash
Expected behavior
- OK it doesn't listen on the port 8082
- OK I can't administrate opush using crash
- OK I have some logs in opush.log telling that opush won't start
Impacts: The opush startup
QA: I've tested on a debian that: