Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
-Original Message- From: fossology-boun...@fossology.org [mailto:fossology- boun...@fossology.org] On Behalf Of Peter Jalajas, GigaLock Backup Services Sent: Tuesday, August 02, 2011 8:22 PM To: fossology@fossology.org Subject: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression This is VERY likely the cause. Please do delete the uploads completely and try again. The delete must run to a successful completion before you try and upload again. Otherwise, you run the risk of having 2 uploads in your DB with the same signature. Mary Likely due to trying to delete a prior Upload of the RedHat test file that threw a couple of FAILED agents. Deleting these Uploads and starting again is no big deal, I'm just familiarizing myself with FOSSology. Suggestions welcome! (I'm not afraid of the command line.) Thanks! Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
FWIW, this problem with the delete agent is addressed in V 2.0. There is another problem with the delete agent that is a bit more difficult. We store each file separately in the repository, so deleting say an iso with 2M files can take a while. Until/unless we go to a different file storage scheme, perhaps saving the files in large blocks, this problem will be with us. Bob Gobeille On Aug 3, 2011, at 10:57 AM, Laser, Mary wrote: -Original Message- Sent: Tuesday, August 02, 2011 8:22 PM Subject: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression This is VERY likely the cause. Please do delete the uploads completely and try again. The delete must run to a successful completion before you try and upload again. Otherwise, you run the risk of having 2 uploads in your DB with the same signature. Mary Likely due to trying to delete a prior Upload of the RedHat test file that threw a couple of FAILED agents. Deleting these Uploads and starting again is no big deal, I'm just familiarizing myself with FOSSology. Suggestions welcome! (I'm not afraid of the command line.) ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
Thanks, Mary and Bob. Perhaps my problem was, more specifically, that I deleted the Uploaded file _while_ the Agents were still running on it? Should I have deleted the _jobs_ first, and then the Upload? When I deleted the Upload, there were many jobs in the queue for _other_ Uploads. In such a case, could it take quite a long time before the Scheduler even _begins_ to delete the Upload? I don't remember now, but I believe I recall seeing the delagent job at the very bottom of the queue for that Upload, making it appear that the Scheduler would delete the Upload only having completed all the jobs for that Upload (I don't recall the job numbers)--is that true? Delete Upload doesn't automatically deletes all jobs for that Upload, does it? Thanks again, Pete On Wed, Aug 3, 2011 at 1:05 PM, Bob Gobeille wrote: FWIW, this problem with the delete agent is addressed in V 2.0. There is another problem with the delete agent that is a bit more difficult. We store each file separately in the repository, so deleting say an iso with 2M files can take a while. Until/unless we go to a different file storage scheme, perhaps saving the files in large blocks, this problem will be with us. Bob Gobeille On Aug 3, 2011, at 10:57 AM, Laser, Mary wrote: -Original Message- Sent: Tuesday, August 02, 2011 8:22 PM Subject: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression This is VERY likely the cause. Please do delete the uploads completely and try again. The delete must run to a successful completion before you try and upload again. Otherwise, you run the risk of having 2 uploads in your DB with the same signature. Mary Likely due to trying to delete a prior Upload of the RedHat test file that threw a couple of FAILED agents. Deleting these Uploads and starting again is no big deal, I'm just familiarizing myself with FOSSology. Suggestions welcome! (I'm not afraid of the command line.) ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
See inline responses... -Original Message- Subject: Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression Thanks, Mary and Bob. Perhaps my problem was, more specifically, that I deleted the Uploaded file _while_ the Agents were still running on it? Should I have deleted the _jobs_ first, and then the Upload? Yes and yes. When I deleted the Upload, there were many jobs in the queue for _other_ Uploads. In such a case, could it take quite a long time before the Scheduler even _begins_ to delete the Upload? It depends on how your scheduler is configured. If you have installed on a single system (probably the case), and are using the default Scheduler.conf file, then you can run a max of 3 agents at one time (%Host localhost 3 1). I don't remember now, but I believe I recall seeing the delagent job at the very bottom of the queue for that Upload, making it appear that the Scheduler would delete the Upload only having completed all the jobs for that Upload (I don't recall the job numbers)--is that true? Yes Delete Upload doesn't automatically deletes all jobs for that Upload, does it? No. that has to be done manually Mary Thanks again, Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression
Thanks, Mary. I'd be glad to edit any user docs with these notes, if that makes sense. On Wed, Aug 3, 2011 at 2:55 PM, Laser, Mary wrote: See inline responses... -Original Message- Subject: Re: [FOSSology] DBaccess(7): ERROR: more than one row returned by a subquery used as an expression Thanks, Mary and Bob. Perhaps my problem was, more specifically, that I deleted the Uploaded file _while_ the Agents were still running on it? Should I have deleted the _jobs_ first, and then the Upload? Yes and yes. When I deleted the Upload, there were many jobs in the queue for _other_ Uploads. In such a case, could it take quite a long time before the Scheduler even _begins_ to delete the Upload? It depends on how your scheduler is configured. If you have installed on a single system (probably the case), and are using the default Scheduler.conf file, then you can run a max of 3 agents at one time (%Host localhost 3 1). I don't remember now, but I believe I recall seeing the delagent job at the very bottom of the queue for that Upload, making it appear that the Scheduler would delete the Upload only having completed all the jobs for that Upload (I don't recall the job numbers)--is that true? Yes Delete Upload doesn't automatically deletes all jobs for that Upload, does it? No. that has to be done manually Mary Thanks again, Pete ___ fossology mailing list fossology@fossology.org http://fossology.org/mailman/listinfo/fossology
