Error connecting to database: SQLSTATE[28000] [1045] Access denied for user 'roundcube'@'localhost'

Paul Boddie paul at boddie.org.uk
Tue Sep 2 16:09:53 CEST 2014


On Tuesday 2. September 2014 15.05.15 you wrote:
> Hi,
> all setup python libs reside in the /usr/share/pyshared/pykolab/setup dir.
> So, setup_roundcube.py e.g runs this:
>  schema_files = []
>     for root, directories, filenames in os.walk('/usr/share/doc/'):
>         for directory in directories:
>             if directory.startswith("roundcubemail"):
>                 for root, directories, filenames in
> os.walk(os.path.join(root, directory)):
>                     for filename in filenames:
>                         if filename.startswith('mysql.initial') and
> filename.endswith('.sql'):
>                             schema_filepath = os.path.join(root,filename)
>                             if not schema_filepath in schema_files:
>                                 schema_files.append(schema_filepath)
> 
>                 break
>         break

I'm still not sure that this code is actually functional on Debian, but I 
don't remember which bug was tracking this now. Various Roundcube resources 
reside in different directories under /usr/share/doc as I recall, and there 
were some things that weren't getting found and executed in code resembling 
the above.

> So try to run the sql files in /usr/share/doc/roundcube or try to run
> the setup_roundcube.py.
> Or start over the whole installation by removing the kolab debs and
> dependency and the purge the configs.

Starting over may not help because you'll end up running the same code. 
Perhaps changing the setup_roundcube.py file and running setup-kolab or the 
relevant package configuration script might work. The issue of persuading the 
Debian/Ubuntu packaging that everything is now configured might also be a 
problem, but you could always modify the script (in /var/lib/dpkg/info/ 
somewhere) to exit with a suitable status: that's the hack I've used to fix 
bad packages before now.

Of course, the proper solution is to fix the packaging, but we're at something 
of an impasse there at the moment.

Paul


More information about the users mailing list