install script fails

[BardiaAfshin]

running the install script creates the configuration file , but fails to validate a logged message

here's the output

[ec2-user@ip-172-31-14-149 ~]$ sudo bash configure-file-monitoring.sh -a PRIVATE -u PRIVATE -p SECRET -f /var/www/email-microservice/storage/logs/ -l laravel-log-directory
INFO: Downloading dependencies - configure-linux.sh
Loggly account or subdomain: x
Username is set
Directory to monitor: /var/www/email-microservice/storage/logs
File alias: laravel-log-directory
INFO: Initiating configure Loggly for file monitoring.
INFO: Operating system is Amazon AMI.
INFO: Checking if logs-01.loggly.com is reachable.
INFO: logs-01.loggly.com is reachable.
INFO: Checking if logs-01.loggly.com is reachable via 514 port. This may take some time.
INFO: logs-01.loggly.com is reachable via 514 port.
INFO: Checking if 'x' subdomain is valid.
INFO: https://x.loggly.com is valid and reachable.
INFO: Checking if Gen2 account.
INFO: It is a Gen2 account.
INFO: Checking if provided username and password is correct.
INFO: Username and password authorized successfully.
INFO: Authentication token not provided. Trying to retrieve it from https://x.loggly.com account.
INFO: Retrieved authentication token: 5a3a7753-addc-45bd-a4b2-869364a77228
INFO: Checking if provided auth token is correct.
INFO: Authentication token validated successfully.
INFO: rsyslog is present as service.
INFO: selinux status is not enforced.
INFO: There are 0 files in directory. Configuring each file for monitoring present in this directory.
There are 0 files present in this directory. Would you like to configure all the files (yes/no)?yes
INFO: Initiating Configure Loggly for Linux.
INFO: Loggly rsyslog file /etc/rsyslog.d/22-loggly.conf already exist.
INFO: Restarting the rsyslog service.
Shutting down system logger:                               [  OK  ]
Starting system logger:                                    [  OK  ]
INFO: /var/spool/rsyslog already exist, so not creating directory.
Would you like install a Cron job to sync the files currently in your Directory every 5 minutes? (yes/no)
Please answer yes or no.
Would you like install a Cron job to sync the files currently in your Directory every 5 minutes? (yes/no)yes
INFO: Creating cron script /root/.loggly/file-monitoring-cron-laravel-log-directory.sh
INFO: Restarting the rsyslog service.
Shutting down system logger:                               [  OK  ]
Starting system logger:                                    [  OK  ]
INFO: Search URL: https://x.loggly.com/apiv2/search?q=syslog.appName%3Alaravel-log-directory&from=-15m&until=now&size=1
INFO: Getting initial log count.
INFO: Verifying if the logs made it to Loggly.
INFO: Verification # 1 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 2 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 3 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 4 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 5 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 6 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 7 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 8 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 9 of total 10.
INFO: Did not find the test log message in Loggly's search yet. Waiting for 30 secs.
INFO: Done waiting. Verifying again.
INFO: Verification # 10 of total 10.
ERROR: File logs did not make to Loggly in time. Please check network and firewall settings and retry.
Manual instructions to configure a file is available at https://www.loggly.com/docs/file-monitoring/. Rsyslog troubleshooting instructions are available at https://www.loggly.com/docs/troubleshooting-rsyslog/

[varshneyjayant]

@BardiaAfshin could you try the version hosted at https://www.loggly.com/install/configure-linux.sh?

[DannyCork]

I've the same problem. Running on Centos. Syslog works fine, it's apache logs that don't work.

I'm running the curl -O https://www.loggly.com/install/configure-apache.sh , hosted script

[ernestom]

I'm experiencing the same problem with the latest configure-nginx.sh and configure-file-monitoring.sh on Ubuntu.
Syslog works fine though, and sudo tcpdump -A dst logs-01.loggly.com shows data being sent.

[niclashedam]

Still an issue ..

[mostlyjason]

Hey guys I'm not sure if this is an issue with the script because most customers are able to run it successfully. It might be something different about your particular system or a transient system issue. Also, there might not be a single issue that all of you face, it might be a collection of issues. One example could be indexing delays inside Loggly. I'm afraid there's not really enough information provided in this chain to determine the problem. I think it would probably be better for you to open support tickets and then we can address each individually and update the script as needed.

[benmullin333]

I ran into this problem and was able to solve it by changing the alias. Apparently, duplication on that screws with loggly.

[mostlyjason]

Thanks @benmullin333 we might want to add a uniqueness check

[itjunkii83]

@benmullin333 could you elaborate on how to change the alias?