General Error: 14 after uploading files


#1

Owncloud was running, I was uploading files to store and share them. Then a pop up came saying, that some of the files had another file size than expected. I closed this pop up and wanted to leave the folder and navigate somewhere else, but obviously the entire installation crashed with this error message: Exception occurred while logging exception: Failed to connect to the database: An exception occurred while executing ‘PRAGMA journal_mode = WAL’: SQLSTATE[HY000]: General error: 14 unable to open database file

Steps to reproduce

  1. Can not log in.

Expected behaviour

Log in (or anything).

Actual behaviour

I get this error message: Exception occurred while logging exception: Failed to connect to the database: An exception occurred while executing ‘PRAGMA journal_mode = WAL’: SQLSTATE[HY000]: General error: 14 unable to open database file

And obviously a list of files, which can’t connect.

Server configuration

Operating system: Hosted on 1&1, don’t know more details

Web server: Hosted on 1&1, don’t know more details

Database: Standard database with standard installation

PHP version: 7.0

ownCloud version: (see ownCloud admin page) 10.0.3.3

Updated from an older ownCloud or fresh install:

Where did you install ownCloud from:

Signing status (ownCloud 9.0 and above): ?

Login as admin user into your ownCloud and access 
http://example.com/index.php/settings/integrity/failed 
paste the results into https://gist.github.com/ and puth the link here.

Not possible

The content of config/config.php:
<?php
$CONFIG = array (
‘instanceid’ => ‘(instance-ID)’,
‘passwordsalt’ => ‘(password)’,
‘secret’ => ‘(secret)’,
‘trusted_domains’ =>
array (
0 => ‘URL’,
),
‘datadirectory’ => ‘(home directory)/htdocs/owncloud/data’,
‘overwrite.cli.url’ => ‘(URL)’,
‘dbtype’ => ‘sqlite3’,
‘version’ => ‘10.0.3.3’,
‘installed’ => true,
‘theme’ => ‘(home directory)/htdocs/owncloud/themes/mytheme’,
‘maintenance’ => false,
‘mail_smtpmode’ => ‘smtp’,
‘mail_smtpsecure’ => ‘ssl’,
‘mail_from_address’ => ‘server’,
‘mail_domain’ => ‘(domain)’,
‘mail_smtphost’ => ‘smtp.1und1.de’,
‘mail_smtpport’ => ‘465’,
‘mail_smtpauth’ => 1,
‘mail_smtpname’ => ‘(email address)’,
‘mail_smtppassword’ => ‘(password)’,
‘mail_smtpauthtype’ => ‘NTLM’,
‘loglevel’ => 2,
‘trashbin_retention_obligation’ => ‘auto’,
);

Generate: Config Report => Not possible
Command line: Not possible

Are you using encryption: yes, SSL encrypted connection

Are you using an external user-backend, if yes which one: No

Client configuration

Browser: Chrome 67

Operating system:
Windows 10 Pro 64Bit

Logs

Web server error log

Insert your webserver log here

ownCloud log (data/owncloud.log)

Insert your ownCloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log 
c) ...

#2

Hey,

this looks quite outdated to me. I think it could worth to update to the latest 10.0.8 to see if this fixes your issue.

I have also read somewhere in the documentation that depending on the usage MySQL or PostgreSQL should be used instead of SQLite which could also be another solution.


#3

Hey Tom,

Thanks for your reply and the hints. But how can I get this done? At the current state I can’t do anything, where I need Owncloud to work.

Thanks!


#4

Mhhh, i’m not sure if there is anything what you can do in the current state. From what i understand from the posted error the database file of ownCloud is either inaccessible (maybe corrupt?) or has vanished.


#5

Hi Tom,

The file is there, so it must be corrupted. But how can it become corrupt by just uploading files?

Thanks!
Simeon


#6

Check also the permissions over the DB file: the apache user (www-data?) will need to read and write the DB.

If that isn’t it, I guess you’ll probably need to google around. It’s pretty clear that ownCloud can’t access to the DB.

  • Wrong permissions might also cause this problem. This should be easy to verify.
  • If the permissions are right, the file might be corrupted. Verify you can (or not) connect to the DB using another client, probably sqlite3
  • If the file is really corrupted, you might want to google how to recover the file (if it’s possible)

#7

Hi Everyone,

I actually did the update thing, and it worked, so I’m back online.

Thanks a lot!