[ovirt-devel] Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql

2019-02-19 Thread Galit Rosenthal
DS: We have the same problem with 4.2 as we have in US. DS master known issue handle by Sandro on collectd-write_syslog On Tue, Feb 19, 2019 at 12:24 PM Dan Kenigsberg wrote: > there is a parallel thread > [ovirt-devel] [URGENT] - seems like regression: Re: Re: Misc > configuration': Failed t

[ovirt-devel] Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql

2019-02-19 Thread Dan Kenigsberg
there is a parallel thread [ovirt-devel] [URGENT] - seems like regression: Re: Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql with some an idea. TL;DR: lago is not allocating a specific TTY number which postres's selinux policy requires. On Tue, Feb 19, 2019 at 12:20

[ovirt-devel] Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql

2019-02-19 Thread Eli Mesika
Galit Did you find what went wrong? On Sun, Feb 17, 2019 at 12:55 PM Galit Rosenthal wrote: > Thanks Greg > > I will check this > > > On Sun, Feb 17, 2019 at 12:51 PM Greg Sheremeta > wrote: > >> Is there any way you can run >> "systemctl status rh-postgresql95-postgresql.service" and "journal

[ovirt-devel] Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql

2019-02-17 Thread Galit Rosenthal
Thanks Greg I will check this On Sun, Feb 17, 2019 at 12:51 PM Greg Sheremeta wrote: > Is there any way you can run > "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" > like it suggests? > The logs below don't give any indication why it failed to start, afaict. > > On

[ovirt-devel] Re: Misc configuration': Failed to start service 'rh-postgresql95-postgresql

2019-02-17 Thread Greg Sheremeta
Is there any way you can run "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" like it suggests? The logs below don't give any indication why it failed to start, afaict. On Sun, Feb 17, 2019 at 4:59 AM Galit Rosenthal wrote: > Hi > > I receive this error message both in