From: Dick C. <dca...@im...> - 2006-11-07 18:01:13
|
Hi Folks, Our production version of Mail Manager 2.0 on Windows server-2000; PostgreSQL 8.0.7 has been working OK until recently. When we attempt to do a "Search", delete & archive, or enter the "Reports" page, we get a programming error as follows: (from Zope ZMI error_log) ERROR: invalid input syntax for type timestamp with time zone: "2006/11/01 23:59:59 US/Eastern" SELECT COUNT(1) AS count FROM IOC.mm_ticket WHERE id IN (SELECT id FROM IOC. ) I can think of nothing we consciensly did to cause this? Have tried to delete the old instance and create a new one but I am sure that all I did was copy the problem into the new instance. Any ideas on how to cure this?? Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 |
From: Chris D. <ch...@20...> - 2006-11-07 18:58:52
|
You said you can't think of anything that did this... Are you sure the timezone settings didn't change the computer that has either the database or the application? I ran into this problem on windows too once, it was a long time ago during a new install... I ended up fixing the code in some way, but I bet there is better way to fix this, such as setting the system timezone differently. I would try setting the system timezone to the same as Edinburgh, Scotland, just to see what happens. I am also wondering if upgrading to the latest version of 2.0 would fix it. What version are you using exactly? If no one else has a better idea, I am willing to provide a snapshot of our code. Although I am not sure we fixed the specific error you cite below. Let me know if you want it... Good Luck! -Chris -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of Dick Calhoun Sent: Tuesday, November 07, 2006 10:01 AM To: Logicalware Mailmanager-users Subject: [Mailmanager-users] MM 2.0 Error - Invalid input syntax for type timestamp with time zone Hi Folks, Our production version of Mail Manager 2.0 on Windows server-2000; PostgreSQL 8.0.7 has been working OK until recently. When we attempt to do a "Search", delete & archive, or enter the "Reports" page, we get a programming error as follows: (from Zope ZMI error_log) ERROR: invalid input syntax for type timestamp with time zone: "2006/11/01 23:59:59 US/Eastern" SELECT COUNT(1) AS count FROM IOC.mm_ticket WHERE id IN (SELECT id FROM IOC. ) I can think of nothing we consciensly did to cause this? Have tried to delete the old instance and create a new one but I am sure that all I did was copy the problem into the new instance. Any ideas on how to cure this?? Dick Calhoun InterMedi@ Marketing Solutions Ofc. Ph: 610-701-9654 ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
From: Timothy A. K. <tk...@im...> - 2006-11-13 17:54:08
|
Hi Dick, It's Tim. I don't know what is causing your problem, but from the information you gave, it looks like your sql query is not complete. Look in the subquery "(SELECT id FROM IOC. )" after the "IOC.", I believe there should be some table name which the "id" data should be selected from. If this is the problem, then the subquery is not being built correctly. --Tim Dick Calhoun wrote: > Hi Folks, > Our production version of Mail Manager 2.0 on Windows server-2000; PostgreSQL 8.0.7 has been working OK until recently. When we attempt to do a "Search", delete & archive, or enter the "Reports" page, we get a programming error as follows: (from Zope ZMI error_log) > > ERROR: invalid input syntax for type timestamp with time zone: "2006/11/01 23:59:59 US/Eastern" SELECT COUNT(1) AS count FROM IOC.mm_ticket WHERE id IN (SELECT id FROM IOC. ) > > I can think of nothing we consciensly did to cause this? Have tried to delete the old instance and create a new one but I am sure that all I did was copy the problem into the new instance. > > Any ideas on how to cure this?? > > Dick Calhoun > InterMedi@ Marketing Solutions > Ofc. Ph: 610-701-9654 > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Mailmanager-users mailing list > Mai...@li... > https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
From: S.J.Stanaitis <sst...@dp...> - 2006-11-20 15:52:41
|
I tend to hit some performance bumps in MM 2.0.9 when the number of tickets gets as obscenely high as ours. Regular purges of tickets older than 6 months to 1 year tend to fix it up... Doing this through the interface even for a small number of tickets takes a significant amount of time though. Is there a PSQL statement I can run to dump tickets older than a certain date without messing it all up? I've found working directly in the database works much faster. Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network |
From: S.J.Stanaitis <sst...@dp...> - 2006-11-21 02:26:04
|
I took a look at the deleteTickets.zsql file and determined how to delete the tickets manually from PostgreSQL... Just takes a bit of time. In the interim (until I can commit the DELETE's after hours) I will simply redirect the tickets to an alternate User, which seems to resolve the hang-ups when a user with 15000+ tickets logs on. UPDATE public.mm_ticket SET assigned = 'dump' WHERE date_opened LIKE '2004-%'; That redirects all tickets from 2004 to the dump user, taking the load off the other accounts. Once all is said and done, then I'll use the following command: DELETE FROM mm_ticket WHERE assigned = 'dump'; Easy enough... If this has the possibility of hosing the whole thing, be a pal and let me know! :) Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of S.J.Stanaitis Sent: Monday, November 20, 2006 10:52 AM To: 'Logicalware Mailmanager-users' Subject: [Mailmanager-users] Quick way to dump tickets? I tend to hit some performance bumps in MM 2.0.9 when the number of tickets gets as obscenely high as ours. Regular purges of tickets older than 6 months to 1 year tend to fix it up... Doing this through the interface even for a small number of tickets takes a significant amount of time though. Is there a PSQL statement I can run to dump tickets older than a certain date without messing it all up? I've found working directly in the database works much faster. Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
From: S.J.Stanaitis <sst...@dp...> - 2006-12-04 18:16:36
|
Zope Error Zope has encountered an error while publishing this resource. Error Type: KeyError Error Value: 1165256100 Troubleshooting Suggestions * This resource may be trying to reference a nonexistent object or variable 1165256100. * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the HTML source for this page. If the error persists please contact the site maintainer. Thank you for your patience. Any ideas? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network |
From: S.J.Stanaitis <sst...@dp...> - 2006-12-04 18:18:39
|
2006-12-04T13:17:03 ERROR Zope.SiteErrorLog http://mailmanager:8080/mm/setSession Traceback (most recent call last): File "/usr/local/zope/lib/python/ZPublisher/Publish.py", line 113, in publish request, bind=1) File "/usr/local/zope/lib/python/ZPublisher/mapply.py", line 81, in mapply v=get(name, args) File "/usr/local/zope/lib/python/ZPublisher/HTTPRequest.py", line 1177, in get if callable(v): v = v() File "/usr/local/zope/lib/python/Products/Sessions/SessionDataManager.py", line 93, in getSessionData return self._getSessionDataObject(key) File "/usr/local/zope/lib/python/Products/Sessions/SessionDataManager.py", line 180, in _getSessionDataObject ob = container.new_or_existing(key) File "/usr/local/zope/lib/python/Products/Transience/Transience.py", line 846, in new_or_existing self[key] = item File "/usr/local/zope/lib/python/Products/Transience/Transience.py", line 449, in __setitem__ current_bucket = self._data[current_ts] KeyError: 1165256220 Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of S.J.Stanaitis Sent: Monday, December 04, 2006 1:16 PM To: sst...@dp...; 'Logicalware Mailmanager-users' Cc: 'Kevin Campbell' Subject: [Mailmanager-users] Logged in to MailManager 2.0.9 today and... Zope Error Zope has encountered an error while publishing this resource. Error Type: KeyError Error Value: 1165256100 Troubleshooting Suggestions * This resource may be trying to reference a nonexistent object or variable 1165256100. * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the HTML source for this page. If the error persists please contact the site maintainer. Thank you for your patience. Any ideas? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
From: S.J.Stanaitis <sst...@dp...> - 2006-12-04 18:25:52
|
Someone changed the time on the box, restarted Zope and all is well. Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of S.J.Stanaitis Sent: Monday, December 04, 2006 1:18 PM To: sst...@dp...; 'Logicalware Mailmanager-users' Cc: 'Kevin Campbell' Subject: Re: [Mailmanager-users] Logged in to MailManager 2.0.9 today and... 2006-12-04T13:17:03 ERROR Zope.SiteErrorLog http://mailmanager:8080/mm/setSession Traceback (most recent call last): File "/usr/local/zope/lib/python/ZPublisher/Publish.py", line 113, in publish request, bind=1) File "/usr/local/zope/lib/python/ZPublisher/mapply.py", line 81, in mapply v=get(name, args) File "/usr/local/zope/lib/python/ZPublisher/HTTPRequest.py", line 1177, in get if callable(v): v = v() File "/usr/local/zope/lib/python/Products/Sessions/SessionDataManager.py", line 93, in getSessionData return self._getSessionDataObject(key) File "/usr/local/zope/lib/python/Products/Sessions/SessionDataManager.py", line 180, in _getSessionDataObject ob = container.new_or_existing(key) File "/usr/local/zope/lib/python/Products/Transience/Transience.py", line 846, in new_or_existing self[key] = item File "/usr/local/zope/lib/python/Products/Transience/Transience.py", line 449, in __setitem__ current_bucket = self._data[current_ts] KeyError: 1165256220 Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network -----Original Message----- From: mai...@li... [mailto:mai...@li...] On Behalf Of S.J.Stanaitis Sent: Monday, December 04, 2006 1:16 PM To: sst...@dp...; 'Logicalware Mailmanager-users' Cc: 'Kevin Campbell' Subject: [Mailmanager-users] Logged in to MailManager 2.0.9 today and... Zope Error Zope has encountered an error while publishing this resource. Error Type: KeyError Error Value: 1165256100 Troubleshooting Suggestions * This resource may be trying to reference a nonexistent object or variable 1165256100. * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the HTML source for this page. If the error persists please contact the site maintainer. Thank you for your patience. Any ideas? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mailmanager-users mailing list Mai...@li... https://lists.sourceforge.net/lists/listinfo/mailmanager-users |
From: S.J.Stanaitis <sst...@dp...> - 2006-12-13 15:58:19
|
No problems since I did the big purge of old tickets in MailManager, right now however the Reports seem to take a long time to even access the menu... sometimes getting a Zope error... Any ideas to speed it up? Thanks, Sam SJ.Stanaitis - Network Administrator Decorative Product Source E-commerce Network (877)-650-8054 x160 sst...@dp... |
From: S.J.Stanaitis <sst...@dp...> - 2006-12-28 20:12:02
|
Anyone home? Have we all gone on Holiday? Sam |
From: Kevin C. <ke...@lo...> - 2007-01-02 12:48:36
|
On Wed, Dec 13, 2006 at 10:57:58AM -0500, S.J.Stanaitis wrote: > No problems since I did the big purge of old tickets in MailManager, right > now however the Reports seem to take a long time to even access the menu... > sometimes getting a Zope error... Any ideas to speed it up? Sam, What version of MailManager are you running and what database backend? There are quite a lot of changes to reporting in the 2.1 branch to deal with large datasets. The solution may be to upgrade. Regards, Kevin |
From: Kevin C. <ke...@lo...> - 2007-01-02 13:00:04
|
On Tue, Jan 02, 2007 at 12:47:47PM +0000, Kevin Campbell wrote: > On Wed, Dec 13, 2006 at 10:57:58AM -0500, S.J.Stanaitis wrote: > > No problems since I did the big purge of old tickets in MailManager, right > > now however the Reports seem to take a long time to even access the menu... > > sometimes getting a Zope error... Any ideas to speed it up? > > Sam, > > What version of MailManager are you running and what database backend? > There are quite a lot of changes to reporting in the 2.1 branch to deal > with large datasets. The solution may be to upgrade. Sam, Sorry, just noticed the subject line. There are a couple of things you can do here: a) run a full vacuum on the database, which should improve performance b) Turn on postgres command string debugging (log_statement = 'all') so that you can use select * from pg_stat_activity to see what running statements are slowing the process c) upgrade to 2.1, which should use caches for daily and snapshot reports, rebuilt nightly. Regards, Kevin |