Re: [Ground-user] Error generating reports -> ERROR: relation "page_summary_norm_mv" does not exist
Status: Beta
Brought to you by:
calumfodder
From: Calum F. <cal...@gm...> - 2011-04-11 18:37:38
|
Hiya, My first thoughts are: verify your connection details to the db. If these are not correct then I could see how it would throw this error as conn is defined by creating the db connection. If this fails then it will exit on the line that you specified was in the error....I may need to tidy that up a bit. Cheers Cal On 11 April 2011 16:30, Ouray Viney <ou...@vi...> wrote: > Hi Calum: > OK, so it appears I jumped the gun. After trying to generate scripts a > second time, I am seeing the following error thrown by the groundReport.py. > grinder@hostname:~/grinder_artifacts/ground_report-1.5/bin$ > ./generateReport.bash /test_data/PEValidation_1104_R1T1 > Traceback (most recent call last): > File > "/opt/home/grinder/grinder_artifacts/ground_report-1.5/lib/groundReport.py", > line 367, in <module> > conn.close() > NameError: name 'conn' is not defined > -- > grinder@hsotname:~/grinder_artifacts/ground_report-1.5/bin$ grep conn > ../lib/groundReport.py > conn = du.getTxDbConnection(d, u, p, v) > c = conn.cursor(1) > sg = StandardGrapher(loadRun, loadRunList, conn, dataType, path, > lang, imageFormat, resourceFile) > mg = MultithreadGrapher(loadRun, loadRunList, conn, dataType, > path, lang, imageFormat, resourceFile) > ac = ArticleCreation(project, loadRun, loadRunList, pagePair, test, > conn, dataType, outputFormat, path, lang, booleanDict['archive'], > booleanDict['useConcurrentUserComparisonGraphs'], > booleanDict['useWatermark'], watermarkImage, imageFormat, resourceFile) > conn.close() > Any thoughts? > Cheers, > Ouray > On Mon, Apr 11, 2011 at 8:06 AM, Ouray Viney <ou...@vi...> wrote: >> >> Hi Calum: >> Thank you for your reply. Sorry I am a bit delayed getting back to you. >> I did as you requested, I tweaked the groundReport.properties as >> recommended. I retried the report generation script and this time had no >> errors (sweet!). >> So, for now, you have solved my issues generating reports. Now I have to >> review the generated reports. >> Thank you for your Support! >> Ouray >> >> On Fri, Apr 8, 2011 at 2:45 PM, Calum Fitzgerald >> <cal...@gm...> wrote: >>> >>> Hi Ouray, >>> >>> Please cc the ground-user mailing list on all correspondence so that >>> the mailing list keeps a record. Thanks. >>> >>> I've had a look at both the files that you sent. >>> >>> The data.properties file is ok. >>> >>> The groundReport.properties file has a lot of stuff switched on. >>> >>> regarding the following: >>> >>> ''' >>> ################# >>> # >>> # Select Reports >>> # >>> ################# >>> # >>> #choose report type (boolean y or n) >>> # >>> SummaryArticle=y >>> IndividualTestArticle=y >>> IndividualPageArticle=y >>> PageBreakdownArticle=y >>> LoadRunComparisonArticle=y >>> >>> ''' >>> >>> Please can you try it with only the summary report switched on and all >>> the others switched off. >>> The page reports are incompatible with your data type..as you only >>> have norm data and not http data. Page reports are for http data. >>> The LoadRunComparisonArticle is for comparing multiple runs, which I >>> don't think you are trying to do in this instance. >>> Anyway lets start with one report, get that working and then move onto >>> the others if necessary. >>> >>> Regarding the following section: >>> >>> ''' >>> ################# >>> # >>> # Select Graphs >>> # >>> ################# >>> # >>> ''' >>> >>> You have a number of the graphs switched on as well. For the purposes >>> of getting things running can you have them all switched off as well. >>> >>> The reports automatically create graphs which are incorporated into >>> the reports so you don't need to produce the graphs if you are >>> producing a report....unless there is a specific graph you are looking >>> for. >>> >>> Any graph with HTTP in its name is specifically for HTTP type data, if >>> a graph does not have HTTP in its name it should be safe to use with >>> norm type data. >>> >>> So long short lets try and output only a summary report to see if we >>> can narrow down where the problem might be.. >>> >>> Cheers >>> Cal >>> >>> >>> On 8 April 2011 14:02, Ouray Viney <ou...@vi...> wrote: >>> > HI Calum: >>> > >>> > The OSS world is amazing. Thank you for your reply! >>> > >>> > OK, first, let me answer your questions. >>> > >>> > I am not have any issues with the databaseInterface.bash script at all. >>> > >>> > I have loaded "norm" data into the reporting DB (see attached >>> > properties >>> > files you requested). >>> > >>> > Looking forward to solving this with you. >>> > >>> > Cheers, >>> > >>> > Ouray >>> > >>> > On Thu, Apr 7, 2011 at 11:56 AM, Calum Fitzgerald >>> > <cal...@gm...> wrote: >>> >> >>> >> Hi, >>> >> >>> >> Apologies for the slight delay in response. >>> >> >>> >> I'm glad you have managed to load the data into the Postgres DB, are >>> >> you still having problems with the databaseInterface script? >>> >> >>> >> With respects to the report generation I am assuming that you have >>> >> loaded norm data into the database. >>> >> >>> >> The table page_summary_norm_mv does not exist for data of type 'norm' >>> >> as norm data does not have the pages (composite tests) which are >>> >> generated from the http plugin. >>> >> >>> >> The report should not be trying to access this table if the data type >>> >> has been set to norm. >>> >> >>> >> Please could you let me know the settings in your data.properties and >>> >> the groundReport.properties file...attaching them to a reply would be >>> >> good >>> >> >>> >> This may well be a bug. >>> >> >>> >> Cheers >>> >> Cal >>> >> >>> >> On 6 April 2011 18:47, Ouray Viney <ou...@vi...> wrote: >>> >> > Hi All: >>> >> > Running with GroundReports 1.5. Have successfully uploaded my >>> >> > Grinder3 >>> >> > data >>> >> > to the PostgreSQL DB. When I attempt to run the >>> >> > ./generateReport.bash >>> >> > script with the desired data dir, I get the following error: >>> >> > Traceback (most recent call last): >>> >> > File >>> >> > >>> >> > >>> >> > "/opt/home/grinder/grinder_artifacts/ground_report-1.5/lib/groundReport.py", >>> >> > line 278, in <module> >>> >> > c.execute('SELECT e."Load Run", count(e."Test") AS "Count" FROM >>> >> > ONLY >>> >> > "page_summary_%s_mv" e WHERE e."Load Run" = %s AND e."Test" = %s >>> >> > GROUP >>> >> > BY >>> >> > e."Load Run";' % (str(dataType),str(loadRun),str(p))) >>> >> > zxJDBC.Error: ERROR: relation "page_summary_norm_mv" does not exist >>> >> > [SQLCode: 0], [SQLState: 42P01] >>> >> > + cd /opt/home/grinder/grinder_artifacts/ground_report-1.5/bin >>> >> > When I look at the database, I don't actually see the table. I have >>> >> > used >>> >> > the databaseInterface.bash script several times to recreate the >>> >> > database, >>> >> > but not luck. That particular table is never there. >>> >> > Clearly I am missing something. >>> >> > Any ideas? >>> >> > >>> >> > >>> >> > ------------------------------------------------------------------------------ >>> >> > Xperia(TM) PLAY >>> >> > It's a major breakthrough. An authentic gaming >>> >> > smartphone on the nation's most reliable network. >>> >> > And it wants your games. >>> >> > http://p.sf.net/sfu/verizon-sfdev >>> >> > _______________________________________________ >>> >> > Ground-user mailing list >>> >> > Gro...@li... >>> >> > https://lists.sourceforge.net/lists/listinfo/ground-user >>> >> > >>> >> > >>> > >>> > >>> > >>> > -- >>> > Ouray Viney >>> > http://www.viney.ca >>> > >> >> >> >> -- >> Ouray Viney >> http://www.viney.ca > > > > -- > Ouray Viney > http://www.viney.ca > |