Full Time Position Available
Santa Monica, CA company has immediate full time opening for advanced Perl programmer to assume maintenance and expansion of running site. Current environment is Linux/Apache/mod_perl/MySQL. Relaxed work environment. Salary and benefits commensurate with experience. Reply to me directly, please. -jh
Re: mod_perl-1.21 and apache-1.3.9
Well, for all who have attempted to help, i wish to thank you. I decided to download the src.rpm for perl-5.005_02-2 and do a rebuild for my system, thinking that the libperl.a was trashed or at least partially responsible for the server being killed off. And i also grabbed the modperl from CVS and rebuilt that, which i had done prior to the perl rebuild and reinstall to no avail. But to my surprise, after a successful rebuild of perl-5.005_02-2.src.rpm and installing it and a successful rebuild of modperl_19991107232715 i got it all working. :-) Now i am a happy camper and see the following in my server-status: Server Version: Apache/1.3.9 (Unix) (Red Hat/Linux) mod_ssl/2.4.8 OpenSSL/0.9.4 mod_perl/1.21_01-dev PHP/3.0.12 Thanks again to all who tried to assist. Regards -- Michael B. Weiner Systems Administrator/Partner The UserFriendly Network (UFN) -- / / (_)__ __ __ / /__/ / _ \/ // /\ \/ / //_/_//_/\_,_/ /_/\_\ * * * CHOICE OF A GNU GENERATION * * *
Question about caching
I have a directory of images use for navigation purposes, but when
generating dynamic pages with:
sub handler {
$r = shift;
...
$r->header_out("Pragma","no-cache");
$r->header_out("Cache-control","no-cache");
$r->no_cache(1);
$r->send_http_header;
page to follow
}
It immediately expires the navigation images as well. A big performance
drag. Does there need to be some type of handler sniffing a navigation
image directory to set some other expiration date other than 'now'?
Thanks for any help,
Craig Bullock
Re: mod_perl-1.21 and apache-1.3.9
Rasmus Lerdorf wrote: > > As of Apache-1.3.9, Apache's DSO support really should be stable. I am > running a bunch of servers with the DSO version of the PHP module without > any problems. > > -Rasmus I am as well. I have 5 other redhat 6.1 servers running apache-1.3.9 with mod_ssl, mod_perl, openssl, and php and they all run fantastic. But its just this one redhat 5.2 server thats giving me headaches. -- Michael B. Weiner Systems Administrator/Partner The UserFriendly Network (UFN) -- / / (_)__ __ __ / /__/ / _ \/ // /\ \/ / //_/_//_/\_,_/ /_/\_\ * * * CHOICE OF A GNU GENERATION * * *
RE: Hooking into core
Once again, I don't seem to have been very successful in describing my problem. I'll try again. I am using mod_proxy, as a reverse proxy, i.e. so that I can push inbound requests to a bunch of backend servers. This works great, as most of you probably already know, until one of the back end servers dies. Depending on the error, this is reported back to the client as either a 500 Proxy Error or 502 Proxy Error, with a little but not much more info. It is not possible to use the standard ErrorDocument approach as if one attempts to use a relative URI ( so that one can use the REDIRECT_* variables ) one gets a loop because the server isn't there ( thats why we got an error in the first place ). If one does an absolute URI, one can not do anything smart with the page displayed. I would like to be able to do two things 1. When there is no alternative service, display a nice page with appropriate content. 2. If the same page can be delivered from one of the other servers, automatically redirect the request to one of them. i.e. don't show the user an error message at all. Any suggestions appreciated. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Glen Eustace, Systems Engineer - Networking, Computing Services, Massey University, Private Bag 11222, Palmerston North, N.Z. Ph: +64 6 350 5161, Fax: +64 6 350 5607, Mobile +64 25 500 321 Pvt Ph: +64 6 356 2562
Folder::Maildir / modperl woos
Hello,
i am experiencing weird problems with Folder::Maildir module and mod_perl
1.21/Apache1.3.9 running on Redhat 6. Whenever i try to receive an attachment
larger than ~100K, apache process seg faults. I figured that problem is
not in Folder::Maildir since i can receive attachments of arbitrary sizes
by running a script from a command line or as a cgi script. I have pinpointed
the problem to the following line of code in Maildir.pm (line 459):
my $fh = new IO::File "$folder/tmp/$filename", O_CREAT|O_WRONLY, 0600
or croak "can't create $folder/tmp/$filename: $!";
The apache segfaults on this line of code. I have checked everything.. variables
are initialized, permissions are correct, plenty of disk space.. i mean
the script runs fine as a cgi script..
Here is the strace output:
# strace ./httpd -X
[snip]
select(8, [4], NULL, NULL, {120, 0})= 1 (in [4], left {120, 0})
read(4, "bEg30gHR5uLVkdEg64918RL6e/b\r\nt"..., 1024) = 953 <-- done
receiving an attachment from a mail server
brk(0x876f000) = 0x876f000
brk(0x877) = 0x877
brk(0x8771000) = 0x8771000
SYS_175(0, 0, 0xb90c, 0x8, 0) = 0
brk(0x8777000) = 0x8777000
brk(0x8778000) = 0x8778000
brk(0x8779000) = 0x8779000
[snip] bunch of brk calls here
open("/http/perl/syscall.ph", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/http/perl/syscall.ph", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/perl5/5.00503/i386-linux/syscall.ph", O_RDONLY) = 5
brk(0x87fc000) = 0x87fc000
fstat(5, {st_mode=S_ISVTX|071, st_size=0, ...}) = 0
mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x401d3000
read(5, "require \'_h2ph_pre.ph\';\n\nreq"..., 4096) = 54
read(5, "", 4096) = 0
close(5)= 0
munmap(0x401d3000, 4096)= 0
open("/http/perl/_h2ph_pre.ph", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/http/perl/_h2ph_pre.ph", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/perl5/5.00503/i386-linux/_h2ph_pre.ph", O_RDONLY) = 5
brk(0x87fd000) = 0x87fd000
fstat(5, {st_mode=S_ISVTX|0103, st_size=0, ...}) = 0
mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x401d3000
read(5, "# This file was created by h2ph "..., 4096) = 870
brk(0x87fe000) = 0x87fe000
brk(0x87ff000) = 0x87ff000
brk(0x880) = 0x880
brk(0x8801000) = 0x8801000
brk(0x8802000) = 0x8802000
read(5, "", 4096) = 0
close(5)= 0
munmap(0x401d3000, 4096)= 0
open("/http/perl/sys/syscall.ph", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/http/perl/sys/syscall.ph", O_RDONLY) = -1 ENOENT (No such file or
directory)
open("/usr/lib/perl5/5.00503/i386-linux/sys/syscall.ph", O_RDONLY) = 5
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
i then retrieved the big attachment from a command line and sent myself
a smaller one. after running strace on http -X again i have figured out
that apache segfaults during the following system call:
fstat(5, {st_mode=S_ISGID|S_ISVTX|0604, st_size=0, ...}) = 0
Any ideas on what is going on?
Thanks.
Get HushMail. The world's first free, fully encrypted, web-based email system.
Speak freely with HushMail http://www.hushmail.com
Re: mod_perl-1.21 and apache-1.3.9
> I don't use DSO, may be someone who does can clear things out? Why there > are so many problems with DSO. The best answer I heard so far: "DSO isn't > stabilized yet." So I have just repeated it for you, Michael. > > Come on, are we on a techical list or what? Anybody care/know to explain > when this [DSO] would change for good? I could dig the info about DSO at > apache.org, but it doesn't help... As of Apache-1.3.9, Apache's DSO support really should be stable. I am running a bunch of servers with the DSO version of the PHP module without any problems. -Rasmus
Re: mod_perl-1.21 and apache-1.3.9
> Stas Bekman wrote: > > > > Sure, compile static mod_perl. DSO is not stable. > > > > Stas - > > Not stable? Thats news to me and probably a lot of others who build DSO > modules for apache this way. OK, what is the best way to build it > statically? Well, I don't have the numbers, but think about 40% of problem reported lately were due to DSO builds. Once backed to static the problems were reported to be gone. I don't use DSO, may be someone who does can clear things out? Why there are so many problems with DSO. The best answer I heard so far: "DSO isn't stabilized yet." So I have just repeated it for you, Michael. Come on, are we on a techical list or what? Anybody care/know to explain when this [DSO] would change for good? I could dig the info about DSO at apache.org, but it doesn't help... ___ Stas Bekman mailto:[EMAIL PROTECTED]www.singlesheaven.com/stas Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC www.apache.org & www.perl.com == www.modperl.com || perl.apache.org single o-> + single o-+ = singlesheavenhttp://www.singlesheaven.com
Re: mod_perl-1.21 and apache-1.3.9
Stas Bekman wrote: > > Sure, compile static mod_perl. DSO is not stable. > Stas - Not stable? Thats news to me and probably a lot of others who build DSO modules for apache this way. OK, what is the best way to build it statically? Regards -- Michael B. Weiner Systems Administrator/Partner The UserFriendly Network (UFN) -- / / (_)__ __ __ / /__/ / _ \/ // /\ \/ / //_/_//_/\_,_/ /_/\_\ * * * CHOICE OF A GNU GENERATION * * *
Re: mod_perl-1.21 and apache-1.3.9
On Sun, 7 Nov 1999, hUnTeR wrote: > Dear list readers - > > I have tried to read all the relevant documentation on building mod_perl > for apache prior to building it. And i believe that i am running all > that is required for it to work: > > Redhat-5.2 > Linux-2.0.38 > Apache-1.3.9 > Perl-5.005_02 > > And when i go to make the module i am using the following: > > perl Makefile.PL USE_APXS=1 WITH_APXS=/usr/sbin/apxs EVERYTHING = 1 > > for DSO installation of mod_perl > > And it appears to be a successful make, with no compilation errors. > > However, when i uncomment the appropriate lines in the httpd.conf file, > and go to restart the webserver, it wont start properly, if fires up the > first process, and then i check with httpd status and the pids are > continually changing as if the daughters are all killed and trying to > restart. And the webserver eventually dies. I even tried the same with > mod_perl-1.17 with the same end result. The libperl.so is indeed in the > modules directory, but apache doesnt seem to like it very much. > > Can anyone possibly point me in the right direction, or give a hint as > to what might be wrong? Thanks in advance for any assistance. Sure, compile static mod_perl. DSO is not stable. > > Regards > -- > Michael B. Weiner > Systems Administrator/Partner > The UserFriendly Network (UFN) > -- > > / / (_)__ __ __ > / /__/ / _ \/ // /\ \/ / >//_/_//_/\_,_/ /_/\_\ > > * * * CHOICE OF A GNU GENERATION * * * > ___ Stas Bekman mailto:[EMAIL PROTECTED]www.singlesheaven.com/stas Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC www.apache.org & www.perl.com == www.modperl.com || perl.apache.org single o-> + single o-+ = singlesheavenhttp://www.singlesheaven.com
Re: Apache::Session Locking
[EMAIL PROTECTED] wrote: > > > "Kimbro" == Kimbro Staken writes: > > Kimbro> I'm trying to setup Apache::Session under Embperl with a MySQL > Kimbro> datastore. I have multiple machines that will be serving the site thus > Kimbro> all machines will access the datastore. In the documentation it says to > Kimbro> use the DBIStore with a DaemonLocker which is fine. However there seems > Kimbro> to be no documentation on how to use the DeamonLocker. I see it is There isn't any documentation of the DaemonLocker class because it is incomplete and experimeantal. It is not usable. > Well, I've ended up using NullLocker. I still don't understand how > Apache::Session could work. Any lock-releasing is done ONLY in DESTROY > method, and while it should perform excellently in CGIs, I wonder how > locks ever gets released in mod_perl environment... Funny, If you had read the documentation or my 50+e18 emails to [EMAIL PROTECTED] on the subject, you would have found the answer. Here it is from Apache::Session since your perldoc program seems to be broken: As shown in this example, you should undef or untie your session hash as soon as you are done with it. This will free up any locks associated with your process. This is the way to free up locks. Whenever you have a question as to why your httpds are hanging after the first request, the answer is that your session hash MUST be scoped at the request level! Again I urge you to read the archive. -jwb
Re: XML and Apache
On Fri, 05 Nov 1999, Anthony Gardner wrote: > All, > > I have a problem. > > I want to use data in XML format and store it in memory for obvious reasons > of speed and to utilise the capabilities of XML. I also want to load the > data at server start up time. > > The problem arises with the size of the data. I end up with six children > each with 150MB of data. Needless to say I've run out of memory and the > error_log gives error msgs about not being able to fork. > > I really would like to keep the data in XML format and not use a DB. How can > I make it so that the children reference one copy of data and not have their > own. > > I've tried assigning the $doc from $xp->parsefile to IPC::Shareable but that > keels over under the load. > > I could maybe get away with not loading the data at startup time but how can > the children reference it? > > Have I over looked a simple strategy? Or Wot!! Definitely. XML is not a database format. It can make a great database export/transmission format, but don't use it for a live database - you may live to regret it :) -- Details: FastNet Software Ltd - XML, Perl, Databases. Tagline: High Performance Web Solutions Web Sites: http://come.to/fastnet http://sergeant.org Available for Consultancy, Contracts and Training.
RE: Apache::Session Locking
> Kimbro> I'm trying to setup Apache::Session under Embperl with a MySQL > Kimbro> datastore. I have multiple machines that will be serving > the site thus > Kimbro> all machines will access the datastore. In the > documentation it says to > Kimbro> use the DBIStore with a DaemonLocker which is fine. > However there seems > Kimbro> to be no documentation on how to use the DeamonLocker. Yes, documentation of Apache::Session is not the best side of the module... You have to take a look at the source on your own... > I see it is > Well, I've ended up using NullLocker. I still don't understand how > Apache::Session could work. Any lock-releasing is done ONLY in DESTROY > method, and while it should perform excellently in CGIs, I wonder how > locks ever gets released in mod_perl environment... > In normal scripts you create a session object and destroy it at the end of your script. Embperl goes a differnt way. It uses the cleanup method of HTML::Embperl::Session (which is a subclass of Apache::Session; in Embperl 1.2b11, older version had used different names, but the same code). The cleanup method will make sure that all locks are released. It works, I use it on my own. (DBIStore and SysVSemaphoeLocker, I don't have tried DeamonLocker) Gerald
mod_perl-1.21 and apache-1.3.9
Dear list readers - I have tried to read all the relevant documentation on building mod_perl for apache prior to building it. And i believe that i am running all that is required for it to work: Redhat-5.2 Linux-2.0.38 Apache-1.3.9 Perl-5.005_02 And when i go to make the module i am using the following: perl Makefile.PL USE_APXS=1 WITH_APXS=/usr/sbin/apxs EVERYTHING = 1 for DSO installation of mod_perl And it appears to be a successful make, with no compilation errors. However, when i uncomment the appropriate lines in the httpd.conf file, and go to restart the webserver, it wont start properly, if fires up the first process, and then i check with httpd status and the pids are continually changing as if the daughters are all killed and trying to restart. And the webserver eventually dies. I even tried the same with mod_perl-1.17 with the same end result. The libperl.so is indeed in the modules directory, but apache doesnt seem to like it very much. Can anyone possibly point me in the right direction, or give a hint as to what might be wrong? Thanks in advance for any assistance. Regards -- Michael B. Weiner Systems Administrator/Partner The UserFriendly Network (UFN) -- / / (_)__ __ __ / /__/ / _ \/ // /\ \/ / //_/_//_/\_,_/ /_/\_\ * * * CHOICE OF A GNU GENERATION * * *
Apache::Session Locking
> "Kimbro" == Kimbro Staken writes: Kimbro> I'm trying to setup Apache::Session under Embperl with a MySQL Kimbro> datastore. I have multiple machines that will be serving the site thus Kimbro> all machines will access the datastore. In the documentation it says to Kimbro> use the DBIStore with a DaemonLocker which is fine. However there seems Kimbro> to be no documentation on how to use the DeamonLocker. I see it is Well, I've ended up using NullLocker. I still don't understand how Apache::Session could work. Any lock-releasing is done ONLY in DESTROY method, and while it should perform excellently in CGIs, I wonder how locks ever gets released in mod_perl environment... -- Alexander B. Povolotsky[ICQ 18277558] [2:5020/145][[EMAIL PROTECTED]]
RE: Embperl - modperl SEGV 11 violations
> > well - I've used up about 2 days trying to figure this out on my own. > My SEGV's occur intermittantly and from different in my embperl code, > but always when using $req_req. It helps to constantly switch back and > forth from SSL pages and non-SSLpages. > Sometimes I have to hit the server over 50 times to make it SEGV. > > Here is an example confess upon catching SEGV 11 > Does your startup.pl contain a use HTML::Embperl ; If not, please add it. If it's already their, or it doesn't help to add it, please start your Apache under gdb and when you receive the SIGSEGV print out a stack backtrace (BT) and send it to me. You may also try to upgrade to 1.2b11, because there was a problem with memory management, which occurs only when you Execute a lot of files (The error has only occured with tainting on, but I am not sure if it could cause problems, even with tainting off) Gerald --- Gerald Richter ecos electronic communication services gmbh Internet - Infodatenbanken - Apache - Perl - mod_perl - Embperl E-Mail: [EMAIL PROTECTED] Tel:+49-6133/925151 WWW:http://www.ecos.de Fax:+49-6133/925152 --- >
RE: Make error: Apache_1.3.9 + mod_perl-1.21 + RedHat-6.0
Ted, please keep the threads on the list. When someone attempts to help, it doesn't always mean, he wills and capable to follow-up, unless he explicitly offers this to you! What are the parameters did you pass to the 'perl Makefile.PL'? What are the versions of mod_perl and apache did you use? > > >> Hi, > >> > >> I hope someone can help me. I cannot get Apache to compile with > >> mod_perl. By itself, Apache builds fine. Introducing mod_perl causing > >> the problem. The solution isn't obvious to me. The "The all-in-one way" > >> described in INSTALL.apaci causes the same problem. I'm using perl, > >> version 5.005_03 built for i686-linux. > > >Seems like a corrupted source file(s) -- did you try getting fresh > >apache and mod_perl sources and trying it again? > > Yes, I reloaded source tars but got the same compile errors. God, I hope you > can help! > > ===> modules/perl > gcc -I. -I../../include -I../../include/regex -I../../include/.././os/unix - > DLINUX=2 -DUSE_HSREGEX -DUSE_EXPAT -I../lib/expat-lite -DMOD_PERL > `/usr/bin/perl -MExtUtils::Embed -e > opts` -DNO_PERL_DISPATCH -DNO_PERL_POST_READ_REQUEST -DNO_PERL_TRANS -DNO_ > PERL_HEADER_PARSER -DNO_PERL_ACCESS -DNO_PERL_AUTHEN -DNO_PERL_AUTHZ -DNO_PE > RL_TYPE -DNO_PERL_FIXUP -DNO_PERL_LOG -DNO_PERL_INIT -DNO_PERL_CLEANUP -D > NO_PERL_RESTART -DNO_PERL_STACKED_HANDLERS -DNO_PERL_SECTIONS -DNO_PERL_METH > OD_HANDLERS -DNO_PERL_SSI -DNO_PERL_DIRECTIVE_HANDLERS -DMOD_PERL_VERSION=\ > "1.21\" -I./os/unix -I../../include -c mod_perl_opmask.c -o > mod_perl_opmask.o > In file included from ../../include/httpd.h:72, > from mod_perl.h:114, > from mod_perl_opmask.c:1: > ../../include/alloc.h:165: unrecognized format specifier for `' > In file included from ../../include/httpd.h:73, > from mod_perl.h:114, > from mod_perl_opmask.c:1: > ../../include/buff.h:172: unrecognized format specifier for `' > In file included from ../../include/httpd.h:74, > from mod_perl.h:114, > from mod_perl_opmask.c:1: > ../../include/ap.h:159: unrecognized format specifier for `' > In file included from mod_perl.h:116, > from mod_perl_opmask.c:1: > ../../include/http_protocol.h:153: unrecognized format specifier for `' > In file included from mod_perl.h:117, > from mod_perl_opmask.c:1: > ../../include/http_log.h:119: unrecognized format specifier for `' > ../../include/http_log.h:122: unrecognized format specifier for `' > ../../include/http_log.h:133: unrecognized format specifier for `' > make[3]: *** [mod_perl_opmask.o] Error 1 > make[2]: *** [all] Error 1 > make[1]: *** [subdirs] Error 1 > make[1]: Leaving directory `/home/ted/src/support/apache_1.3.9/src' > make: *** [apache_httpd] Error 2 > > ___ Stas Bekman mailto:[EMAIL PROTECTED]www.singlesheaven.com/stas Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC www.apache.org & www.perl.com == www.modperl.com || perl.apache.org single o-> + single o-+ = singlesheavenhttp://www.singlesheaven.com
