Roundcube not working after update

ezh

Verified User
Joined
Jun 13, 2019
Messages
23
Updated Roundcube via GUI

Now I see on the URL Roundcube used to be:

FILE NOT FOUND​

The requested resource was not found!
Please contact your server-administrator.

How could it be fixed?

Tnx

-------------------------

Update log:
download_with_cache: downloading 'https://github.com/roundcube/roundc...oad/1.6.3/roundcubemail-1.6.3-complete.tar.gz' to '/usr/local/directadmin/custombuild/cache/roundcubemail-1.6.3-complete.tar.gz'
#=#=# ##O#-# ##O=# # /usr/local/mysql/bin/mysqlshow: Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Inserting data to mysql and creating database/user for roundcube...
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Found MySQL version 10.6
Creating User: CREATE USER 'da_roundcube'@'localhost' IDENTIFIED BY 'vDjIZB1F9LPoVPs';
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Granting access: GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,ALTER,LOCK TABLES,INDEX,REFERENCES ON da_roundcube.* TO 'da_roundcube'@'localhost';
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Setting password: ALTER USER 'da_roundcube'@'localhost' IDENTIFIED BY 'vDjIZB1F9LPoVPs';
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
Database created, da_roundcube password is vDjIZB1F9LPoVPs
Editing roundcube configuration...
Installing custom RoundCube Config: /usr/local/directadmin/custombuild/custom/roundcube/config.inc.php
Roundcube 1.6.3 has been installed successfully.
WARNING: Replaced config options:
(These config options have been replaced or renamed)
- 'default_host' was replaced by 'imap_host'
- 'smtp_server' was replaced by 'smtp_host'
Do you want me to fix your local configuration? (y/N)
Please update your config files manually according to the above messages.
WARNING: Changed defaults (These config options have new default values):
- 'skin'
- 'smtp_port'
- 'smtp_user'
- 'smtp_pass'
- 'jquery_ui_skin_map'
Executing database schema update.
Indexing contacts for user 1...
Indexing contacts for user 2...
Indexing contacts for user 12...
Indexing contacts for user 21...
Indexing contacts for user 22...
Indexing contacts for user 23...
Indexing contacts for user 27...
Indexing contacts for user 29...
Indexing contacts for user 30...
Indexing contacts for user 31...
Indexing contacts for user 32...
Indexing contacts for user 33...
done.
This instance of Roundcube is up-to-date.
Have fun!
 
You can do what @Zhenyapan says, but probably you have to do it in another way so the symlink will be re-created after a reboot.
Otherwise you will have the same issue after reboot.
Check this thread (click) for the whole store, this was a fresh install. It's the reason I asked if you ran Debian.

I had a hard time with this on Debian 11 on a new install and only after 3 times reinstall, the error did not occur anymore.

I also needed a very little my.cnf and I don't try to change it, afraid things will go wrong again.
Code:
[mysqld]
max_allowed_packet=64M
local-infile=0
innodb_file_per_table

[client]
socket=/usr/local/mysql/data/mysql.sock

There are 0 exclusions in Debian, while there are many in Centos/RHEL's package manager, which seems very odd to me to begin with.
Also now I suddenly got some mariadb-common and libmariadb3 update problem while I never had installed that. So now I created a snapshot and uninstalled and removed those too.
 
By me all works besides Roundcube, but now I'm afraid to update anything again...
 
By me all works besides Roundcube
I'm afraid not. Try to make a backup via DA and you will see it most likely will fail due to the same reason.

The solution @Zhenyapan posted to make a symlink, will fix the situation for now and updates can be made and backups too.
Just be aware that the symlink might be gone after a server/vps reboot.
So you might need to create it then again or find a more definate solution to automatically have it created on reboot.
 
Back
Top