reverse_proxy.
Amiri
amiribarksdale wrote:
>
> I was just grappling with this problem last week, and after trying out
> lighttpd, nginx, and varnish, I chose varnish.
>
> I too run one single mod-perl server, but it's sort of complicated, with
> file uploads and customizable p
I was just grappling with this problem last week, and after trying out
lighttpd, nginx, and varnish, I chose varnish.
I too run one single mod-perl server, but it's sort of complicated, with
file uploads and customizable pages and stuff. I found that neither lighttpd
or nginx really allowed me to
Fred Moyer wrote:
>
> What version were you using that was causing the problems?
>
4.007.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17675687.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
It appears that downgrading DBD::mysql to version 4.004 has done the trick.
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17668030.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
Fred Moyer wrote:
>
> Can you post your httpd.conf and startup.pl?
>
> Are you using transactions?
>
I am not using transactions--I don't have any InnoDB tables, either.
Here is my httpd.conf:
ServerType standalone
ServerRoot "/usr/local/apache"
PidFile /usr/local/apache/logs/httpd.pid
Sco
Yes, I have the debug output on 2 already. It doesn't say much else than what
I posted.
Amiri
Fred Moyer wrote:
>
> amiribarksdale wrote:
>> No, they're not the same, because they cannot be the same any longer. In
>> the
>> server migration, I had to
No, they're not the same, because they cannot be the same any longer. In the
server migration, I had to recompile and reinstall everything, because of
those 32-bit and 64 bit errors. I just built everything back up from
barebones CentOS.
Amiri
--
View this message in context:
http://www.nabble.
Yes, I moved from 32 bit to 64 bit. But I did exactly what you said. I
reinstalled everything--perl, apache, mysql, DBI, DBD::mysql, every single
module--the whole shebang. So it's not just some careless oversight or file
copy. Everything has already been rebuilt and recompiled.
Amiri
--
View th
Does anyone have any guidance on what I should do here?
Amiri
--
View this message in context:
http://www.nabble.com/Segfault-Help%21-%21--tp17599739p17627528.html
Sent from the mod_perl - General mailing list archive at Nabble.com.
I realized after I posted the last bit that perhaps I should post the full
lib-loading output from gdb as well as the bt full. Here goes:
This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging symbols
found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
Core was g
Here are some better and further details. I turned on DBI debugging, so I can
see that before a segfault, I get the error
Apache::DBI disconnect (overloaded)
I have also done some gdb backtraces--I put strace output before. Here is
one gdb full bt:
(gdb) bt full
#0 0x002a994e37be
I am running Apache 1.3, mod_perl 1.30, perl 5.8.8, with gzip and ssl. I keep
getting segfaults. Sometimes they seem harmless, like the server keeps
running and honoring requests. Other times, they bring everything to a
screeching halt.
This started when I moved my server from a RAM-starved serve
Hi folks:
I am trying to tighten up the code in a web application I have made--I run
HTML::Mason and mod_perl--and I was trying to figure out how to run
Perl::Critic or some other diagnostic tool on the whole thing, so that it
would be active for every request and I could see problems throughout
13 matches
Mail list logo
