Hi Hugh,
it could be many different things which are cached. You can try to get a
backtrace to see where exactly the error occurred. Is this on beta4?
Errors of this kind (byte order not compatible) should not occur any
more (possibly only with old caching data).
Regards, mg
Am 29.09.10 13:08, s
Hi Hugh,
I believe you can change the default screen with
"Frontend::CommonParam###Action".
Best regards, mg
Am 29.09.10 10:55, schrieb Hugh Kelley:
> There is only one machine in use here. I will assume now that the
> large attachment is just a coincidence.
>
> Whatever the issue is, it seems
I think this was related to a change in the number of CPUs on my virtual
machine. I had reduced my VM to one CPU (but of the same type) so as to
simplify the configuration and address the time zone drift issue I am seeing
(another thread).
After running the bin\otrs.DeleteCache.pl script it seems
I forgot to mention that I did run the delete cache script yesterday,
no effect.
I only assumed this was cache-related because of the text in the
PerlEx error. Apparently that is incorrect.
Regards,
Hugh
On 9/29/10, Hugh Kelley wrote:
> There is only one machine in use here. I will assume no
There is only one machine in use here. I will assume now that the
large attachment is just a coincidence.
Whatever the issue is, it seems to have affected /crippled the
dashboard view for many, but not all, staff.
While I find the root cause, is there an easy way to change the
default "screen" g
Hi Hugh,
do you have different machines runnint OTRS sharing some data? That's
what the byte order message would indicate. However, we fixed the
problem by generating architecture-independent cache files (in beta3 or
4, not sure right now). Please run bin/otrs.DeleteCache.pl to clean up
the old ca
Digging into this a bit further I decided to try exporting the attachments
out of the DB and onto the FS. I used the following command line.
perl.exe \OTRS\otrs-3.0.0\bin\otrs.ArticleStorageSwitch.pl -s
ArticleStorageDB -d ArticleStorageFS
This yielded many instances of this error message.
ER
A user sent a large screenshot into OTRS today (3.0 Beta 3) and it seems
(based on the coincidental timing) to have caused an issue with the
dashboard.
I now get these "Byte order is not compatible at ..\..\lib\Storable.pm "
messages in the PerlEx logs (see further down). The web server just retu
