Description of problem:
Bip is consistently inaccessible when a system is first booted.
Version-Release number of selected component (if applicable):
[mcpierce@mcpierce-server ~]$ rpm -q bip
Steps to Reproduce:
1. Reboot the system, with Bip configured to start automatically.
2. Once the system is started, attempt to connect to Bip.
Unable to connect to the configured port. The port only becomes available after logging into the machine and restarting the Bip service.
Bip to be available immediately.
It seems that changing the Bip systemd configuration from having Require to having After for network service should fix this problem. We had a similar problem with Qpid and the above change fixed that.
this appears to be fixed in Fedora 18.
It now includes a After=network.target
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here: