Web UI - All Day Route Report - Time Out?

haroon_rehman8 years ago

Hi Anton,

Great application. Works great. Simple and to the point.
I have encountered a strange behavior while trying to generate a report for all day. Its seems to be kind of time out like. The device is logging ever 10 seconds. short hourly reports are working fine. If i generate the report for few hours or hourly then it works fine. However on full day time period to keeps loading , loading icon keeps rotating. After this noting happens. Then if i try to configure the start and end date/time again the popup windows is malformed / corrupted, stuck in one corner of the window.I am attaching images for loading and then corrupted window at this link http://imgur.com/a/LnrSI . What can be the problem here?

haroon_rehman8 years ago

Hi,

One more thing, i'm using your latest 3.9 version. I used the chrome console to monitor for any exceptions. I dont get any exception or errors for small time perionds. For long time periods like e.g. 24 HRS i get the following exception (log below)

Uncaught TypeError: Cannot read property 'length' of null
    at g.addReportMarkers (app.min.js:206)
    at g.loadReport (app.min.js:204)
    at F.fire (ext-all.js:22)
    at F.dispatch (ext-all.js:22)
    at g.a.doFireEvent (ext-all.js:22)
    at g.fireEventArgs (ext-all.js:22)
    at g.fireEvent (ext-all.js:22)
    at g.onProxyLoad (ext-all.js:22)
    at F.triggerCallbacks (ext-all.js:22)
    at F.setCompleted (ext-all.js:22)
addReportMarkers @ app.min.js:206
loadReport @ app.min.js:204
fire @ ext-all.js:22
dispatch @ ext-all.js:22
a.doFireEvent @ ext-all.js:22
fireEventArgs @ ext-all.js:22
fireEvent @ ext-all.js:22
onProxyLoad @ ext-all.js:22
triggerCallbacks @ ext-all.js:22
setCompleted @ ext-all.js:22
setException @ ext-all.js:22
setException @ ext-all.js:22
processResponse @ ext-all.js:22
(anonymous) @ ext-all.js:22
callback @ ext-all.js:22
onComplete @ ext-all.js:22
abort @ ext-all.js:22
onTimeout @ ext-all.js:22
(anonymous) @ ext-all.js:22
(anonymous) @ ext-all.js:22
haroon_rehman8 years ago

Another error message in console i noticed. Maybe its tied with the problem too

Bad Message 414
reason: Request-URI Too Long

http://MyServer/api/positions?_dc=1486159329111&id=25535&id=25725&id=26067&...&start=0&limit=25
Anton Tananaev8 years ago

It looks like it just takes too long to load the data, so it times out.

haroon_rehman8 years ago

Thanks a lot,

Is there a way i can increase the timeout period of report generation?

Also, i looked at Bad Message 414 - reason: Request-URI Too Long, it apperas in Apache webserver , it can be resolved by changing the configurable value "LimitRequestLine". Since traccar uses its own webserver is there any place where we can change this configuration as well?

Thanks in advance.

Anton Tananaev8 years ago

Request it likely timed out in the browser and not the server side, so you would have to configure your browser, if it's even possible.

As for the other problem, I would recommend to create a separate thread. I would also need to know when it happens.

haroon_rehman8 years ago

Agreed, will start separate thread if i see that problem again.

As for first problem, I will add the device in demo4 server today. and check after couple of hours how it performs. Somehow it seems more than just browser timeout. I will report back my results.

I also tried the same device logging data on one of your project forks by Vitaly Litvak and it works fine on large result set there.

P.S. sent an email @ sales, would be great if anyone can contact me.

haroon_rehman8 years ago

Hi,

I had the tracker device log data on to demo4 server and my own installation. I did not get any problems on generating 24HRs report on first attempt. This makes me think its an installation issue. Is demo4 server running on linux or windows?

Regards,
Haroon

Anton Tananaev8 years ago

It's running on Linux. I guess you have some problems with your server performance. What are the specs?

peteclyde8 years ago

Hey Haroon,

Sounds like an issue I had, the cause was low powered hardware (Raspberry Pi) that timed out after 30 seconds.

https://www.traccar.org/forums/topic/error-on-compiling-a-report-of-todays-route/#post-9399