Issue with Grabbit (grabbit-3.0.5) installation

[jbornemann]

Hi @ani91 !

Sorry you are having issues! A couple of things :

• Double-check the path "/CQt5/author/crx-quickstart/Grabbit/grabbit-3.0.5/config.json." grabbit.sh is expecting an absolute path to a configuration file. e.g on Linux : /data/apps/cq5/myconfig.json
• You mentioned you uploaded the protobuf compiler to your Linux servers. It sounds like you are building from source? Note that the protobuf compiler is only required at compile-time. Did everything get installed to your CQ5 servers as expected?
• Aside from the configuration not being uploaded, I see that you received a 409 Conflict response. Check to make sure you can reach the target server, and that Grabbit is running by checking "http://t5-author.fcc.ca:4502/grabbit/job/all.json"

If none of these points help, could you provide a the version of CQ/AEM you are running?

[jbornemann]

Also, note that exclude paths are relative. For e.g, path: "apps/onlinePresence/i18n", excludePaths: ["fr"]

[jbornemann]

Hmm, okay. From your original post, one issue is that for some reason grabbit.sh (which is really just a wrapper around cURL) can't find, and/or access your "config.json." Make sure you have appropriate read permissions using stat, or ls -l; You may try toying around with curl -X GET --data-binary "@" --verbose to debug the issue. Another issue may be that Grabbit isn't installed, based on your screenshot above.

To make things a little bit easier - I noticed that we didn't provide a built version of 3.0.5; I've uploaded the built AEM package to https://github.com/TWCable/grabbit/releases/download/v3.0.5/grabbit-3.0.5.zip

The protobuf compiler is only required if you are building Grabbit from source.

• Try downloading the built software from the link above and installing it to both source, and destination servers via the Package Manager.
• After you've done that, check to make sure all your bundles are in the "Started" state via /system/console on both servers
• If your bundles are good, try /grabbit/jobs/all.json again on both servers. For a fresh install, you should see a response of "[]"
• If you see the "[]", try running ./grabbit.sh with your configuration again. If you still run into issues, if you would attach your client log from the source server "/logs/batch-client.log", and your server log from the destination server "/logs/batch-server.log"; this will help.

[jbornemann]

Also, this may be unclear in the documentation (which we should fix), but the path to the configuration that grabbit.sh asks for is an absolute path on the machine you are running grabbit.sh not an absolute path on the machine the Grabbit client is running - although of course, the machine may be the same.

[jdigger]

@ani91 Did @jbornemann's clarifications help?

[jbornemann]

@ani91 are all the bundles (including Grabbit) in a "Started" state? If you ssh into the box you are playing with above, does curl -u : localhost:4502/grabbit/job/all.json return '[]', with SC_OK?

You can't find the batch-client.log, or batch-server.log? Is Grabbit printing any messages to your error.log on start up?

[jbornemann]

Hey @ani91 did you get this resolved?