It appears that it *ALWAYS* prints it when your doing an :
<form action="/otrs/index.pl" method="post"> <input type="hidden" name="Action" value="AdminUser"> <input type="hidden" name="Subaction" value="Add">
so is it *REALLY* an error. It appears to throw this into the Apache error log every time I attempt to add an Admin User.
Normally it shout not appear if you go into the admin user mask.
So I think it's a bug (but it's working fine on my installations %-)).
I had filed http://bugs.otrs.org/show_bug.cgi?id=2411 on it.
It would be nice if the problem would be reproducible to finde the problem.
-=> So can you reproduce this on a fresh installed OTRS (only default settings). Did you some customizing on OTRS?
I found out why I saw it and pretty much no one else in the entire world did. :) While it seems that OTRS does try to keep security in mind, I'm not very trusting. I used something called CGIWRAP to make sure more stringent security was in place. One of the things it didn't like is that index.pl was 777, so I made it 755 for it to run. One of the features of CGIWRAP (Currently at 4.0) is that if there is any STDERR printed, it DEFAULTS to also putting it into the STDOUT stream. In the 8 or 9 years I've been using it no application ever did that which is why I didn't understand or look for that happening when I first encountered the error. One of the config options IS to keep the STDERR *OUT* of the STDOUT, which is normal for a typical basic install of any CGI onto Apache. So, in the interim, I did compile a special CGIWRAP just for OTRS and now I have things working. It apparently will happen to everyone else in the entire world, except since they aren't sending it to the screen like CGIWRAP does, they won't realize it. So on a base install, its happening that it logs the error, but just goes along its merry way. It still leads me to ask, though, if error messages like that are actually REALLY errors that should have that happen. I do see others that *ARE* true errors, and I can see putting them into the logs... But wondered if there was a better way to do it than just sending to STDERR? I usually log my CGI's to a file, so I've never worked with putting them into the ErrorLog directive. I really appreciate this, and now that the system is actually usable (Since we can add non root@localhost users) I hope to become more active in contributing. Thanks, Tuc