[ZBX-7263] Errors in postgresql log due to bad syntax (invalid input syntax for integer: "1.3832467E9") Created: 2013 Oct 31 Updated: 2017 May 30 Resolved: 2013 Nov 08 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 2.0.8 |
Fix Version/s: | 2.2.1rc1, 2.3.0 |
Type: | Incident report | Priority: | Minor |
Reporter: | Dawid Mos | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | database, triggers | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Debian Wheezy (7.2) |
Attachments: |
![]() |
Description |
In postgresql log file every 15 minutes I get an error: |
Comments |
Comment by Eduards Samersovs (Inactive) [ 2013 Nov 01 ] |
Can you please provide additional information how to reproduce this problem? Do you use Zabbix Frontend or someone else client? If you use Zabbix Frontend may be you can see this error in some page? Which PHP version do you have? |
Comment by Dawid Mos [ 2013 Nov 01 ] |
I don't know how reproduce this problem. There is no messages during browsing frontend, only database log file. It doesn't look like result of clicking something in the frontend. There is always exactly 15 or 30 minutes between this log entries, like result of some scheduled task. I'm using Zabbix Frontend - zabbix-frontend-php from dotdeb repo (2.0.9-1~dotdeb.1) |
Comment by Eduards Samersovs (Inactive) [ 2013 Nov 01 ] |
(1) Require monitoring trigger filter limit for days field (2 years) Eduards RESOLVED r.39802 jelisejev The parameter shouldn't be marked as P_SYS, because then entering an incorrect value in the input will cause a fatal error. Eduards RESOLVED r.40113 jelisejev It must also be greater than 0, otherwise we will not show any results. Eduards RESOLVED r.40120 jelisejev CLOSED. |
Comment by Eduards Samersovs (Inactive) [ 2013 Nov 01 ] |
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7263 |
Comment by Eduards Samersovs (Inactive) [ 2013 Nov 04 ] |
Can you please test |
Comment by Dawid Mos [ 2013 Nov 04 ] |
Patch applied. |
Comment by Dawid Mos [ 2013 Nov 04 ] |
The second thing is that I've 2.0.8 frontend version, but your patch seems to be for 2.0.9. Maybe it's not important (patching was succesful). |
Comment by Eduards Samersovs (Inactive) [ 2013 Nov 06 ] |
Hm, seems this error is in-consequence call of API. May be You have some external scripts in CRON which call API? If so please check input value for field "lastChangeSince" it must be correct integer. |
Comment by Pavels Jelisejevs (Inactive) [ 2013 Nov 08 ] |
TESTED. |
Comment by Alexander Vladishev [ 2013 Nov 12 ] |
Fixed in pre-2.2.1 r40190 and pre-2.3.0 (trunk) r40191. |