Jump to content

Internal Server error when using BackOffice


Recommended Posts

I get a lot of "Internal Server Error" pages when I click on the Catalog tab of the back office. It has happened on two installations.

The first thing I did was to delete the demo products and categories, and it immediately happens whenever I delete everything in a group. Might this be bad?

However, it happens intermittently on anything related to the Product catalogue. It often sorts itself out after refreshing the page; though sometimes you have to leave it for 30 seconds or so.

Is this normal....?

Link to comment
Share on other sites

Further to this:

I'm getting the following log message in cgierrors.log:

file: unrecognized option `--mime-type'
Usage: file [-bcikLnNsvz] [-f namefile] [-F separator] [-m magicfiles] file...
      file -C -m magicfiles
Try `file --help' for more information.



The two seem to be related, as whenever I get the 500 error, the log files gets updated with one of these.

Link to comment
Share on other sites

Bump. No one else knows about this?

I presume that it's not normal, then.

Curious that it's happened on two installations: one done manually, and another by Softaculous, a script installer.

So it's probably something else that's causing the problem. Might deleting all the demo data cause a problem with the database?

Any way of fixing a database?

Link to comment
Share on other sites

  • 1 month later...
Apparently, changing the file attributes of various files in the affected modules to 655 (instead of 755) seems to fix this.


I have the same problem, what modules you're talking about ?

Thanks.

[EDIT] SOLVED : This is a typo in /images.inc.php : line 80 (Presta 1.2.5) or 82 (Presta 1.3.1) : 'file -b --mime ' instead of 'file -b --mime-type '
Link to comment
Share on other sites

  • 8 months later...

Correcting the error in images.inc.php doesn't seem to help.

I'll try changing the file permissions, though I can't understand why the owner should not have the execute bit set, when everybody else does!

(I seem to remember being told to set lots of things to 755 when I first installed PS, in order to correct some other bug....!)

Link to comment
Share on other sites

You have to check exactly the syntax of the 'file' command on your Linux system. Open a console an type 'file' or 'file --help' and search what argument is related to the mime type.


You mean on the Linux system of the server that hosts my website, surely? How on earth am I supposed to run shell commands on that?
From the log message quoted in my second post, it looks like the server doesn't use the --mime option at all. I'll try -I.

Can whoever changed this thread's title to SOLVED please not do so until the suggestions here have been proved to work for the original post (i.e. mine). Thanks.
Link to comment
Share on other sites

You mean on the Linux system of the server that hosts my website, surely? How on earth am I supposed to run shell commands on that?


Some providers allow to do this. This is a connection to the server through SSH via Putty if your client is Windows.

If you can't do this, make a .php file and do some tests using 'file' with the '—mime' option and see if you always have the error message.

Another solution is to run 'file --help' through PHP, the error message should contain the help of the file command.
Link to comment
Share on other sites

I'll have to get in touch with my ISP. But from the options given in the log error, it doesn't look as though their version of file supports any of the mime typing options.

The other error message I get in cgierror.log relates to a "Stale NFS handle" on category-tree-branch.tpl.php.

I suppose that the "easiest" thing would be to update to Prestashop 1.4, but I just know that will take a good couple of days to install and sort out, and I don't have the time right now.

Link to comment
Share on other sites

"Stale NFS handle". So there's perhaps another problem related to the file system of the server and then the 'file" command fail. You should report this "Stale NFS handle" message to your provider to solve it first.

Link to comment
Share on other sites

×
×
  • Create New...