Well the rebuild came back with the same issue. This issue seems to be
tied to this hardware somehow as I can build using the same process in a VM
and everything is as it should be. Diags have been ran on the hardware
with no issues found. we also removed the external storage and mounted
On 08/04/2016 07:38 AM, Rick Langston wrote:
> Well this is strange. it looks as if the process has stabilized. I didn't
> see anything in the capture that jumped out at me but will try and
> normalize the build today and see if it continues to work.
>
Well, I am glad it works now at
Things seem to stem from pulp and a connection
[root@servername ~]# /bin/systemctl status pulp_celerybeat.service
● pulp_celerybeat.service - Pulp's Celerybeat
Loaded: loaded (/usr/lib/systemd/system/pulp_celerybeat.service;
enabled; vendor preset: disabled)
Active: inactive (dead) since
On Tuesday, August 2, 2016 at 7:30:07 AM UTC-5, Chris Duryee wrote:
>
> and it will eventually die as it did last night.
>
Where would I send the debug file?
>
> On 08/01/2016 04:14 PM, Rick Langston wrote:
> > Strange, If I restart the service "/bin/systemctl status
> >
Thank you for help on this
yes here is the actual capture
command line output
[root@dscaprv01 tmp]# systemctl restart pulp_celerybeat.service
[root@dscaprv01 tmp]# systemctl status pulp_celerybeat.service
● pulp_celerybeat.service - Pulp's Celerybeat
Loaded: loaded
On 08/01/2016 09:39 AM, Rick Langston wrote:
> The backend service all say ok but when a run a katelli-service status I
> can see that celery.bet fails to status. if I restart the server it and
> immediately check the status it says running but checking the status again
> shows it timed out.
No worries! Certs don't always make it easy -- glad to hear its working!
Eric
On Tue, Jul 26, 2016 at 9:49 AM, Edgars M. wrote:
> Hi Eric
>
> I re-generated all certs and re-downloaded CA cert again and now it works!
> I have no idea what was wrong with them. Sorry
Can you run:
systemctl start httpd
journalctl -xn
On Jul 8, 2016 7:05 AM, "Edgars M." wrote:
> Hi
>
> Here it is:
>
> sudo /bin/systemctl start httpd.service
> Job for httpd.service failed because the control process exited with
> error code. See "systemctl status
No, there is nothing special about our certificates. No wildcard, no even
SAN. 2048 bits.
Why is Crane needed? Can I disable it? Can I disable everything related to
Puppet as we don't need that functionality?
I just tested it and it failed again, here is my full install command:
sudo