Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Perl broken after Veritas Install
rwinterpacht
We recently installed Veritas Cluster on our development machines, to implement a failover architecture. After the install, however, none of our ipl files called from the WF as externaltasks work. Here's some output from our trace log:
Perl lib version (5.00404) doesn't match executable version (5.00503) at /opt/VR
TSvcs/lib/perl5/Config.pm line 7.
BEGIN failed--compilation aborted at /opt/VRTSvcs/lib/perl5/IO/Seekable.pm line
50.
BEGIN failed--compilation aborted at /opt/VRTSvcs/lib/perl5/IO/File.pm line 111.
BEGIN failed--compilation aborted at /opt/iw-home/iw-perl/lib/perl5/site_perl/5.
005/sun4-solaris/XML/Parser.pm line 12.
BEGIN failed--compilation aborted at /opt/iw-home/iw-perl/lib/perl5/site_perl/5.
005/TeamSite/WFtask.pm line 2.
BEGIN failed--compilation aborted at /iwmnt/default/main/TeamSiteAdmin/STAGING/i
w-home/custom/bin/ehouse_content_log.ipl line 38.
It looks as if the perl libs installed with Veritas have a version incompatability with TeamSite. Anyone have any thoughts on how to remedy this problem?
Thanks,
Raf
Raf Winterpacht
Household Intl/HSBC
TS 5.5.2 sp3
Find more posts tagged with
Comments
Adam Stoller
You shouldn't be mixing Perl libraries like that - chances are the veritas version of Perl is more recent (5.6? 5.8?) than TeamSite's ancient 5.005_03 version - and some of the modules are incompatible.
Check the perl that comes with Veritas (/opt/VRTSvcs/bin/perl -v ??)
Do you know what scripts are relying on the Veritas Perl library modules? - perhaps somewhere you're calling a script with something like "perl scriptname" - and "perl" is now coming from Veritas rather than IWHOME/iw-perl/bin because the PATH environment changed?
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
rwinterpacht
I think it's the other way around...Veritas probably installed an even older version of PERL, but it didn't install any perl exe's, just lib files, from what I can tell. Notice the error message:
Perl lib version (5.00404) doesn't match executable version (5.00503) at /opt/VR
TSvcs/lib/perl5/Config.pm line 7
I think I can get around this by including the interpreter along with calling the ipl:
IWHOME/iw-perl/bin/iwperl perl_pgm
Lots of places to update this, and it's more a workaround than a solution...
Raf Winterpacht
Household Intl/HSBC
TS 5.5.2 sp3
Adam Stoller
If all your Perl scripts start with
#!/path/to/iw-home/iw-perl/bin/iwperl
you shouldn't have to explicitly specify the perl interpreter on the command line for these scripts (assuming that the scripts are executable too)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
mmb
We suffered this exact same problem. Its because teamSite's iwperl and Vertias Perl both have a module called Config.pm. Bascially the unix environment variable PERL5LIB is pointing at Vertias's library path instead of teamSite's. As the iwserver process is ran as root, set and export PERL5LIB="/iw/iw-home/iw-perl/lib/perl5" in roots .profile (/.profile). Restart teamsite as root. When this is done, it should pick up the correct environment variable and access the correct Config.pm. Hope this helps - mark
rwinterpacht
We tried this, to no avail. We also tried putting the interpreter in so it explicitly calls /opt/iw-home/iw-perl/bin/iwperl.
Any other ideas? Are you running Veritas Cluster with two TeamSite machines? Which versions are you on?
We're running on Solaris 8, TS 5.5.2 sp3, and Veritas Volume Manager 3.5 and Veritas Cluster 3.5 with SP2.
Raf Winterpacht
Household Intl/HSBC
TS 5.5.2 sp3
mmb
yep we're running TS5.5.2 sp2 on solaris 6 over 2 boxes, managed by VCS.
Surprised that the fix didnt work. As a final (hack) fix you could comment out the line in the VCS Config.pm that checks the version number!!
sorry I cant be of more help
- mark