Hi all,
Since yesterday otrs.log is no longer writable and has been wiped of all its contents. Surely if the log file exists in a tmp directory then Linux will periodically wipe this file?
-rw-r----- 1 syslog adm 0 Jul 9 19:42 /tmp/otrs.log
Shouldn't it exist in /opt/otrs/var/tmp/otrs.log?
Is this the correct prcoedure to update this path?:
Update log path in: Core::Log
Update log path in: Kernel/Config.pm
Strangely enough if I look in /index.pl?Action=AdminLog then I see logs. Where is this being stored if not /tmp/otrs.log as it states?
Grateful if someone could solve this confusion for me.
Problem with otrs log file
Moderator: crythias
Problem with otrs log file
Current Production Server (recently switched from Windows)
OTRS 3.2.7 on Ubuntu 12.04LTS 64bit
PHP 5.3.10-1ubuntu3.6
mysql Ver 14.14 Distrib 5.5.31
Previous Production Server:
Windows 2008
MySQL 5.1.51 Community Server
Strawberry Perl 5.12.3.0
OTRS 3.2.7 on Ubuntu 12.04LTS 64bit
PHP 5.3.10-1ubuntu3.6
mysql Ver 14.14 Distrib 5.5.31
Previous Production Server:
Windows 2008
MySQL 5.1.51 Community Server
Strawberry Perl 5.12.3.0
-
- Moderator
- Posts: 10169
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Problem with otrs log file
Defaults.pm
Where does SysLog go? Wherever it points within rsyslog... usually /var/log/messages or /var/log/syslog
For more information: viewtopic.php?f=60&t=16826
Code: Select all
$Self->{LogModule} = 'Kernel::System::Log::SysLog';
# $Self->{'LogModule'} = 'Kernel::System::Log::File';
$Self->{'LogModule::SysLog::Facility'} = 'user';
$Self->{'LogModule::SysLog::LogSock'} = 'unix';
$Self->{'LogModule::LogFile'} = '/tmp/otrs.log'; #not relevant because SysLog, not File
For more information: viewtopic.php?f=60&t=16826
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 9
- Joined: 04 Aug 2022, 11:05
- Znuny Version: 6.4.1
- Real Name: Stefano Simula
Re: Problem with otrs log file
Hi Crythias,
Thanks for your reply.
From what I can see from the file:
There is no "CGILogPrefix" in the log.. do you know why?
Thanks,
Stefano
Thanks for your reply.
From what I can see from the file:
Code: Select all
Oct 23 09:15:13 helpdesk-psa systemd[1]: user@1000.service: Deactivated successfully.
Oct 23 09:15:13 helpdesk-psa systemd[1]: Stopped User Manager for UID 1000.
Oct 23 09:15:13 helpdesk-psa systemd[1]: Stopping User Runtime Directory /run/user/1000...
Oct 23 09:15:13 helpdesk-psa systemd[1]: run-user-1000.mount: Deactivated successfully.
Oct 23 09:15:13 helpdesk-psa systemd[1]: user-runtime-dir@1000.service: Deactivated successfully.
Oct 23 09:15:13 helpdesk-psa systemd[1]: Stopped User Runtime Directory /run/user/1000.
Oct 23 09:15:13 helpdesk-psa systemd[1]: Removed slice User Slice of UID 1000.
Oct 23 09:15:13 helpdesk-psa systemd[1]: user-1000.slice: Consumed 1.194s CPU time.
Oct 23 09:20:02 helpdesk-psa systemd[1]: Created slice User Slice of UID 1000.
Oct 23 09:20:02 helpdesk-psa systemd[1]: Starting User Runtime Directory /run/user/1000...
Oct 23 09:20:02 helpdesk-psa systemd[1]: Finished User Runtime Directory /run/user/1000.
Oct 23 09:20:02 helpdesk-psa systemd[1]: Starting User Manager for UID 1000...
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Queued start job for default target Main User Target.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Created slice User Application Slice.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Started Mark boot as successful after the user session has run 2 minutes.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Started Daily Cleanup of User's Temporary Directories.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Reached target Paths.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Reached target Timers.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Starting D-Bus User Message Bus Socket...
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Starting Create User's Volatile Files and Directories...
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Finished Create User's Volatile Files and Directories.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Listening on D-Bus User Message Bus Socket.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Reached target Sockets.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Reached target Basic System.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Reached target Main User Target.
Oct 23 09:20:02 helpdesk-psa systemd[1]: Started User Manager for UID 1000.
Oct 23 09:20:02 helpdesk-psa systemd[294562]: Startup finished in 223ms.
Oct 23 09:20:02 helpdesk-psa systemd[1]: Started Session 5692 of User otrs.
Oct 23 09:20:03 helpdesk-psa systemd[1]: session-5692.scope: Deactivated successfully.
There is no "CGILogPrefix" in the log.. do you know why?
Thanks,
Stefano