Server connect failed after upgrade to 1.6.0

8 posts / 0 new
Last post
sq3htx
Server connect failed after upgrade to 1.6.0

I use cqrlog with Ubuntu 13.04, it worked fine until last update to 1.6.0. Now I get a message "Error during connection to database: Server connect failed." I no longer see any of my databases. What can be wrong?

Marek SQ3HTX

ok2cqr
ok2cqr's picture
Re: Server connect failed after upgrade to 1.6.0

Hi Marek,

are you using cqrlog and database on local machine? Do you have Save log data to local machine checked?
It could help, if you delete ~/.config/cqrlog/cqrlog_log.cfg file. ~ means your home directory.

73 Petr, OK2CQR

sq3htx
Re: Server connect failed after upgrade to 1.6.0

Yes, I use the cqrlog on a local machine and this option is selected, nothing changed during upgrade. I removed the config file but it didn't help.

Marek SQ3HTX

f4gwh
f4gwh's picture
Server connect failed after upgrade to 1.6.0

I have the same issue with ubuntu 12.10 (despite this thanks for your great software!)
best 73's Emmanuel - F4GWH

Station operating QRP only!

ok2cqr
ok2cqr's picture
Re: Server connect failed after upgrade to 1.6.0

Hi Mark and Emanuel,

could you run cqrlog from command line, please?

cqrlog --debug=2 > debug.log

and please send me the debug.log file. Thanks a lot!

73 Petr, OK2CQR

f4gwh
f4gwh's picture
Server connect failed after upgrade to 1.6.0

Hi Petr,
Debug.log file sent to your mailbox.
Thanks a lot!
73 Emmanuel

Station operating QRP only!

UA6CEY
Hi Petr!

Hi Petr!
I have the same problem with 1.6.0 starting with local database.
The only way to start it is (manually) changing of parameter SaveToLocal (file cqrlog_login.cfg, section Login) to '0'. After that I have to check 'Save to local' during starting and then cqrlog starts local mysql server.
The parameter was set to '1' that time.
Next time cqrlog "trying" to start a local database (is checked) but mysql server is not started. That's a problem, I believe.
Anyway, a new version is more stable. With slow internet connection especially.

73! Andrey

sq3htx
workaround procedure

I was able to recover with the following procedure:
1. rename config folder:
mv ~/.config/cqrlog ~/.config/cqrlog.copy
2. start cqrlog and let it reinitialize config folder
3. create as many empty databases as you had before - in my case two databases
4. quit cqrlog
5. remove folders created for databases
rm -rf ~/.config/cqrlog/database/cqrlog001
rm -rf ~/.config/cqrlog/database/cqrlog002
...
6. copy old corresponding folders
cp -r ~/.config/cqrlog.copy/database/cqrlog001 ~/.config/cqrlog/database/cqrlog001
cp -r ~/.config/cqrlog.copy/database/cqrlog002 ~/.config/cqrlog/database/cqrlog002
...
7. copy old config file
cp ~/.config/cqrlog.copy/cqrlog.cfg ~/.config/cqrlog/cqrlog.cfg

That's it.
Worked for me and I don't see any suspicious logs and all my contacts are in place so I believe databases are consistent. You have to just rename databases back to what you had before. There's no guarantee though, so you'd better retain old config folder.

Marek SQ3HTX