Login Failed - SystemID

[bwesaala]

Hi All,

I changed my SystemID in order to in order to alter the Ticket Number format. This was to avoid conflict with other OTRS installations on the same network.

It worked okay and the ticket number format changed. However, users are unable to log back in once they log out. I highly suspect the SystemID change is the cause of this problem.

We are authenticating users against an LDAP server.

Thanks,

Brian

[crythias]

you should see what the log says to determine why failure. SystemID shouldn't apply to anything but tickets.

[bwesaala]

Thank you crythias. Managed to sort it out.

It was a DNS problem. It was just a coincidence that it happened as soon as I changed the systemID.

Cheers

[crythias]

I should make you aware that you may find ticket followups with old SystemID will create new tickets. You can't easily retroactively fix this, because it's doing exactly what it is intended to do. Inbound ticket numbers will be checked against SystemID.

[bwesaala]

Thanks, will watch out for that.

Just as a follow up, where can I find or how can I configure otrs-specific logs (otrs.log), so as to be able to monitor this in case I don't have access to the web interface as was the case for me. Currently, they under apache2. From the manual I see the Windows platform has the logs under OTRS_INSTALL_DIR/var/log/...

[crythias]

By default, otrs logs via syslog in linux. It sends to /var/log/syslog or /var/log/messages.
If you want to modify this, you can change rsyslog.conf
Take a look at this viewtopic.php?f=60&t=16826

[bwesaala]

Thanks crythias,

Actually, the logs that were of interest to me were in /var/log/apache2/ ...not in /var/log/messages (which contains more otrs logs). I will try to see if I consolidate the two into otrs.log as I think it is better to have them in one place.

Cheers!