SID-01141: Can't call method "run" on an undefined value Error in View
| Status: |
Answered |
TWiki version: |
5.0.1 |
Perl version: |
5.008008 |
| Category: |
CategoryInstallation |
Server OS: |
Linux 2.6.18-53.1.14.el5pae (i386-linux-thread-multi) |
Last update: |
14 years ago |
Little Background:
I am new to Perl as well as Twiki. My client had already installed and done basic setup of Twiki 4.3.2 last year. But he wanted me to install the latest version and do more than the basic setup now. So in the same server, I installed (instead of upgrading the old version) Twiki 5.0.1 but under a different directory. Here is the URL:
http://sindhu.ece.iisc.ernet.in/nanofab/twikii/
The problem:
I am able to install and configure twiki. There are no error or warning messages in the configure page. But here the two problems I am facing right now:
1. When I click on "Test PATH_INFO", it shows the new PATH_INFO as /foo/configure instead of /foo/bar.
2. When I try to view the
WebHome (
http://sindhu.ece.iisc.ernet.in/nanofab/twikii/bin/view/Main/WebHome
) it shows a Software Error:
Can't call method "run" on an undefined value at /var/www/html/nanofab/twikii/bin/view line 43.
at /var/www/html/nanofab/twikii/bin/view line 43
ModPerl::ROOT::ModPerl::Registry::var_www_html_nanofab_twikii_bin_view::handler('Apache2::RequestRec=SCALAR(0x94e946c)') called at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x932783c)') called at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x932783c)') called at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x94e946c)') called at -e line 0
eval {...} called at -e line 0
Since I am new to Perl as well Twiki, I am not sure whats going wrong here. Is it because of the two twiki versions running on the same server (although they are in different folder)? or Is it because of some required CPAN modules (I guess configure should be able to pin point that)? I am not able to figure this out.
Can you anybody help me with this please?
Many thanks in advance
--
RajeevMiglani - 2011-03-31
Discussion and Answer
Without looking into details I do not need/want to run TWiki under mod_perl unless you have thousands of users. Use the
ApacheConfigGenerator.
--
PeterThoeny - 2011-03-31
Thanks Peter. Disabling mod_perl did the trick.
But I am just wondering if the older Twiki version 4.3.2 is working with mod_perl on the same server, why the new version doesn't work. That was the reason I kept mod_perl enabled. The mod_perl_startup.pl file was not originally there in the Twiki version which I downloaded. So I copied it from the older version (4.3.2) which was already installed and running on the client server. I did make changes to $binurlbase and $binbase as well in mod_perl_startup.pl file.
Can you please advise on what went wrong under mod_perl enabled?
--
RajeevMiglani - 2011-04-01
Try the mod_perl_startup.pl script generated by
ApacheConfigGenerator.
--
PeterThoeny - 2011-04-01
I used the mod_perl_startup.pl script generated by
ApacheConfigGenerator. But it starts giving the same error message again.
--
RajeevMiglani - 2011-04-02
I do not have the bandwidth to debug this. TWiki is an open source project where people take and contribute back. I invite you to
get involved and help debug and fix issues you find.
--
PeterThoeny - 2011-04-02
Closing this question after more than 30 days of inactivity. Feel free to reopen if needed. Consider engaging one of the
TWiki consultants if you need timely help. We invite you to
get involved with the community, it is more likely you get community support if you support the open source project!
--
PeterThoeny - 2011-06-16
I had the same error... and restarting the Apache server sorted out the problem for me !!
--
RajeshN - 2011-10-19
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.