My apologies for introducing another issue
Should i perhaps put these into RT somewhere?
RT_LOGFILE tells where to log stuff. If you want to use syslog, get
problems reported by mail or anything else, check etc/config.pm and
the Log::Dispatch POD.
RT_LOGFILE = ($RT_PATH)/rt.log
Should this not be $(RT_PATH) ?
Also, the Makefile doesnt do the inplace substitutions on
etc/config.pm, so it ends up looking like
[snip]
$Logger->add(Log::Dispatch::File->new
( name=>ārtlogā,
min_level=>āinfoā,
filename=>ā!!RT_LOGFILE!!ā,
mode=>āappendā,
callback => sub {%p=@_; return ā$p{message}\nā}
));
And a file named !!RT_LOGFILE!! is placed in the current directory
When i look into this file i get:
[root@beer]15:55/www/rt2/bin/cgi% cat \!\!RT_LOGFILE\!\!
HTML::Mason::Interp::new: must specify value for data_dir
HTML::Mason::Interp::new: must specify value for data_dir
HTML::Mason::Interp::new: must specify value for data_dir
Being new to HTML::Mason, iām not sure what this means, but
iāll see if i canāt glean the problem from the perl sourceā¦
cheers,
_M.
Michael Jastremski ā¦ AIM:rstfinsyn
WORK:liquidation.com ME:westphila.net/mike
PHOTO:opl.megaglobal.net ā¦ BIZ:megaglobal.net
And so i says to him|herā¦
When i look into this file i get:
[root@beer]15:55/www/rt2/bin/cgi% cat !!RT_LOGFILE!!
HTML::Mason::Interp: must specify value for data_dir
HTML::Mason::Interp: must specify value for data_dir
HTML::Mason::Interp: must specify value for data_dir
Being new to HTML::Mason, iām not sure what this means, but
iāll see if i canāt glean the problem from the perl sourceā¦
I see. Looking at rtmux.pl.org, the problem is that after the install,
the following variables in rtmux.pl end up getting set to null.
#TODO: Make this draw from the config file
my $interp = new HTML::Mason::Interp (
parser=>$parser,
comp_root=>ā!!WEBRT_HTML_PATH!!ā,
data_dir=>ā!!WEBRT_DATA_PATH!!ā);
Probably due to the following typo in the mux-install rule:
s'!!WEBRT_HTML_PATH!!'$($WEBRT_HTML_PATH)'g;\
s'!!WEBRT_DATA_PATH!!'$($WEBRT_DATA_PATH)'g;\
It seems that the extra $ signs are spuriousā¦
Another patch for the makefileā¦
regards,
_Michael.
Michael Jastremski ā¦ AIM:rstfinsyn
WORK:liquidation.com ME:westphila.net/mike
PHOTO:opl.megaglobal.net ā¦ BIZ:megaglobal.net
My apologies for introducing another issue
Should i perhaps put these into RT somewhere?
Hm ā¦ what do you mean āPut it into RTā? If you mean āsend patchesā,
then that might be a good idea Also, minor bugfixes might be sent to
me instead of the list.
RT_LOGFILE = ($RT_PATH)/rt.log
Should this not be $(RT_PATH) ?
Of course. I didnāt test this, my fault. Thanx.
Also, the Makefile doesnt do the inplace substitutions on
etc/config.pm, so it ends up looking like
Oh? Weird. Iāll look at it.
And a file named !!RT_LOGFILE!! is placed in the current directory
When i look into this file i get:
[root@beer]15:55/www/rt2/bin/cgi% cat !!RT_LOGFILE!!
HTML::Mason::Interp: must specify value for data_dir
HTML::Mason::Interp: must specify value for data_dir
HTML::Mason::Interp: must specify value for data_dir
Being new to HTML::Mason, iām not sure what this means, but
iāll see if i canāt glean the problem from the perl sourceā¦
Hm. I just got a mail from another person that said he couldnāt get the
webmux.pl to work (httpd just died on him when the perlhandler was
installed). Iām running FCGI instead of perl_mod myself, so I donāt know
much.
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
My apologies for introducing another issue
Should i perhaps put these into RT somewhere?
Hm ā¦ what do you mean āPut it into RTā? If you mean āsend patchesā,
then that might be a good idea Also, minor bugfixes might be sent to
me instead of the list.
presumably the bugs queue.
RT_LOGFILE = ($RT_PATH)/rt.log
Should this not be $(RT_PATH) ?
Of course. I didnāt test this, my fault. Thanx.
Also, the Makefile doesnt do the inplace substitutions on
etc/config.pm, so it ends up looking like
Oh? Weird. Iāll look at it.
And a file named !!RT_LOGFILE!! is placed in the current directory
When i look into this file i get:
[root@beer]15:55/www/rt2/bin/cgi% cat \!\!RT_LOGFILE\!\!
HTML::Mason::Interp::new: must specify value for data_dir
HTML::Mason::Interp::new: must specify value for data_dir
HTML::Mason::Interp::new: must specify value for data_dir
Being new to HTML::Mason, iām not sure what this means, but
iāll see if i canāt glean the problem from the perl sourceā¦
Hm. I just got a mail from another person that said he couldnāt get the
webmux.pl to work (httpd just died on him when the perlhandler was
installed). Iām running FCGI instead of perl_mod myself, so I donāt know
much.
He should look in the !!RT_LOGFILE!! that was created. Iād put money on it
being the Mail::addrlist bug.
ā
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent ā root@eruditorum.org ā jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
As I sit here alone looking at green text on a laptop in a mostly bare room listening
to loud music wearing all black, I realize that that it is much less cool in real life
āRichard Tibbets
I see. Looking at rtmux.pl.org, the problem is that after the install,
the following variables in rtmux.pl end up getting set to null.
You should use webmux.pl for operations with mod_perl. The
web-code in rtmux.pl contains a lot of errors, thatās for sure. Iāve
managed to get one rtmux.pl running locally, but I have been too lazy to
update the rtmux.pl yet.
Probably due to the following typo in the mux-install rule:
sā!!WEBRT_HTML_PATH!!ā$($WEBRT_HTML_PATH)āg;
sā!!WEBRT_DATA_PATH!!ā$($WEBRT_DATA_PATH)'g;\
Oh. Iāll fix that also.
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
And a file named !!RT_LOGFILE!! is placed in the current directory
He should look in the !!RT_LOGFILE!! that was created. Iād put money on it
being the Mail::addrlist bug.
Actually the first bug is probably the same one that I got where RT tries to
write that log file to any directory it ends up in and rt dosnāt usually
have perms to write into say /usr/lib/perl5/site_perl/
I pointed the RT_LOGFILE to /tmp/rt.log and that fixes the first problem.
The second is most likely addrlist.pm and date.pm not being around, Find the
follow files and link them to thier lowercase names instead then it should
work. Here is the location on my system.
/usr/lib/perl5/site_perl/5.005/Mail/Field
do the next two commands in the Field dir to fix the problem.
ln -sf AddrList.pm addrlist.pm
ln -sf Date.pm date.pm
ā
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent ā root@eruditorum.org ā jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
As I sit here alone looking at green text on a laptop in a mostly bare room
listening
to loud music wearing all black, I realize that that it is much less cool in
real life
āRichard Tibbets
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Hm ā¦ what do you mean āPut it into RTā? If you mean āsend patchesā,
then that might be a good idea Also, minor bugfixes might be sent to
me instead of the list.
presumably the bugs queue.
Actually I will deal with small bugreports and attached patches if they
come directly to me. More complex bugs (without applied patches) should
be sent to the bug queue at rt20@fsck.com.
Hm. I just got a mail from another person that said he couldnāt get the
webmux.pl to work (httpd just died on him when the perlhandler was
installed). Iām running FCGI instead of perl_mod myself, so I donāt know
much.
He should look in the !!RT_LOGFILE!! that was created. Iād put money on it
being the Mail::addrlist bug.
No, he had already dealt with thatā¦
Thatās another really weird bug that I havenāt managed to reproduce. When
starting up RT2, it complains that it canāt find Mail::Field::addrlist and
Mail::Field::date - while Mail::Field::AddrList and Mail::Field::Date
exists. The problem vanishes when some symlinks are made at the right
place. I absolutely havenāt found out why this happens, and I havenāt
managed to get a stack trace which made any sense. Iāve even scanned the
whole RT + DBIx + site_perl after āaddrlistā without finding anything at
all!
The only thing that is certain is that this bug was introduced when I
started using Log::Dispatch. But Log::Dispatch passes itās test suite ā¦
so I really donāt know where and how to lookā¦
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
/usr/lib/perl5/site_perl/5.005/Mail/Field
do the next two commands in the Field dir to fix the problem.
ln -sf AddrList.pm addrlist.pm
ln -sf Date.pm date.pm
while that will patch the problem for now, thatās not a solution we can
release withā¦
ā
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
ā
jesse reed vincent ā root@eruditorum.org ā jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
As I sit here alone looking at green text on a laptop in a mostly bare room
listening
to loud music wearing all black, I realize that that it is much less cool in
real life
āRichard Tibbets
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
jesse reed vincent ā root@eruditorum.org ā jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
āItās buried in the desert, got sand in it, melts Nazis. You know,
the Ark of the Covenantā ā siva
And so i says to him|herā¦
Actually I will deal with small bugreports and attached patches if they
come directly to me. More complex bugs (without applied patches) should
be sent to the bug queue at rt20@fsck.com.
Gotcha. āPut it in RTā is what folks are always saying around here .
Or perhaps thats what i tell them when they come to me with scraps
of paper with issues written on them;)
Hm. I just got a mail from another person that said he couldnāt get the
webmux.pl to work (httpd just died on him when the perlhandler was
installed). Iām running FCGI instead of perl_mod myself, so I donāt know
much.
Iām curious, is mod_perl the preferred platform, or can i get away
with running it in plain old CGI mode? I was using rtmux.pl to
begin with because āmake installā created a symlink from rtmux.pl
to webrt.cgi, so i assumed that was what i was to be usingā¦
Thatās another really weird bug that I havenāt managed to reproduce. When
starting up RT2, it complains that it canāt find Mail::Field::addrlist and
Mail::Field::date - while Mail::Field::AddrList and Mail::Field::Date
exists. The problem vanishes when some symlinks are made at the right
place. I absolutely havenāt found out why this happens, and I havenāt
managed to get a stack trace which made any sense. Iāve even scanned the
whole RT + DBIx + site_perl after āaddrlistā without finding anything at
all!
I just did some quick searching of my own in my perl tree.
I havenāt come up with anything yet.
_Michael.
Michael Jastremski ā¦ AIM:rstfinsyn
WORK:liquidation.com ME:westphila.net/mike
PHOTO:opl.megaglobal.net ā¦ BIZ:megaglobal.net
Actually I will deal with small bugreports and attached patches if they
come directly to me. More complex bugs (without applied patches) should
be sent to the bug queue at rt20@fsck.com.
Gotcha. āPut it in RTā is what folks are always saying around here .
Or perhaps thats what i tell them when they come to me with scraps
of paper with issues written on them;)
Heh, while RT1 might be good enough for the support dept, itās not good
enough for me One of the most essential things (which will be dealt
with in RT2) is that it doesnāt support attachments. Because of
linebreaks and so on, itās usually a lot easier to get patches as
attachments.
Hm. I just got a mail from another person that said he couldnāt get the
webmux.pl to work (httpd just died on him when the perlhandler was
installed). Iām running FCGI instead of perl_mod myself, so I donāt know
much.
Iām curious, is mod_perl the preferred platform, or can i get away
with running it in plain old CGI mode?
You can get away with plain, old CGI, but it will go quite slowly.
Unfortunately, we have a lot of overhead in the object oriented approach
as for now - we hope we can optimize it a bit.
Itās really not that hard to install FCGI. I donāt like mod_perl much, it
seems to me that it has this tendency of letting the httpd die with a
segfault and no explanation whatsoever whatās wrong with itself nor the
perl code.
I was using rtmux.pl to
begin with because āmake installā created a symlink from rtmux.pl
to webrt.cgi, so i assumed that was what i was to be usingā¦
Did you ever read the README?
Thatās another really weird bug that I havenāt managed to reproduce.
ā¦eh, I have managed to reproduce it, just not pinpoint it The perl
5.6.0 debugger seems instable, and it never managed to give me a stack
trace which made sense. It also seems to do a lot of weird things
(with a lot of weird warnings) during cleanup. So my advice to
everybody: Donāt install perl 5.6.0!
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
Looking closer at the code, it seems pretty obvious that it must be
something wrong with Field.pm itself:
foreach $f (readdir(DIR))
next
unless $f =~ /^([\w-]+)/;
my $p = lc $1;
(...)
eval "require ${pkg}::$p"
This is plain wrong, thatās one thing. But Iām still interessted to see
the stack trace to discover why this shi^H^H^Hinteressting piece of code
was called in the first place. Itās really a waste to require packages
that are never used.
āThe trouble with the world is that the stupid are
cocksure and the intelligent are full of doubt.ā
| > > Hm ā¦ what do you mean āPut it into RTā? If you mean āsend patchesā,
| > > then that might be a good idea Also, minor bugfixes might be sent
| to > > me instead of the list.
| > >
| > presumably the bugs queue.
|
| Actually I will deal with small bugreports and attached patches if they
| come directly to me. More complex bugs (without applied patches) should
| be sent to the bug queue at rt20@fsck.com.
|
| > > Hm. I just got a mail from another person that said he couldnāt get
| the > > webmux.pl to work (httpd just died on him when the perlhandler was
| > > installed). Iām running FCGI instead of perl_mod myself, so I donāt
| know > > much.
| > >
| >
| > He should look in the !!RT_LOGFILE!! that was created. Iād put money on
| it > being the Mail::addrlist bug.
|
| No, he had already dealt with thatā¦
|
| Thatās another really weird bug that I havenāt managed to reproduce. When
| starting up RT2, it complains that it canāt find Mail::Field::addrlist and
| Mail::Field::date - while Mail::Field::AddrList and Mail::Field::Date
| exists. The problem vanishes when some symlinks are made at the right
| place. I absolutely havenāt found out why this happens, and I havenāt
| managed to get a stack trace which made any sense. Iāve even scanned the
| whole RT + DBIx + site_perl after āaddrlistā without finding anything at
| all!
|
| The only thing that is certain is that this bug was introduced when I
| started using Log::Dispatch. But Log::Dispatch passes itās test suite ā¦
| so I really donāt know where and how to lookā¦
Ā±ā>8
Mail::Field is broken. The stack trace is useless because itās obscured by
an AUTOLOAD routine which automagically loads the appropriate
Mail::Field::* āsubclassā; said AUTOLOAD does a ucfirst, but should be
doing an lc (or the files should be renamedā¦).
(The documentation matches Mail::Field::_header_pkg_name, so I conclude
that the *.pm files are misnamed.)
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical & computer engineering KF8NH
carnegie mellon university [ābetter check the oblivious firstā -ke6sls]