500 internal server error owncloud



500 Internal server error accessing /owncloud/remote.php/caldav/calendars/brian/defaultcalendar/ #25381

Comments

brianjmurrell commented Jul 6, 2016

Steps to reproduce

Expected behaviour

I shouldn’t get 500 errors from caldav backend

Actual behaviour

I get a 500 Internal server error

Server configuration

Operating system:
Linux

Web server:
Apache

Database:
MySQL/MariaDB

PHP version:
5.4.16

ownCloud version: (see ownCloud admin page)
9.0.2

Updated from an older ownCloud or fresh install:
Updated from 8.2.x

Where did you install ownCloud from:
EPEL

Signing status (ownCloud 9.0 and above):
Integrity checker has been disabled. Integrity cannot be verified.

List of activated apps:
Enabled:

  • activity: 2.2.1
  • calendar: 1.2.2
  • comments: 0.2
  • contacts: 1.3.1.0
  • dav: 0.1.6
  • federatedfilesharing: 0.1.0
  • federation: 0.0.4
  • files: 1.4.4
  • files_pdfviewer: 0.8.1
  • files_sharing: 0.9.1
  • files_texteditor: 2.1
  • files_trashbin: 0.8.0
  • files_versions: 1.2.0
  • files_videoplayer: 0.9.8
  • firstrunwizard: 1.1
  • gallery: 14.5.0
  • notifications: 0.2.3
  • provisioning_api: 0.4.1
  • systemtags: 0.2
  • templateeditor: 0.1
  • user_ldap: 0.8.0
    Disabled:
  • encryption
  • external
  • files_external
  • user_external

The content of config/config.php:
<
«system»: <
«log_type»: «owncloud»,
«datadirectory»: «/var/lib/owncloud/data»,
«updatechecker»: false,
«check_for_working_htaccess»: false,
«asset-pipeline.enabled»: false,
«assetdirectory»: «/var/lib/owncloud»,
«apps_paths»: [
<
«path»: «/usr/share/owncloud/apps»,
«url»: «/apps»,
«writable»: false
>,
<
«path»: «/var/lib/owncloud/apps»,
«url»: «/apps-appstore»,
«writable»: true
>
],
«instanceid»: «xxx»,
«passwordsalt»: «_REMOVED SENSITIVE VALUE«,
«secret»: «_REMOVED SENSITIVE VALUE
«,
«trusted_domains»: [
«owncloud.example.com»,
«www.example.com»
],
«overwrite.cli.url»: «http://owncloud.example.com/owncloud»,
«dbtype»: «mysql»,
«dbname»: «owncloud»,
«dbhost»: «linux.example.com»,
«dbuser»: «_REMOVED SENSITIVE VALUE«,
«dbpassword»: «_REMOVED SENSITIVE VALUE
«,
«version»: «9.0.2.2»,
«installed»: true,
«theme»: «»,
«maintenance»: false,
«forcessl»: false,
«loglevel»: 1,
«log_authfailip»: true,
«mail_from_address»: «owncloud»,
«mail_smtpmode»: «smtp»,
«mail_domain»: «example.com»,
«mail_smtphost»: «smtp.example.com»,
«trashbin_retention_obligation»: «auto»
>
>

Are you using external storage, if yes which one: local/smb/sftp/.
No

Are you using encryption: yes/no
No

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/.
No

Client configuration

Browser:
N/A

Operating system:
Linux

Источник

Internal Server error 500 #8414

Comments

colinpeak commented Apr 30, 2014

I have a user who has their own owncloud account. Currently this is set to sync on both the server and onto the clients computer. At present the servers owncloud is syncing correctly without any issues but when the clients computer loads owncloud after 10 minutes an error reporting «1060 happened, internal server error 500».

I have looked into other tickets and I can see the some say restart the ownclouds IIS service which has been completed and produced the same error.

The windows client version used is version 1.5.4

Server operating system — Windows

Owncloud version — 6.0.2

The text was updated successfully, but these errors were encountered:

DeepDiver1975 commented Apr 30, 2014

@colinpeak Thanks a lot for reporting issues back to us!

We need some more information to properly support you with your issue!

Can I ask you to follow our guidelines for submitting bugs as described here: https://github.com/owncloud/core/blob/master/CONTRIBUTING.md

colinpeak commented Apr 30, 2014

Steps to reproduce

  1. Setup owncloud with the same user details on 2 different computers.
  2. set one to download the data and one to download the data from the cloud.
  3. This replicates when we create a new user.

Expected behaviour

The files should sync between both the server and computer.

Actual behaviour

The server uploads but errors on the local computer error 500.

Server configuration

Windows server 2008 r2

Web server:
IIS
Database:

Источник

Internal Error 500 #21869

Comments

bkerensa commented Jan 24, 2016

Steps to reproduce

Expected behaviour

Tell us what should happen

Читайте также:  Bb error rom image layout detected romhole is redesigned

Actual behaviour

Tell us what happens instead

Server configuration

Operating system: Ubuntu Server

Web server: Apache

Database: MySQL

PHP version: 5.6

ownCloud version: (see ownCloud admin page)
8.2.2

Updated from an older ownCloud or fresh install:
Updated from 8.1.5

Signing status (ownCloud 9.0 and above):

List of activated apps:

Are you using external storage, if yes which one: local/smb/sftp/.

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/.

LDAP configuration (delete this part if not used)

Client configuration

Browser: Chrome

Operating system: OSX

Web server error log

ownCloud log (data/owncloud.log)

This is most recent so there is nothing helpful as to why this error is happening

Browser log

The text was updated successfully, but these errors were encountered:

bkerensa commented Jan 24, 2016

Mind you nothing has been changed and my owncloud install has been up solid for over a year now but all of a sudden this week I got to access it and I get this 500 error and I notice another user has the same issue as me:
https://forum.owncloud.org/viewtopic.php?f=36&t=32660

My only guess is cron or something that usually runs broke something in the install but the lack of useable logs is not helping me find out what

DeepDiver1975 commented Jan 24, 2016

Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set ‘always_populate_raw_post_data’ to ‘-1’ in php.ini and use the php://input stream

please fix this — THX

bkerensa commented Jan 24, 2016

That shouldn’t be causing a 500 error in a build that still supports it and that said for most folks on a shared platform always_populate_raw_post_data is going to be on.

ghost commented Jan 24, 2016

a first starting point would be to research what was changed within your environment to get to this state (ownCloud itself won’t magically damage itself or its files so there must be changed something, even an update of PHP or something).

As the cron.php is mentioned you should check your cron settings and php-cli environment which is executing that file.

The always_populate_raw_post_data should be also fixed on your side as already suggested. I think the message is not there just for fun.

ghost commented Jan 24, 2016

Ah, as both of you have the «File does not exist: /home/xxx/owncloud.xxx/ownCloud/internal_error.html» message in your logfile you’r probably both are on the same shared hoster?

If yes then it should be obvious that your hoster probably changed something in their environment which is causing those issues.

Have you considered contacting the support of your hoster about that issue?

bkerensa commented Jan 24, 2016

No we’re not on the same hosted and others have had this too look on forums. Nothing has changed my provider tailed their logs and it’s OC install that’s busted.

ghost commented Jan 24, 2016

So you’re saying you both are not on the same hoster but have the same uncommon ‘internal_error.html’ in your logfiles? Or do you just have copied over the logfiles of the other user in here?

Читайте также:  Error reading file in oracle

How are you sure that nothing changed?

bkerensa commented Jan 24, 2016

I just said in the comment above that my host investigated. We have other OC installs on the same server that are low major version and still chugging along fine.

ghost commented Jan 24, 2016

Please answer the questions above

bkerensa commented Jan 24, 2016

Im not in any position to explain someone else’s setup. That said I’ve supplied the necessary info for the template of an actual OC dev wants more info I’ll provide it.

ghost commented Jan 24, 2016

I’m just asking you to answer this:

So you’re saying you both are not on the same hoster but have the same uncommon ‘internal_error.html’ in your logfiles? Or do you just have copied over the logfiles of the other user in here?

If both of your hosters have the same environment like Plesk for example then such issues can be caused by an upgrade of such components. Also webhosters tend to say «we havn’t changed anything» even if they have changed something.

bkerensa commented Jan 24, 2016

I don’t know what part of I can’t tell you what kind of environment another user that I do not know is on.

Maybe ask him? He isn’t on my host that’s all I know and I know because I trace routed his hostname.

ghost commented Jan 24, 2016

This is not about the environment of the other user. I’m just asking you if that are the logfiles of your server you have posted here or if you have copied from the logfiles of the other user in the forum thread?

If those are your logfiles we can ask the user at the forum if he can ask the support of this hoster because:

  • You have both the same uncommon internal_error.html message in your logfiles
  • Both of your instances stopped to work out of the blue with the Premature end of script headers: error

bkerensa commented Jan 24, 2016

Why would I post someone else’s log files ? Yes they are mine

ghost commented Jan 24, 2016

Just to be sure. I have seen a lot of things in the last 2 years since i’m giving support at the forums.

Just have asked the other user at the forums to contact his hoster. Maybe they can provide more info/insights.

ghost commented Jan 24, 2016

Cross-Posting from the linked forums post:

I just found out what changed. DreamHost added zend_extension=opcache.so to my phprc file. I removed that line and the site works fine.

Woo Hoo. unintended consequences of a dreamhost modification

bkerensa commented Jan 24, 2016

So first off I do have one instal as I mentioned above that works fine on dreamhost and I just checked and yep opcode is there.

That said according to OwnCloud doc opcode should be supported so someone might want to file a bug about that.

On the OwnCloud instance that’s 500 erroring is on a different provider Arivxe and opcode is not set in phprc.

MorrisJobke commented Jan 25, 2016

This is clearly nothing the bug tracker is for. This seems to be a setup issue. Please try to figure out what the cause of this is.

Читайте также:  Ошибка runtime error this application has requested the runtime to terminate

Once you know which setting/feature/setup is not compatible with owncloud you can report a bug here, but this just seems to be a setup issue and we as owncloud developers can’t do much here.

I will close this because it lacks the essential information of how to reproduce the issue.

bkerensa commented Jan 25, 2016

@MorrisJobke Actually the information is there and basically if a server has Zend opcache enabled it then OC breaks. According to doc this form of caching is supported so this is a bug.

I checked my phprc on a different host and the same issue caused it and so I would encourage reopening this and editing the title and queuing it to be worked on.

RobinMcCorkell commented Jan 25, 2016

@bkerensa Zend Opcache works fine for most people, myself included. Given that we have seen 2 instances of a broken ownCloud due to this issue, out of likely many hundreds of thousands of installations, I’d say it’s a specific environment issue, and you’re better off getting help from the forums or other support channels.

bkerensa commented Jan 25, 2016

Looking at logs the breakage happened on first cron run after I upgraded to 8.2.2 so perhaps a regression? I mean its your project if it were mine and I do run open source projects myself I would definitely investigate it more versus write it off to forums or a environment issue.

If you think its environment then ask for more info to rule that out. But again its your call and if it is a regression I guess you will see more of these reports come up.

MorrisJobke commented Jan 25, 2016

@MorrisJobke Actually the information is there and basically if a server has Zend opcache enabled it then OC breaks. According to doc this form of caching is supported so this is a bug.

Nearly all instances I’m aware of use Zend opcache and all work fine 🙁 Sadly it seems to be really hard to reproduce.

We are also not aware of any issues on Ubuntu (especially the LTS versions). The packages there just work. Maybe you have some other hints what is different on those systems. If this is not possible, we can’t do much. We always try to investigate, but if this doesn’t show any hints what it could be there is not much we can do.

@bkerensa Where is this «internal_error.html» coming from?

ghost commented Jan 26, 2016

There is a third instance showing issues with opcache but with a different error (400): #21876

bkerensa commented Jan 26, 2016

ghost commented Jan 30, 2016

Getting more reports about that:

ghost commented Feb 4, 2016

lock bot commented Aug 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Оцените статью
toolgir.ru
Adblock
detector