<div dir="ltr">A bit more information about the error I am seeing. The page, when it finally times out, provides a 500 error and generates a traceback email to me. If I had to guess, the long running postgres operation failed and rolled back and is why Perl code below is complaining about missing postgres objects. I poked through /var looking for recently updated logfile and didn't find anything to help me with any further clues. The filesystem that hold my postgres database has 11G still available and while I wasn't watching the disk closely the entire time it was running, I don't believe it would eat up 11G of space. The rest of this email is the traceback:<div>
<div><br></div><div><font><span style="font-size:10pt">The following exception occurred while executing this request:<br>
POST /network/software/channels/manage/edit.pxt HTTP/1.1 (from browser)<br>
/network/software/channels/manage/edit.pxt (from Apache)<br>
<br>
Date:<br>
Thu Jun 20 16:59:12 2013<br>
<br>
Headers:</span></font><br></div><div style><font><span style="font-size:10pt">...<http headers left out of this email></span></font></div><div style><font><span style="font-size:10pt">Form variables:<br>
channel_arch => 513<br>
channel_description => <br>
channel_gpg_key_fp => 7EFB 8811 DD11 E380 B679 FCED FF01 125C DE7F 38BD<br>
channel_gpg_key_id => DE7F38BD<br>
channel_gpg_key_url => <a href="https://mymail.qualcomm.com/owa/redir.aspx?C=2PdCNGzM50Gui9WN9UOVZ3uoiCKnQdAI4relTaV_GtnXBp3bcfOZ5grk_6DD3YyMIgl7zxtgOSg.&URL=https%3a%2f%2ffedoraproject.org%2fstatic%2fDE7F38BD.txt" target="_blank">
https://fedoraproject.org/static/DE7F38BD.txt</a><br>
channel_name => Neo Fedora 18 Core x86_64 Updates<br>
channel_parent => 110<br>
channel_summary => Fedora 18 Core x86_64 Updates<br>
cid => <br>
clone_from => 134<br>
clone_type => current<br>
new_channel_label => neo-fedora18-x86_64-updates<br>
pxt:trap => rhn:channel_edit_cb<br>
submit => Create Channel<br>
<br>
User Information:<br>
User admin-crad (id 2, org_id 2)<br>
<br>
Error notes:<br>
(none)<br>
<br>
Initial Request:<br>
Yes<br>
<br>
Error message:<br>
RHN::Exception: DBD::Pg::db do failed: ERROR: no such savepoint<br>
RHN::DB /usr/share/perl5/vendor_perl/RHN/DB.pm 121 RHN::Exception::DB::throw<br>
RHN::DB::db /usr/share/perl5/vendor_perl/RHN/DB.pm 185 RHN::DB::handle_error<br>
RHN::DB::db /usr/share/perl5/vendor_perl/RHN/DB.pm 200 RHN::DB::db::rollback<br>
Sniglets::ChannelEditor /usr/share/perl5/vendor_perl/Sniglets/ChannelEditor.pm 283 RHN::DB::db::nested_rollback<br>
PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 482 Sniglets::ChannelEditor::channel_edit_cb<br>
PXT::Request /usr/share/perl5/vendor_perl/PXT/Request.pm 548 PXT::ApacheHandler::pxt_parse_data<br>
PXT::Handlers /usr/share/perl5/vendor_perl/PXT/Handlers.pm 115 PXT::Request::include<br>
PXT::Parser /usr/share/perl5/vendor_perl/PXT/Parser.pm 141 PXT::Handlers::pxt_include_handler<br>
PXT::Parser /usr/share/perl5/vendor_perl/PXT/Parser.pm 72 PXT::Parser::expand_tag<br>
PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 456 PXT::Parser::expand_tags<br>
PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 103 PXT::ApacheHandler::pxt_parse_data<br>
PXT::ApacheHandler /usr/share/perl5/vendor_perl/PXT/ApacheHandler.pm 103 (eval)<br>
main -e 0 PXT::ApacheHandler::handler<br>
main -e 0 (eval)</span></font><font><span style="font-size:10pt"><br></span></font></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 20, 2013 at 2:47 PM, Jon Miller <span dir="ltr"><<a href="mailto:jonebird@gmail.com" target="_blank">jonebird@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would like to continue to use the same base Fedora 18 channel but clone the Updates channel to be managed independently from the original. (Idea is that separate profiles can use separate Updates channels and manage the updates at their own pace.) When I try cloning the channel from the UI, I end up waiting a very long time just for the request to time out.<div>
<br></div><div>The updates channel currently has 14,049 packages and while I wait for the update, I notice postgres working hard but I haven't attempted to discover the statement being ran yet.</div><div><br></div>
<div>I'm hoping that others have a better / alternative recommendation that I could follow?</div><div><br></div><div>Thank you,</div><div>Jon Miller</div></div>
</blockquote></div><br></div>