[Spacewalk-list] Timeouts publishing errata

[Mark]

We actually use an external Oracle database instance which runs on the same
systems as our production DBs. I'd be very surprised if that was the issue,
but I'll check with them. What I don't understand is why using the UI is
almost instantaneous, but the API takes 5 minutes. Is this just a trick of
marking the operation as done and moving on? If so is it something the API
can take advantage of?

On Mon, Aug 15, 2011 at 10:33 AM, Speagle, Andy <andy.speagle at wichita.edu>wrote:

> Hi Mark,****
>
> ** **
>
> It’s been a while since I’ve seen this problem, but I believe it might have
> something to do with the speed of your database.  I believe for my part, I
> had to migrate my Spacewalk database to a more robust server to full
> alleviate this problem in my shop.  Could that be an issue for you?****
>
> ** **
>
> Andy****
>
> ** **
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Mark
> *Sent:* Monday, August 15, 2011 11:50 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Timeouts publishing errata****
>
> ** **
>
> Thanks Walid,
> That's exactly what we're doing. In fact, I took that tack after I read
> your earlier posts. We upped the timeout in httpd.conf to 300 seconds and
> that worked for a while, but then I got another 503 error. It's now at 500
> seconds, but this seems like a ridiculous solution. I'd really like to know
> what the difference is between selecting an errata through the GUI and
> hitting publish (which happens immediately), and doing it through the API.
>
> Mark****
>
> On Fri, Aug 12, 2011 at 2:40 PM, Walid <walid.shaari at gmail.com> wrote:****
>
> Dear Mark,****
>
> ** **
>
> I am new  to this but why do not create the erratas first "unpublished"
> then run the script again with -i for publishing, this have worked for me*
> ***
>
> ** **
>
> kind regards****
>
> ** **
>
> Walid****
>
> On 12 August 2011 23:55, Mark <gajillion at gmail.com> wrote:****
>
> Anyone else experiencing this or have any ideas where to start
> troubleshooting? It happens with my own script and with the
> rhn-clone-errata.py script when I use the '-i' option.
>
> Mark****
>
> ** **
>
> On Wed, Aug 10, 2011 at 10:04 AM, Mark <gajillion at gmail.com> wrote:****
>
> I'm getting "503 Service Temporarily Unavailable" on any attempt to publish
> errata from the API. I can publish just fine by going into the GUI and
> selecting each individual errata and publishing them, but using the API
> gives me timeouts. My first attempt used 'errata.create' and set 'publish'
> to true. That failed with a timeout after 3 minutes. Next I set publish to
> 'false' and it pushed the errata in an unpublished state just fine, but then
> calling 'errata.publish' on the unpublished errata times out the same way.
> The errata are not complicated: they affect two or three packages at most
> and only a single channel. Any ideas what the problem might be?
>
> Mark****
>
>
>
> ****
>
> ** **
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list****
>
> ** **
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list****
>
>
>
>
> --
> Writing Calisthenics : http://blog.markjuric.com****
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>



-- 
Writing Calisthenics : http://blog.markjuric.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110816/94f5961d/attachment.htm>