Re: [otrs] Article Storage Type

2015-02-02 Thread Olivier Macchioni

> On 31 Jan 2015, at 17:29, Mathias Bräunling 
>  wrote:
> 
> Hi,
> 
> 31/01/2015 17:20 - Ml Ml wrote:
> Hello,
>  
> we startet with otrs and Article attachments are stored in the DB until now. 
> Of course the db is growing and growing we have about 10GB of DB and a backup 
> takes ages ...
>  
> Can i now switch to FS based storage and keep the articles until now in the 
> DB?
>  
> I have already tried to run the migration script from DB to FS. This fails 
> with a few articles. Can i just skipp those and carry on?
>  
> So at the end the failed articles will remain in the DB and the rest will be 
> FS?
>  
> 
> yes, it will work like that.
> Some articles might not be switched over because of a number of reasons. 
> However, you can still leave those in the DB and move the rest to FS using 
> otrs.ArticleStorageSwitch.pl from the bin directory.
> 
> If you do this and use OTRS 4, also make sure to activate the "Check All 
> Backends" option in SysConfig. Otherwise ith might be, that OTRS will not 
> correctly display tickets with articles remaining in the DB.

Just two things to pay attention to… activating this option will generate tons 
of small files on the FS. This has cause 2 issues for us:

1. Running out of inodes on the partition (“df -i” to monitor this) - we’re 
using Linux. I don’t know if there can be a similar problem on Windows

2. The backup solution we were using was based on a file-level backup. It ended 
up choking with so many files -> we had to change our backup method for this 
specific server.

OTRS AG could probably improve things significantly by changing their storage 
format (one .tar file for all the articles of a given ticket for instance), but 
I didn’t raise any ticket with them regarding this issue as it’s not really a 
bug (it’s definitely a potential problem for scalability though).

otrs.ArticleStorageSwitch.pl is a bit limited as well (it’s lacking options to 
select the tickets you want to migrate), but well… 


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

Re: [otrs] LDAP, Agent authentication and Customer user backend. Almost running

2015-02-02 Thread Mathias Bräunling
Well.. OTRS is telling you it is looking for a customer key.
Which is an attribute that can be used as a unique identifier for a customer
user.

Have you consulted the official documentation?
[1]http://otrs.github.io/doc/manual/admin/stable/en/html/external-backends.html#ldap-customer-backend

--Mathias


[1] 
http://otrs.github.io/doc/manual/admin/stable/en/html/external-backends.html#ldap-customer-backend
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] LDAP, Agent authentication and Customer user backend. Almost running

2015-02-02 Thread Cosme Corrêa

Hi Mathias,

thank you for your time.

Yes, it is configured.
I was unable to find the problem.
My Config.pm is here and I would appreciate if you look for an error.


*Config.pm:*

# --
# Kernel/Config.pm - Config file for OTRS kernel
# Copyright (C) 2001-2014 OTRS AG, http://otrs.com/
# --
# This software comes with ABSOLUTELY NO WARRANTY. For details, see
# the enclosed file COPYING for license information (AGPL). If you
# did not receive this file, see http://www.gnu.org/licenses/agpl.txt.
# --
#  Note:
#
#  -->> Most OTRS configuration should be done via the OTRS web interface
#   and the SysConfig. Only for some configuration, such as database
#   credentials and customer data source changes, you should edit this
#   file. For changes do customer data sources you can copy the 
definitions

#   from Kernel/Config/Defaults.pm and paste them in this file.
#   Config.pm will not be overwritten when updating OTRS.
# --

package Kernel::Config;

#use strict;
use warnings;
use utf8;

sub Load {
my $Self = shift;

#  #
# database settings #
#  #

# The database host
$Self->{'DatabaseHost'} = '127.0.0.1';

# The database name
$Self->{'Database'} = "otrs";

# The database user
$Self->{'DatabaseUser'} = "otrs";

# The password of database user. You also can use 
bin/otrs.CryptPassword.pl

# for crypted passwords
$Self->{'DatabasePw'} = '';

# The database DSN for MySQL ==> more: "perldoc DBD::mysql"
$Self->{'DatabaseDSN'} = 
"DBI:mysql:database=$Self->{Database};host=$Self->{DatabaseHost}";


# The database DSN for PostgreSQL ==> more: "perldoc DBD::Pg"
# if you want to use a local socket connection
#$Self->{DatabaseDSN} = "DBI:Pg:dbname=$Self->{Database};";
# if you want to use a TCP/IP connection
#$Self->{DatabaseDSN} = 
"DBI:Pg:dbname=$Self->{Database};host=$Self->{DatabaseHost};";


# The database DSN for Microsoft SQL Server - only supported if OTRS is
# installed on Windows as well
#$Self->{DatabaseDSN} = "DBI:ODBC:driver={SQL 
Server};Database=$Self->{Database};Server=$Self->{DatabaseHost},1433";


# The database DSN for Oracle ==> more: "perldoc DBD::oracle"
#$Self->{DatabaseDSN} = 
"DBI:Oracle://$Self->{DatabaseHost}:1521/$Self->{Database}";

#
#$ENV{ORACLE_HOME} = '/path/to/your/oracle';
#$ENV{NLS_DATE_FORMAT} = '-MM-DD HH24:MI:SS';
#$ENV{NLS_LANG}= 'AMERICAN_AMERICA.AL32UTF8';

#  #
# fs root directory
#  #
$Self->{Home} = '/opt/otrs';

#  #
# insert your own config settings "here" #
# config settings taken from Kernel/Config/Defaults.pm #
#  #
# $Self->{SessionUseCookie} = 0;
# $Self->{CheckMXRecord} = 0;

#  #

#  #
# data inserted by installer #
#  #
# $DIBI$

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

$Self->{Organization} = '*';
$Self->{ProductName} = '***';


$Self->{DefaultLanguage} = 'pt_BR';

$Self->{'AuthModule1'} = 'Kernel::System::Auth::LDAP';
$Self->{'AuthModule::LDAP::Host1'} = '127.0.0.1';
$Self->{'AuthModule::LDAP::BaseDN1'} = 'dc=aa,dc=b,dc=ccc,dc=dd';
$Self->{'AuthModule::LDAP::UID1'} = 'uid';

$Self->{'AuthModule::LDAP::GroupDN'} = 
'cn=atendentes,ou=Group,dc=aa,dc=b,dc=ccc,dc=dd';

$Self->{'AuthModule::LDAP::AccessAttr'} = 'memberUid';


#$Self->{'AuthModule::UseSyncBackend'} = 'AuthSyncBackend';

$Self->{AuthSyncModule} = 'Kernel::System::Auth::Sync::LDAP';
$Self->{'AuthSyncModule::LDAP::Host'} = '127.0.0.1';
$Self->{'AuthSyncModule::LDAP::BaseDN'} = 
'dc=aa,dc=b,dc=ccc,dc=dd';

$Self->{'AuthSyncModule::LDAP::UID'} = 'uid';

$Self->{'AuthSyncModule::LDAP::UserSyncMap'} = {
# DB -> LDAP
UserFirstname => 'givenName',
UserLastname  => 'sn',
UserEmail => 'mail',
#UserMobile=> 'mobile',
};

# Attributes needed for group syncs
# (attribute name for group value key)
$Self->{'AuthSyncModule::LDAP::AccessAttr'} = 'memberUid';
# (attribute for type of group content UID/DN for full ldap name)
$Self->{'AuthSyncModule::LDAP::UserAttr'} = 'DN';
# AuthSyncModule::LDAP::UserSyncInitialGroups
# (sync following group with rw permission after initial create of 
first agent

# login)
$Self->{'AuthSyncModule::LDAP::UserSyncInitialGroups'} = [
'users',
];
# AuthSyncModule::L

[otrs] Agent Role Assignment

2015-02-02 Thread Sharad Mishra
What happens when if an agent "A” is mapped to a role "R” as well as to a group 
“G”? What set of permissions will be applicable for A? Role -> Group or Agent 
-> Group?

Sharad Mishra
sharad.m...@gmail.com



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