search

CUTR-at-USF / onebusaway-application-modules

OneBusAway, modified for a Tampa, Fl deployment
https://github.com/OneBusAway/onebusaway-application-modules/wiki
Other
2 stars 1 forks source link

Configure GTFS-realtime Generator for better logging #17

Closed barbeau closed 10 years ago

barbeau commented 11 years ago

GTFS-realtime Generator application is currently kicked off by the Windows Task Scheduler on every server startup. However, because of this, there is no command-line interface that shows the application output.

We should try to configure the application so it outputs to a file instead of stdout , such as mentioned here, to be able to better troubleshoot issues: http://richarddingwall.name/2009/01/26/capture-the-output-from-a-scheduled-task/

barbeau commented 11 years ago

Khoa tested this line, and it works:

java -jar cutr-gtfs-realtime-hart-1.0.1-SNAPSHOT.jar --tripUpdatesUrl=http://localhost:8088/trip-updates --vehiclePositionsUrl=http://localhost:8088/vehicle-positions --tripUpdatesPath=C:\Test\tripUpdates.pb  --vehiclePositionsPath=C:\Test\vehiclePositions.pb --refreshInterval=20 >> C:\Test\err.log 2>> C:\Test\out.log

Now need to modify on server...

barbeau commented 11 years ago

I've modified the .bat file on the server to output to D:\GTFS-realtime_logs (D drive because we have a lot more disk space than C drive, because of below issue).

The only problem is that the log file size will continue to grow significantly due to the constant refresh of the GTFS-realtime feed every 5 seconds and the repeated append to the file.

We need to find a configuration for output that doesn't result in a constantly growing file (possibly outputting only error log, not normal output?).

barbeau commented 11 years ago

After ~2 days, output log file is around 30MB, and err log is 1.1MB (but only includes the occasional "SQL Exception ERROR at xxxxxx: Cannot get a value from a deleted row.", which the GTFS-realtime software seems to recover fine from).

So, we definitely need to either stop the standard output or fine a more efficient way of outputting it.

barbeau commented 10 years ago

Standard output was stopped on the GTFS-realtime feed, since this seemed to be causing performance issues. Since feed output was stopped, we have no longer had issues with the setup, so I'm closing this for now, until we have a need for better logging.