#*** starts checking at the beginning of time, since it found no registry file: *** T14:32:30.536-0500 WARN beater/o365beat.go:390 error parsing registry file, may not exist. # *** with that misleading error message you pointed out we expect it when running the first time: *** T14:32:29.988-0500ĝEBUG beater/o365beat.go:111 issuing api request: $O365_DIRECTORY_ID/activity/feed/subscriptions/list?PublisherIdentifier=$O365_DIRECTORY_ID # *** this can take time, and it's an issue that i don't check for it here: *** # *** after first auth, it checks your content subscriptions, and subscribes you if they're disabled *** T14:32:29.524-0500ĝEBUG beater/o365beat.go:157 getting content subscriptions from $O365_DIRECTORY_ID/activity/feed/subscriptions/list ![]() T14:32:29.524-0500ĝEBUG service/service_windows.go:72 Windows is interactive: true I see the following abridged output: # /snip/ ![]() ![]() c o365beat.yml -e -d "*" -strict.perms=false *> debug.log When I run it (on Windows in this case), using the following command in powershell. I'll post an example of what I see, with that stuff redacted, perhaps that'll help find the exact spot things are failing for you: Happy to help! Those 400 errors can come from a number of steps in the process, and some of the debug output does have sensitive-ish info in it.
0 Comments
Leave a Reply. |