For some reason the current working directory wasn't being set to the location where the script is running. It was manifested by the "can't load module ...", "can't call method XYC" ... Templates, config files .... whatever ... everything was coded with relative paths.

Simplest solution was to set the CWD with :
cwd '/full/path/here';

Does anyone know what went wrong - so that CWD isn't automaticly set to location where the script is located?

Likely taint mode was switched on because you're running with setuid or setgid. You probably do not want the current directory to be in @INC if that's the case.

Forget that. Anyway, normal scripts never have cwd set to the location of the script. Apache does it for CGI scripts but you should probably not rely on that. See FindBin.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Wow - I guess you learn something new each day.

Beside being able to swear that I read somewhere that cwd is automaticly set to location where script is running. I never had an problem with that in the past ~ 5 years of working with Perl.

Here is the source Changing the Working Directory which I found out yesterday - but I got it from other places in the past ...

EDIT:

During development and testing I used -T option. First thought was that it's the thing causing the problem on the server - obviosly it isn't.

---

Have you tried freelancing? Check out Scriptlance - I work there. For more info about Scriptlance and freelancing in general check out my home node.