Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
Ok,. Thanks.

2012/5/9 Kevin Falcone 

> On Wed, May 09, 2012 at 01:50:00PM +0200, Juanjo wrote:
> >Yes, this parameter is OK (at 15MB, per default). But the fastcgi
> parameter by default is only
> >100k.
>
> Yep, this is why I added
>
> https://github.com/bestpractical/rt/commit/89c6750d4c87cfd65c5eaaec25928bb91ccfcb43
> which will be in the docs for the next RT release.
>
> -kevin
>
> >2012/5/9 Ruslan Zakirov <[1]r...@bestpractical.com>
> >
> >  mysql also has max_packet_size (spelling may be wrong).
> >
>



-- 
Un saludo.
Juanjo Corral

[rt-users] Reply/Comments to include previous message attachments.

2012-05-09 Thread Luong Bui Duc 
Hi,

I have RT 4.0.4 and currently users requested to have previous
email(original email) attachments to be added to correspondence/reply so
they don't have  to manually download each attachment and attach in
correspondence. I'm pretty sure this feature is implemented, but just can't
find it. Could you please help me out here. Thanks a lot

-- 
Regards,

Bui Duc Luong

Re: [rt-users] 403 Forbidden message when adding local customisations

2012-05-09 Thread Jenni Wilson 
On 10/05/2012, at 11:48 AM, Kevin Falcone wrote:

> On Thu, May 10, 2012 at 10:51:18AM +1000, Jenni Wilson wrote:
>> We are upgrading RT from 3.8.7 to 4.0.5.
>> 
>> We have some mason customisations under /usr/local/share/request-
>> trackerx/html/Ticket/Elements. These work fine under 3.8.7 but under
>> 4.0.5 we are receiving a 403 Forbidden message and a blank screen.
> 
>> 
>> The functionality of the customizations is such that a separate form
>> containing custom fields are added to a ticket. When this form is
>> submitted a new ticket should be created in a different queue, however
>> the 403 and blank screen is being returned instead. The same mason
>> file - /usr/local/share/request-
>> tracker4/html/Ticket/Elements/ManageInventoryItems - is used to add
>> the custom fields and is then posted back to itself as http://rt-
>> url/Ticket/Elements/ManageInventoryItems
> 
> RT does not allow direct access to Elements, _elements, Widgets and a
> few other files.  This is a security issue since there are files in
> Elements/ that do not expect to be accessed directly.  It's simpler
> for RT to just deny direct access to these files.
> 
> If you'd applied the security patches from last year to your 3.8.7
> http://lists.bestpractical.com/pipermail/rt-announce/2011-April/000187.html
> you would have run into the same failure.
> 
> Move your custom form to something other than Elements, such as
> Tickets/CustomForms/ and you'll be fine.
> 

That was the problem. Thanks for your help.

Jenni.

[rt-users] Inline screenshots

2012-05-09 Thread rosewood 
On the RT Demo site you can paste screenshots into the ticket, like this:
http://dl.dropbox.com/u/7981096/rtticket.png

But when you submit the ticket the inline screenshot goes away. If you click
the download link you get the raw html showing

Re: [rt-users] 403 Forbidden message when adding local customisations

2012-05-09 Thread Kevin Falcone 
On Thu, May 10, 2012 at 10:51:18AM +1000, Jenni Wilson wrote:
> We are upgrading RT from 3.8.7 to 4.0.5.
> 
> We have some mason customisations under /usr/local/share/request-
> trackerx/html/Ticket/Elements. These work fine under 3.8.7 but under
> 4.0.5 we are receiving a 403 Forbidden message and a blank screen.

> 
> The functionality of the customizations is such that a separate form
> containing custom fields are added to a ticket. When this form is
> submitted a new ticket should be created in a different queue, however
> the 403 and blank screen is being returned instead. The same mason
> file - /usr/local/share/request-
> tracker4/html/Ticket/Elements/ManageInventoryItems - is used to add
> the custom fields and is then posted back to itself as http://rt-
> url/Ticket/Elements/ManageInventoryItems

RT does not allow direct access to Elements, _elements, Widgets and a
few other files.  This is a security issue since there are files in
Elements/ that do not expect to be accessed directly.  It's simpler
for RT to just deny direct access to these files.

If you'd applied the security patches from last year to your 3.8.7
http://lists.bestpractical.com/pipermail/rt-announce/2011-April/000187.html
you would have run into the same failure.

Move your custom form to something other than Elements, such as
Tickets/CustomForms/ and you'll be fine.

-kevin


pgp5ZiubO2GWs.pgp
Description: PGP signature

[rt-users] 403 Forbidden message when adding local customisations

2012-05-09 Thread Jenni Wilson 
We are upgrading RT from 3.8.7 to 4.0.5.

We have some mason customisations under 
/usr/local/share/request-trackerx/html/Ticket/Elements. These work fine under 
3.8.7 but under 4.0.5 we are receiving a 403 Forbidden message and a blank 
screen.

The functionality of the customizations is such that a separate form containing 
custom fields are added to a ticket. When this form is submitted a new ticket 
should be created in a different queue, however the 403 and blank screen is 
being returned instead. The same mason file - 
/usr/local/share/request-tracker4/html/Ticket/Elements/ManageInventoryItems - 
is used to add the custom fields and is then posted back to itself as 
http://rt-url/Ticket/Elements/ManageInventoryItems

RT is obviously able to find the file and access it in order to add the 
customised form but when it tries to post back to itself the error is occurring.

We have tried adding the following directive to the 
/etc/request-tracker4/libapache2-mod-perl2 config:


   Order Allow,Deny
   Allow from all


This makes the entire libapache2-mod-perl2 config:
-
PerlSetEnv RT_SITE_CONFIG /etc/request-tracker4/RT_SiteConfig.pm

Alias / /usr/share/request-tracker4/html


   Order Allow,Deny
   Allow from all



 SetHandler modperl
 PerlResponseHandler Plack::Handler::Apache2
 PerlSetVar psgi_app /usr/share/request-tracker4/libexec/rt-server


# Limit mail gateway access to localhost by default

   Order Allow,Deny
   Allow from 127.0.0.1



 use Plack::Handler::Apache2;
 
Plack::Handler::Apache2->preload("/usr/share/request-tracker4/libexec/rt-server");

-

We have  Set($LogToFile, 'debug') in RT_SiteConfig.pm but are seeing nothing in 
the RT error logs. 
We have 'LogLevel debug' in apache2.conf and the only error we are seeing in 
the apache error log is the 403.

All file and directory permissions appear to be the same as the 3.8.7 
installation. There are no .htaccess files.
We have also played around with the file's owners and groups with no success.

We have also tried playing around with user and group access from within the RT 
user interface.

Have there been changes made in version 4 that would cause this to fail? Is 
there a way of getting more error messages out of Apache or RT? Any other 
suggestions?

Thank-you,
Jenni.

Re: [rt-users] msmtp with RT 4.0.5 setup issues

2012-05-09 Thread Dave Burgess 
I ran into a similar problem with my hosted e-mail provider, and there 
are a couple of things that helped me:


1)  The smtp host name (the one returned by "telnet server 25") was the 
only one that would work for my authentication step.
2)  Some providers use alternate ports for anything by "vanilla" e-mail 
forwarding.


You might also want to check with your SMTP provider - they may not let 
you do this at all.


Dave

On 5/9/2012 10:36 AM, Scott Sjodin wrote:

Kevin,

I'm using an external mail server that's hosted, so I can't exactly 
check those logs. I will check out the verbose logging and the client 
you suggested and report back. Thank You.


On Wed, May 9, 2012 at 7:17 PM, Kevin Falcone 
mailto:falc...@bestpractical.com>> wrote:


On Wed, May 09, 2012 at 07:13:24PM +0400, Scott Sjodin wrote:
> Msmtp is running, however, when I attempt to send mail thru a
test (msmtp
> -a default @domain.com ) I get the
following errors both in the
> CLI and the log:
>
> msmtp: TLS handshake failed: the operation timed out
> msmtp: could not send mail (account default from /etc/msmtprc)

If msmtp has a verbose mode, use it.  Otherwise, your best bet is
going to be the logs of the server you're trying to relay through.

You can also use openssl's s_client command to try connecting to the
relay server to check the tls connection.

-kevin





--
Dave Burgess
Manager
Cynjut Consulting Services, LLC
402-403-4434 (Phone, FAX, and Cell)


--
Dave Burgess - Manager VOIP Nebraska 402-403-4434 (Phone, FAX, and Cell) 
/A subsidiary of Cynjut Consulting Svcs, LLC/

Re: [rt-users] --no-verify-ssl option

2012-05-09 Thread David T. Grayston 
I guess that was obvious - thanks. I went ahead and uploaded just the 4.0.5 
rt-mailgate and it seems to work fine with the no-verify-ssl option in my 
installation. I think I've got the need prerequisites installed and tried the 
ca-file option but still couldn't get the ssl to verify so just giving up on it 
for now.

David
--
David T. Grayston Systems & Database Administrator
University of Washington   School of Public Health

> -Original Message-
> From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-
> boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone
> Sent: Tuesday, May 08, 2012 7:27 PM
> To: rt-users@lists.bestpractical.com
> Subject: Re: [rt-users] --no-verify-ssl option
> 
> On Wed, May 09, 2012 at 01:45:10AM +, David T. Grayston wrote:
> >I'm trying to get rt-mailgate working with https which seems kind of
> difficult around
> >verifying the certificate.
> >
> >I was hoping to use this option "--no-verify-ssl" to successfully test 
> > "--url
> >https://myrt.server.edu/rt/"; but I'm getting in my fetchmail log
> "Unknown option:
> >no-verify-ssl".
> >
> >Running RT 4.0.4 on Ubuntu.
> 
> That option wasn't introduced until 4.0.5, which is why ./bin/rt-mailgate --
> help wouldn't list it on your install.
> 
> -kevin

[rt-users] Setting us users for read only access

2012-05-09 Thread Zoedog 

I have a requirement to set up a select few users for read only access, what
is the best way to do that.
-- 
View this message in context: 
http://old.nabble.com/Setting-us-users-for-read-only-access-tp33763651p33763651.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

[rt-users] Reminders CSS

2012-05-09 Thread Eric O'Brien 
I have been trying to update the CSS for the overdue class so that any reminder 
that is overdue will show with a different background but unfortunately I have 
not been successful so far. Has anyone ever done this before or at least point 
me in the right direction? Thanks.

--
Eric O'Brien
System Administrator
BioReference Laboratories, Inc.
Phone: 201-791-2600 x 8310
Cell: 551-486-8925
Email: eobr...@bioreference.com
The information transmitted in this email and any of its attachments is 
intended only for the person or entity to which it is addressed and may contain 
BioReference Laboratories proprietary information, which is privileged, 
confidential, or subject to copyright belonging to BioReference Laboratories. 
Any review, retransmission, dissemination or other use of, or taking of any 
action in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited and may be unlawful. If you received this in 
error, please contact the sender immediately and delete and destroy the 
communication and all of the attachments you have received and all copies 
thereof.

Re: [rt-users] msmtp with RT 4.0.5 setup issues

2012-05-09 Thread Scott Sjodin 
Kevin,

I'm using an external mail server that's hosted, so I can't exactly check
those logs. I will check out the verbose logging and the client you
suggested and report back. Thank You.

On Wed, May 9, 2012 at 7:17 PM, Kevin Falcone wrote:

> On Wed, May 09, 2012 at 07:13:24PM +0400, Scott Sjodin wrote:
> > Msmtp is running, however, when I attempt to send mail thru a test (msmtp
> > -a default @domain.com) I get the following errors both in the
> > CLI and the log:
> >
> > msmtp: TLS handshake failed: the operation timed out
> > msmtp: could not send mail (account default from /etc/msmtprc)
>
> If msmtp has a verbose mode, use it.  Otherwise, your best bet is
> going to be the logs of the server you're trying to relay through.
>
> You can also use openssl's s_client command to try connecting to the
> relay server to check the tls connection.
>
> -kevin
>

Re: [rt-users] msmtp with RT 4.0.5 setup issues

2012-05-09 Thread Kevin Falcone 
On Wed, May 09, 2012 at 07:13:24PM +0400, Scott Sjodin wrote:
> Msmtp is running, however, when I attempt to send mail thru a test (msmtp
> -a default @domain.com) I get the following errors both in the
> CLI and the log:
> 
> msmtp: TLS handshake failed: the operation timed out
> msmtp: could not send mail (account default from /etc/msmtprc)

If msmtp has a verbose mode, use it.  Otherwise, your best bet is
going to be the logs of the server you're trying to relay through.

You can also use openssl's s_client command to try connecting to the
relay server to check the tls connection.

-kevin


pgpCjNHA5EqKf.pgp
Description: PGP signature

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Kevin Falcone 
On Wed, May 09, 2012 at 01:50:00PM +0200, Juanjo wrote:
>Yes, this parameter is OK (at 15MB, per default). But the fastcgi 
> parameter by default is only
>100k.

Yep, this is why I added
https://github.com/bestpractical/rt/commit/89c6750d4c87cfd65c5eaaec25928bb91ccfcb43
which will be in the docs for the next RT release.

-kevin

>2012/5/9 Ruslan Zakirov <[1]r...@bestpractical.com>
> 
>  mysql also has max_packet_size (spelling may be wrong).
> 


pgpBrxLxqGX51.pgp
Description: PGP signature

[rt-users] msmtp with RT 4.0.5 setup issues

2012-05-09 Thread Scott Sjodin 
Hi all,

Thanks to this community, I almost have RT fully up and operational.

The last step is getting msmtp to work. I'm not sure what's wrong and in
troubleshooting haven't gotten very far. As a guideline, I followed this
wiki page for instructions: http://requesttracker.wikia.com/wiki/Msmtp. I'm
using the default msmtprc file to simplify things.

Msmtp is running, however, when I attempt to send mail thru a test (msmtp
-a default @domain.com) I get the following errors both in the
CLI and the log:

msmtp: TLS handshake failed: the operation timed out
msmtp: could not send mail (account default from /etc/msmtprc)

For reference, my msmtprc file looks like this:

defaults
logfile /var/log/msmtp.log
account default
host smtp.mydomain.com
port 587
tls on
tls_certcheck off
tls_starttls off
auth on
user usern...@domain.com
password suparsekratpw
from usern...@domain.com
password suparsekratpw
auto_from on

Anybody have any tips or pointers? It would be greatly appreciated. Thanks
in advance.

Scott

Re: [rt-users] RT3 - login history recorded?

2012-05-09 Thread Schincke, Keith D. (JSC-IT)[DB Consulting Group, Inc.] 
Couldn't this be accomplished by increasing your log level from 'error' to 
'info'?
I think this would  login (and a lot of other activity) to your RT logging 
destination.

Keith Schincke CAP, LPIC-1, RHCA, RHCSS
Team Lead IT Security System Administration, ITAMS
Building 46, Room 110A
email to: keith.d.schin...@nasa.gov
281-244-0183 Office   832-205-1534 Mobile
281-244-5708 Fax

ITAMS - Information Technology And Multimedia Services Contract
"One Team, One Vision >> Partnered For Innovative Solutions"

From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Joseph Spenner
Sent: Wednesday, May 02, 2012 5:50 PM
To: RT- us...@lists.bestpractical.com
Subject: [rt-users] RT3 - login history recorded?

I'm using RT 3.8.8 and am curious whether RT records login history of users 
logging into the web interface.
?

Thanks!


If life gives you lemons, keep them-- because hey.. free lemons.

Re: [rt-users] StTicketPropertiesViaMail, valid for RT 4.0.5

2012-05-09 Thread Ruslan Zakirov 
On Wed, May 9, 2012 at 3:23 PM, Juanjo  wrote:
> Hi, again.
>
> I see this documentation:
> http://requesttracker.wikia.com/wiki/SetTicketPropertiesViaMail
>
> Are valid for RT 4.0.5? or are implemented in other way?

Looks still valid. Don't skip command by email thing mentioned. Many
things that are based on Scrips will work with newer versions.

> Thanks
> Regards.



-- 
Best regards, Ruslan.

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
Yes, this parameter is OK (at 15MB, per default). But the fastcgi parameter
by default is only 100k.

2012/5/9 Ruslan Zakirov 

> mysql also has max_packet_size (spelling may be wrong).
>
>
>


-- 
Un saludo.
Juanjo Corral

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Ruslan Zakirov 
On Wed, May 9, 2012 at 2:52 PM, Juanjo  wrote:
> :( Sorry for my obstination and impatience.
>
> I checked the apache log. If you use fastcgi, the upload limit are around
> 100k. You need to edit the vitualhost definition for RT with this.
>
>
>     
>    # 20MB should be enough
>    MaxRequestLen 2000
>     
>
> It permit upload files at least 20MB.
>
> Sorry for the all the emails sent without making standart tests.
> Kindest Regards.

mysql also has max_packet_size (spelling may be wrong).


>
>
>
> 2012/5/9 Juanjo 
>>
>> Yes.
>>
>> But i have some extra info.
>> In the time i can´t open ticket with attachment, the mysql is at 90% (or
>> more) of ram memory. I change my my.cnf to make mysql less ram hungry.
>>
>> But it donesn´t he problem, not works fine. I can´t upload if the file is
>> up than 100kb. I get an 500 internal server error. If the file is 24k works
>> fine for uopload, if is miore than 100k i cant upload it.
>>
>>
>>
>> 2012/5/9 Ruslan Zakirov 
>>>
>>> On Wed, May 9, 2012 at 10:52 AM, Juanjo  wrote:
>>> > Sorry :(
>>> >
>>> > From 3.6.5 to 4.0.5 on mysql.
>>>
>>> Have you followed UPGRADING.mysql instructions?
>>>
>>>
>>> >
>>> >
>>> >
>>> >
>>> > 2012/5/8 Ruslan Zakirov 
>>> >>
>>> >> On Tue, May 8, 2012 at 7:21 PM, Juanjo  wrote:
>>> >> > I finished migrate my old RT to new 4.0.5.
>>> >>
>>> >> From which version on what DB?
>>> >>
>>> >> --
>>> >> Best regards, Ruslan.
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Un saludo.
>>> > Juanjo Corral
>>>
>>>
>>>
>>> --
>>> Best regards, Ruslan.
>>
>>
>>
>>
>> --
>> Un saludo.
>> Juanjo Corral
>
>
>
>
> --
> Un saludo.
> Juanjo Corral



-- 
Best regards, Ruslan.

Re: [rt-users] Get realname or username from $requestor

2012-05-09 Thread Raed El-Hames 
Mario,

Have a look at Ticket/Elements/ShowRequestor to help you.
Basically get the Requestors list, these are members of a group that define the 
requestors of the ticket:
my $people = $Ticket->Requestors->UserMembersObj;

then go through the members to display the properties you want:
while ( my $requestor = $people->Next ) {
   my $name = $requestor->Name;
   my $realname = $requestor->RealName;
}

This is not tested, so I may have missed something, but pretty certain its 
along these lines.

Roy


>
Visit our website today www.daisygroupplc.com

Registered Office: Daisy House, Lindred Road Business Park, Nelson, Lancashire 
BB9 5SR
Company Registration Number: 4145329 |   VAT Number: 722471355
Daisy Communications Limited is a company registered in England and Wales.
DISCLAIMER

This email (including any attachments) is strictly confidential and may also be 
legally privileged. If the recipient has received this email in error please 
notify the sender and do not read, print, re-transmit, store or act in reliance 
on the email or its attachments and immediately delete this email and its 
attachments from the recipient's system. Daisy Communications Limited cannot 
accept liability for any breaches of confidence arising through use of email. 
Employees of Daisy Communications Limited are expressly required not to make 
any defamatory statements and not to infringe or authorise any infringement of 
copyright or any other legal right by email communications. Any such 
communication is contrary to the company's policy and outside the scope of the 
employment of the individual concerned. Daisy Communications Limited will not 
accept any liability in respect of such a communication, and the employee 
responsible will be personally liable for any damages or other liability 
arising.

If you are the intended recipient of this email please ensure that neither the 
email nor any attachments are copied to third parties outside your organisation 
or saved without the written permission of the sender.  In the event of any 
unauthorised copying or forwarding, the recipient will be required to indemnify 
Daisy Communications Limited against any claim for loss or damage caused by any 
viruses or otherwise.

WARNING: Computer viruses can be transmitted by email. The recipient should 
check this email and any attachments for the presence of viruses. Daisy 
Communications Limited accepts no liability for any damage caused by any virus 
transmitted by this email or any attachments.
NOTICE TO CUSTOMERS
If you have ordered a telephone number from Daisy Communications Limited 
(non-geographic or new line installation) please do NOT arrange for any form of 
advertising until the number is live and tested.


-Original Message-
> From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-
> boun...@lists.bestpractical.com] On Behalf Of Mario
> Sent: 09 May 2012 12:00
> To: rt-us...@lists.fsck.com
> Subject: [rt-users] Get realname or username from $requestor
>
> Hello,
> I am trying to use callbacks to customize Request Tracker.
>
> Specifically I would like to use the callback "aboutthisuser".
> I get $requestor as a parameter.
> I am a newbie so I do not know how to get realname or username from
> $requestor.
>
> Can you help me?
>
> Thanks in advance,
> Mario
>

[rt-users] StTicketPropertiesViaMail, valid for RT 4.0.5

2012-05-09 Thread Juanjo 
Hi, again.

I see this documentation:
http://requesttracker.wikia.com/wiki/SetTicketPropertiesViaMail

Are valid for RT 4.0.5? or are implemented in other way?

Thanks
Regards.

[rt-users] Get realname or username from $requestor

2012-05-09 Thread Mario 
Hello,
I am trying to use callbacks to customize Request Tracker.

Specifically I would like to use the callback "aboutthisuser".
I get $requestor as a parameter.
I am a newbie so I do not know how to get realname or username from $requestor.

Can you help me?

Thanks in advance,
Mario

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
:( Sorry for my obstination and impatience.

I checked the apache log. If you use fastcgi, the upload limit are around
100k. You need to edit the vitualhost definition for RT with this.



   # 20MB should be enough
   MaxRequestLen 2000


It permit upload files at least 20MB.

Sorry for the all the emails sent without making standart tests.
Kindest Regards.


2012/5/9 Juanjo 

> Yes.
>
> But i have some extra info.
> In the time i can´t open ticket with attachment, the mysql is at 90% (or
> more) of ram memory. I change my my.cnf to make mysql less ram hungry.
>
> But it donesn´t he problem, not works fine. I can´t upload if the file is
> up than 100kb. I get an 500 internal server error. If the file is 24k works
> fine for uopload, if is miore than 100k i cant upload it.
>
>
>
> 2012/5/9 Ruslan Zakirov 
>
>> On Wed, May 9, 2012 at 10:52 AM, Juanjo  wrote:
>> > Sorry :(
>> >
>> > From 3.6.5 to 4.0.5 on mysql.
>>
>> Have you followed UPGRADING.mysql instructions?
>>
>>
>> >
>> >
>> >
>> >
>> > 2012/5/8 Ruslan Zakirov 
>> >>
>> >> On Tue, May 8, 2012 at 7:21 PM, Juanjo  wrote:
>> >> > I finished migrate my old RT to new 4.0.5.
>> >>
>> >> From which version on what DB?
>> >>
>> >> --
>> >> Best regards, Ruslan.
>> >
>> >
>> >
>> >
>> > --
>> > Un saludo.
>> > Juanjo Corral
>>
>>
>>
>> --
>> Best regards, Ruslan.
>>
>
>
>
> --
> Un saludo.
> Juanjo Corral
>



-- 
Un saludo.
Juanjo Corral

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
Yes.

But i have some extra info.
In the time i can´t open ticket with attachment, the mysql is at 90% (or
more) of ram memory. I change my my.cnf to make mysql less ram hungry.

But it donesn´t he problem, not works fine. I can´t upload if the file is
up than 100kb. I get an 500 internal server error. If the file is 24k works
fine for uopload, if is miore than 100k i cant upload it.


2012/5/9 Ruslan Zakirov 

> On Wed, May 9, 2012 at 10:52 AM, Juanjo  wrote:
> > Sorry :(
> >
> > From 3.6.5 to 4.0.5 on mysql.
>
> Have you followed UPGRADING.mysql instructions?
>
>
> >
> >
> >
> >
> > 2012/5/8 Ruslan Zakirov 
> >>
> >> On Tue, May 8, 2012 at 7:21 PM, Juanjo  wrote:
> >> > I finished migrate my old RT to new 4.0.5.
> >>
> >> From which version on what DB?
> >>
> >> --
> >> Best regards, Ruslan.
> >
> >
> >
> >
> > --
> > Un saludo.
> > Juanjo Corral
>
>
>
> --
> Best regards, Ruslan.
>



-- 
Un saludo.
Juanjo Corral

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
The internal errors occur if i use other language than english. I thin that
i open new cuestion about it.

2012/5/9 Juanjo 

>
>
> 2012/5/9 Juanjo 
>
>> I think i know what are the problem.
>>
>> Mysql are using all the ram memory, when this happend doesn´t accept
>> attachment (per email or per uploading to ticket).
>>
>> Other thing, On Chrome when i upload a attachment i get a 500 internal
>> server error. With IE or Firefox doesn´t occur.
>>
>>
>> 2012/5/9 Juanjo 
>>
>>> Sorry :(
>>>
>>> From 3.6.5 to 4.0.5 on mysql.
>>>
>>>
>>>
>>>
>>> 2012/5/8 Ruslan Zakirov 
>>>
 On Tue, May 8, 2012 at 7:21 PM, Juanjo  wrote:
 > I finished migrate my old RT to new 4.0.5.

 From which version on what DB?

 --
 Best regards, Ruslan.

>>>
>>>
>>>
>>> --
>>> Un saludo.
>>> Juanjo Corral
>>>
>>
>>
>>
>> --
>> Un saludo.
>> Juanjo Corral
>>
>
>
>
> --
> Un saludo.
> Juanjo Corral
>



-- 
Un saludo.
Juanjo Corral

Re: [rt-users] Can not open ticket with attachment on 4.0.5

2012-05-09 Thread Juanjo 
2012/5/9 Juanjo 

> I think i know what are the problem.
>
> Mysql are using all the ram memory, when this happend doesn´t accept
> attachment (per email or per uploading to ticket).
>
> Other thing, On Chrome when i upload a attachment i get a 500 internal
> server error. With IE or Firefox doesn´t occur.
>
>
> 2012/5/9 Juanjo 
>
>> Sorry :(
>>
>> From 3.6.5 to 4.0.5 on mysql.
>>
>>
>>
>>
>> 2012/5/8 Ruslan Zakirov 
>>
>>> On Tue, May 8, 2012 at 7:21 PM, Juanjo  wrote:
>>> > I finished migrate my old RT to new 4.0.5.
>>>
>>> From which version on what DB?
>>>
>>> --
>>> Best regards, Ruslan.
>>>
>>
>>
>>
>> --
>> Un saludo.
>> Juanjo Corral
>>
>
>
>
> --
> Un saludo.
> Juanjo Corral
>



-- 
Un saludo.
Juanjo Corral