Closed dnburgess closed 2 years ago
Thanks for the feedback. Can you provide a sample log file? Not an entire one just a few lines to make sure the format looks correct.
There is a new docker image available, please pull the latest. Added some logging/debugging for the files being retrieved for parsing. It should tell which files are accessible to be read. If there is an issue with permissions can you try adding the correct UID and GID to the docker-compose.yml file; example below.
For example Checking active logs... Filename: /opt/log/proxy-host-6_access.log | Read = yes Filename: /opt/log/proxy-host-24_access.log | Read = yes Filename: /opt/log/proxy-host-9_access.log | Read = yes Filename: /opt/log/proxy-host-10_access.log | Read = yes Filename: /opt/log/proxy-host-14_access.log | Read = yes Filename: /opt/log/proxy-host-17_access.log | Read = yes Filename: /opt/log/proxy-host-21_access.log | Read = yes Filename: /opt/log/proxy-host-18_access.log | Read = yes Filename: /opt/log/proxy-host-16_access.log | Read = yes Filename: /opt/log/proxy-host-25_access.log | Read = yes Filename: /opt/log/proxy-host-15_access.log | Read = yes Filename: /opt/log/proxy-host-19_access.log | Read = yes Filename: /opt/log/proxy-host-4_access.log | Read = yes Filename: /opt/log/proxy-host-5_access.log | Read = yes Filename: /opt/log/proxy-host-1_access.log | Read = yes Filename: /opt/log/proxy-host-12_access.log | Read = yes Filename: /opt/log/proxy-host-11_access.log | Read = yes Filename: /opt/log/proxy-host-20_access.log | Read = yes Filename: /opt/log/proxy-host-23_access.log | Read = yes Filename: /opt/log/proxy-host-2_access.log | Read = yes Filename: /opt/log/proxy-host-8_access.log | Read = yes Filename: /opt/log/proxy-host-7_access.log | Read = yes Filename: /opt/log/proxy-host-13_access.log | Read = yes Filename: /opt/log/proxy-host-22_access.log | Read = yes Filename: /opt/log/proxy-host-3_access.log | Read = yes [PARSING /opt/log/proxy-host-22_access.log] {224} @ {6/s}}9/s} WebSocket server ready to accept new client connections
docker-compose.yml.example
goaccess: image: xavierh/goaccess-for-nginxproxymanager:develop container_name: goaccess restart: always volumes:
Apologies for the delyed response. I didn't get a notification for some reason.
After pulling the newest image and redeploying, things seem to be working well. I've got another question, but, well, it's another question, so I'll close this issue and start a new one.
Spun this up this morning with no success.
My Nginx Proxy Manager logs are located at /home/data/logs
My docker-compose looks like this: https://pastebin.com/t6x0fjZE
After a few minutes, my logs look like this: https://pastebin.com/L51NAbdb
After a few more minutes, I see just more of the same.
I should mention that my logs go as high as 'proxy-host-38_error.log'
The container will not start.