-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No logs when things aren't going right #3
Comments
First off, thanks for taking an interest in acilos! We appreciate the feedback. Which accounts have you authenticated and are trying to get data for? Have you authenticated the accounts to where you can log into the app, and under settings->manageAccounts->authAccounts you can see your accounts and have a valid token? Are you running from dist/app-production after having done a build? or are you running it from src? (it is recommended to run from /src/ as all of the console statements have been removed and the code minified in the build process. Has elasticsearch just started? sometimes ES can take a moment to get the ball rolling and have data entered into it. You can run the crons directly by putting in DOMAIN/src/cron/poller/clientManager.php and cronManager.php and see what errors get logged from there. Let me know if any of that helped |
I've connected it to a Facebook account and it is shown in the Facebook side and the acilos side, just no data is being downloaded. I am running it from dist/app-production, but I'll try it from src once I get another shot at it. I haven't seen any indication that ES is running; I'll double check. |
Wherever you run start.sh (either from dist/app-production or from src) is You can also run sudo crontab -l to see if the crons exist and what scripts Running the crons manually from /src/cron/poller/clientManager.php and On Wed, Jun 25, 2014 at 11:29 AM, Ben Boeckel [email protected]
|
I'm not seeing any data and I'm also not seeing any logs with errors as to what is going wrong. How can I get things to be more verbose?
The text was updated successfully, but these errors were encountered: