We have Google analytics configured for OOD for centos 7, and it stopped working for the OOD on Centos 8 (No GA entries when someone is accessing the OOD website). We used the same OOD deployment procedure and configuration files, and we could not find which part went wrong.
I checked on the OOD server, the ood_portal.yml and ood-portal.conf file shows exactly as in 1. Adding Google Analytics — Open OnDemand 2.0.13 documentation
I also tried update_ood_portal, restarting httpd and htcacheclean, and the GA still not work.
The file /opt/ood/mod_ood_proxy/lib/analytics.lua exist with correct permission.
We have the following packages installed.
httpd-devel-2.4.37-21.module_el8.2.0+494+1df74eae.x86_64
httpd-tools-2.4.37-21.module_el8.2.0+494+1df74eae.x86_64
httpd-2.4.37-21.module_el8.2.0+494+1df74eae.x86_64
httpd-filesystem-2.4.37-21.module_el8.2.0+494+1df74eae.noarch
I worked with the Google Analytics team and confirmed that it can collect data on a test website.
So it is more likely the error is on the OOD part. I would like some help in debugging and find where it goes wrong.
Looks like we’re using wget to send off the data right the on the web node.
You can turn lua log level to debug and see what the response is. I’m guessing that you either have some connectivity issue or you simply don’t have wget.
However, when I search for “Analytics input:” or “Analytics output” I could not find any. I am accessing the website at the meantime. Does this mean the Analytics.lua is not triggered at all?
Thanks!
In the error log, we also have entry that exist for a long time:
[Wed Dec 01 13:15:26.084263 2021] [lua:warn] [pid 440226:tid 140497867548416] AH01471: Lua error: /opt/ood/mod_ood_proxy/lib/logger.lua:22: bad argument #2 to ‘date’ (number has no integer representation)
I’m looking to release 2.0.20 today, it has a bugfix for the lua warning you’re seeing. But I feel like you’d see that on the other system? In any case - that may solve this though I’m skeptical.
Indeed - what’s changed here? The httpd version. Maybe the newer version really doesn’t like that warning?