1st Issue:
Just facing some trouble with the customer front end, to be exactly: the CustomerTicketMessage
Usually when changing a dropdown field entry as "service", the form is "reloading" i.e. to display the right SLA choices
Works fine. As long as nobody is trying to upload an attachment. As soon as an attachment is uploaded, the form isnt reloaded when changing the "service" dropdown
someone with an idea?
2nd issue:
I hardly can manage to upload attachments of 5MB.....10MB: forget it!
Whats wrong?
Regards
Rudy
Costomer front end - problems with atachment upload
Moderator: crythias
Costomer front end - problems with atachment upload
Last edited by Rotyn on 21 Sep 2012, 19:18, edited 2 times in total.
Testing & Productive: OTRS::ITSM 3.3.5 on CentOS 6.5 and MySQL
Packages: All included
Packages: All included
Re: Costomer front end - problems with atachment upload
First one I have no idea. For the second issue, is your SQL configured to accept such large files (maxallowpackage)? Or even better, have you enabled the option to save attachments outside of SQL (WebUploadCacheModule in sysconfig)?
Re: Costomer front end - problems with atachment upload
From OTRS and mySQL side the settings are fine.....up to 25MB allowed
Since I experience a general performance problem:
Unser OS: Windows Server 2008 R2 Datacenter (64-bit)
Unser Apache: Apache 2.2.17 (32-bit)
Unser Datenbank: MySQL 5.1.51 (32-bit)
Could it be that the Apache and DB in the 32bit version doesn't work well with the 64bit server OS?
Since I experience a general performance problem:
Unser OS: Windows Server 2008 R2 Datacenter (64-bit)
Unser Apache: Apache 2.2.17 (32-bit)
Unser Datenbank: MySQL 5.1.51 (32-bit)
Could it be that the Apache and DB in the 32bit version doesn't work well with the 64bit server OS?
Testing & Productive: OTRS::ITSM 3.3.5 on CentOS 6.5 and MySQL
Packages: All included
Packages: All included
Re: Costomer front end - problems with atachment upload
32 bit versions of those programs should work fine on a 64 bit OS. If you have no specific reason for using 32 bit versions, then you should be running 64 bit though, especially if you have a large amount of RAM available.
If you have a general performance problem I'd start with the basics, eg how much RAM is in use, what does the CPU util look like when the server is busy, how full are the partitions, etc. Checking the connectivity to your mail servers is also another idea, as long time-outs can create delays in the interface.
If you have a general performance problem I'd start with the basics, eg how much RAM is in use, what does the CPU util look like when the server is busy, how full are the partitions, etc. Checking the connectivity to your mail servers is also another idea, as long time-outs can create delays in the interface.
Backend: OTRS 3.0.11 RedHat Enterprise Linux 6.2, Apache, MySQL with replication
Frontend: OTRS 3.0.11 RedHat Enterprise Linux 6.2 with SELinux, Apache SSL
Frontend: OTRS 3.0.11 RedHat Enterprise Linux 6.2 with SELinux, Apache SSL