Owncloud problem 503 after Extend Disk Space

I have extended disk space on my univention server and after this action owncloud server wrote this error:
503 Service Unavailable

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.4.25 (Univention) Server at ( mydomain.local ) Port 443
Can you help me, please?

this problem has been described here:

but there was no solution described. Only:
"Hi, the problem was with mariadb. My friend has help me with this problem. Thank you. "

logging in owncloud.log does not occur from the moment the problem occurs


is the database lib on the same directory as the files for ownCloud ? Was the partition full ? Then it could be your MySQL that went broken once reached 100% of free space. Do you have free space for MySQL and the ownCloud files now ?

Could you increase the verbosity of ownCloud ? Do you have any error in the MySQL error log ? Have you also checked the log of your webserver ?

1 Like

2019-09-02 17:15:00 139773545258368 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: The InnoDB memory heap is disabled
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Using Linux native AIO
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Using SSE crc32 instructions
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Initializing buffer pool, size = 150.0M
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Completed initialization of buffer pool
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Highest supported file format is Barracuda.
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Starting crash recovery from checkpoint LSN=159974470449
2019-09-02 17:15:00 139773545258368 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
2019-09-02 17:15:01 139773545258368 [Note] InnoDB: 128 rollback segment(s) are active.
2019-09-02 17:15:01 139773545258368 [Note] InnoDB: Waiting for purge to start
2019-09-02 17:15:01 7f1f69bff700 InnoDB: Assertion failure in thread 139772894902016 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190902 17:15:01 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https:/ /mariadb. com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.38-MariaDB-0+deb9u1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352467 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 0x0 thread_stack 0x30000
The manual page at http:/ /dev .mysql. com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Well, sadly your MySQL is broken. I’d suggest you backup already all the MySQL lib directory, and follow the documentation to try to restore it.

1 Like

I used this guide

in step three, after the command:
mysql -u root -p <mysql.dump
I got an error:
ERROR 1036 (HY000) at line 89: Table ‘entries’ is read only
(maybe someone can explain its cause, for future generations =)
further actions probably led to the complete collapse of the database.
My solution of the problem was a complete rollback of the virtual machine.

error 503 may cause a problem with the tc.log file
In the logs, it looks like:
[Note] InnoDB: Dumping buffer pool (s) not yet started
[Note] Recovering after a crash using tc.log
[ERROR] Can’t init tc log
[ERROR] Aborting
The solution is simple:
delete the file /var/lib/mysql/tc.log
and run command
systemctl restart mariadb

1 Like