Shell Programming and Scripting

Consider reinstall MIME::Base64. This module is actually written in C, and it seems like the error is suggesting that there is a version mismatch between the Perl side of the module, and the object side of the module (i.e. the C XS implementation).

If you google, you should find something similar, like this:
More on "IO object version does not match bootstrap parameter" error

Take a look at Dave's response.

A couple of things to consider.

First, the ~/.profile is not the only file sourced during an interactive login. Depending on the shell there are also files located in /etc/ that are sourced. So, you may still not have the entire environment.

Second, you really don't need the entire profile, but finding exactly what you do need may be a problem. Remember cron is not using a 'login' environment, so somethings may even be skipped when spawning a shell. I would start with setting a secure PATH or even hard-coding the full paths in your shell wrapper. You can add a call to 'env' at the top of your wrapper and redirect the output to a file. Then when you run it manually and via cron, you can see the differences in the environment. You obviously found that the perl binary was not in your path.

Since the module you mention is C based, there is a good chance that a necessary library or binary dependency is not available in your environment when running via cron. You may need to add LD_LIBRARY_PATH or LD_RUN_PATH. You can execute perl with the '-V' option to see how the binary was compiled. This may give you a clue on what libraries and paths are needed. Another thing to look at is using 'ldd' against any binaries to see their library dependencies.

I hope this helps.

- B

@bwhitehd
I mentioned LD_LIBRARY_PATH in my .profile ,which executed in my launch.sh script. So
when running thru cron ,I am not supposed to miss anything.!
@cbkihong
Reinstall MIME::Base64 ,looks like a promising option.

~Thanks
Coolbhai