Re: [dev] unix dgram connect: No such file or directory at../..//Kernel/System/Log/SysLog.pm line 65

Hi Michiel, Many thanks, my OTRS is now working. Best regards, Graeme ----- Original Message ----- From: "Michiel Beijen" To: "Development community of OTRS.org" Sent: Tuesday, February 16, 2010 3:02 PM Subject: Re: [dev] unix dgram connect: No such file or directory at../..//Kernel/System/Log/SysLog.pm line 65

Hi Graeme,

Though slightly more advanced than usual, this is still a "Configuration" type question, and not a developer-one, so you actually should best be asking at otrs@ instead of dev@... That said, it seems like your hoster did not give you permissions to write to Syslog. That is not uncommon. The problem is, successful authentication is always written to the log - and that is not possible in your setup, generating the 500 error. Now if you enable debugging, just opening the login page will already trigger a log message, giving you the 500 even earier.

Please try to set the following via otrs/Kernel/Config.pm

$Self->{'LogModule'} = 'Kernel::System::Log::File'; $Self->{'LogModule::LogFile'} = '/tmp/otrs.log';

where /tmp/otrs.log is a log name at a location you have write permissions on.

-- Michiel Beijen R&D

Follow me on Twitter: @otrsnl [https://twitter.com/otrsnl]

OTRS AG Norsk-Data-Str 1. 61352 Bad Homburg Germany

T: +31 (0) 6457 42418 F: +49 (0) 9421 56818-18 I: http://www.otrs.com/

Business location: Bad Homburg, Country Court: Bad Homburg, HRB 10751, VAT ID: DE256610065 Chairman: Burchard Steinbild, Managing Board: André Mindermann

CU@ CeBIT 2010 in Hannover (Germany) and get to know more about OTRS at booth no. C37, in hall 2 from March 2-6, 2010! http://bit.ly/4qLvqm

On Mon, Feb 15, 2010 at 5:00 PM, Graeme Brough wrote:

...

I have just installed OTRS 2.3.1 and due to the limitations of my hosting package I had to install under /home/www/domain.name/otrs instead of /opt/otrs.

I think there is an issue with error reporting as when accessing otrs/bin/cgi-bin/index.pl in debug mode the error shown above is returned as the 500 error - nothing obvious is shown in either my access or error logs. If I switch off debug mode the page loads perfectly but if I login as root@localhost the same 500 error is generated.

Any suggestions as to how to fix this?

DB connectivity is fine

The following have been set in otrs/Kernel/Config.pm:

$Self->{Home} = '/home/www/domain.name/otrs'; $Self->{ScriptAlias} = 'otrs/bin/cgi-bin/'; $Self->{'LogModule'} = 'Kernel::System::Log::SysLog'; $Self->{'LogModule::LogFile'} = '/home/www/logs/otrs.log';

Graeme --------------------------------------------------------------------- OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

--------------------------------------------------------------------- OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

-------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2691 - Release Date: 02/16/10 07:35:00