[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: stickshift-proxy.service failed to run 'start' task: Is a directory



Anyway thank a lot))

Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine

On Sep 2, 2012 11:27 PM, "Jason Brooks" <jbrooks redhat com> wrote:


----- Original Message -----
> From: "Igor Laskovy" <igor laskovy gmail com>
> To: "Jason Brooks" <jbrooks redhat com>
> Cc: users lists openshift redhat com, "Mike McGrath" <mmcgrath redhat com>
> Sent: Sunday, September 2, 2012 1:14:42 PM
> Subject: Re: stickshift-proxy.service failed to run 'start' task: Is a directory
>
> Thank you Jason very much, this helps! In which way you found this
> issue in the stickshift-proxy.service file?))

The error complained about a folder, I looked and found that the systemd file did point to a folder, so I changed to point to the file in that folder.

>
> A little additional question - when I add new apps they spreads
> across
> the broker and the node hosts. How to control this behavior? For
> example, how tell run php app on the node0 and mysql for it on the
> node1. And of course how to tell do not use broker for hosting apps
> (look like --skip-node option for ss-setup-broker is broken)?

I don't know about that part.

Jason

>
> On Sun, Sep 2, 2012 at 7:55 PM, Jason Brooks <jbrooks redhat com>
> wrote:
> > I encountered both of these issues when I was setting up my paas
> > yesterday. For the first, I needed to append
> > "/stickshift-proxy.env" to the end of the EnvironmentFile line in
> > /lib/systemd/system/stickshift-proxy.service. I sent a pull
> > request for that change.
> >
> > For the qpidd issue, I had to install an additional package
> > manually, I believe it was qpid-cpp-server-daemon.x86_64.
> >
> > Regards, Jason
> >
> > ----- Original Message -----
> >> From: "Igor Laskovy" <igor laskovy gmail com>
> >> To: "Mike McGrath" <mmcgrath redhat com>
> >> Cc: users lists openshift redhat com
> >> Sent: Sunday, September 2, 2012 3:40:37 AM
> >> Subject: Re: stickshift-proxy.service failed to run 'start' task:
> >> Is a        directory
> >>
> >> Hey!
> >>
> >> Additionally to previous problem - when I trying to build all lab
> >> again during executing "ss-setup-broker --skip-node" I have
> >> received
> >> new error:
> >>
> >> error reading information on service qpidd: No such file or
> >> directory
> >> Redirecting to /bin/systemctl restart qpidd.service Failed to
> >> issue
> >> method call: Unit qpidd.service failed to load: No such file or
> >> directory.
> >>
> >> All hosts have been reinstalled anew, so it happens many times.
> >>
> >> My environment is a virtual machine with Fedora 16 installed from
> >> net-install iso in minimum installation and executing steps
> >> according
> >> to
> >> https://openshift.redhat.com/community/wiki/build-multi-node-paas-from-scratch
> >> guide.
> >>
> >> Awaiting any help!
> >>
> >> On Sat, Sep 1, 2012 at 5:02 PM, Igor Laskovy
> >> <igor laskovy gmail com>
> >> wrote:
> >> > Thanks for your attention, Mike!
> >> > Scaled apps is that what I need, so still awaiting any advice.
> >> >
> >> > On Sat, Sep 1, 2012 at 4:36 AM, Mike McGrath
> >> > <mmcgrath redhat com>
> >> > wrote:
> >> >> On Sat, 1 Sep 2012, Igor Laskovy wrote:
> >> >>
> >> >>> Hello from sunny Kiev!
> >> >>>
> >> >>> Have a problem with installing Multi-node PaaS from scratch
> >> >>> according
> >> >>> to
> >> >>> https://openshift.redhat.com/community/wiki/build-multi-node-paas-from-scratch.
> >> >>>
> >> >>> When performing all step by step I execute this:
> >> >>> sudo ss-setup-broker --skip-node
> >> >>>
> >> >>> and at the end I got this error:
> >> >>> Note: Forwarding request to 'systemctl enable
> >> >>> stickshift-proxy.service'.
> >> >>> Redirecting to /bin/systemctl restart stickshift-proxy.service
> >> >>> Job failed. See system logs and 'systemctl status' for
> >> >>> details.
> >> >>>
> >> >>> In the /var/log/messages I found this:
> >> >>> Aug 31 23:19:49 broker systemd[1]:
> >> >>> [/lib/systemd/system/stickshift-proxy.service:9] Invalid
> >> >>> executable
> >> >>> path in command line, ignoring: stickshift-proxy-cfg fixaddr
> >> >>> Aug 31 23:19:49 broker systemd[1]: hsqldb.service: Supervising
> >> >>> process
> >> >>> 989 which is not our child. We'll most likely not notice when
> >> >>> it
> >> >>> exits.
> >> >>> Aug 31 23:19:51 broker systemd[1]: Failed to load environment
> >> >>> files:
> >> >>> Is a directory
> >> >>> Aug 31 23:19:51 broker systemd[1]: stickshift-proxy.service
> >> >>> failed to
> >> >>> run 'start' task: Is a directory
> >> >>>
> >> >>> Waiting for any advice!
> >> >>>
> >> >>> --
> >> >>
> >> >> Oh boy systemd fun.  I have no idea what would be causing that.
> >> >>  I
> >> >> can
> >> >> tell you stickshift-proxy would only impact scaled apps.  So at
> >> >> a
> >> >> minimum
> >> >> while you're waiting for an answer to that, you could continue
> >> >> with your
> >> >> work.
> >> >>
> >> >>         -Mike
> >> >>
> >> >>> Igor Laskovy
> >> >>> facebook.com/igor.laskovy
> >> >>> Kiev, Ukraine
> >> >>>
> >> >>> _______________________________________________
> >> >>> users mailing list
> >> >>> users lists openshift redhat com
> >> >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >> >>>
> >> >
> >> >
> >> >
> >> > --
> >> > Igor Laskovy
> >> > facebook.com/igor.laskovy
> >> > Kiev, Ukraine
> >>
> >>
> >>
> >> --
> >> Igor Laskovy
> >> facebook.com/igor.laskovy
> >> Kiev, Ukraine
> >>
> >> _______________________________________________
> >> users mailing list
> >> users lists openshift redhat com
> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
> >>
>
>
>
> --
> Igor Laskovy
> facebook.com/igor.laskovy
> Kiev, Ukraine
>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]