No mysql No cqrlog.err

28 posts / 0 new
Last post
m0ddr
No mysql No cqrlog.err

I recently reloaded my PC (slack 14.1 and cqrlog 1.9.0) and now CQRLOG won't run

When it starts cqrlog gives the following error:
MySQL could not be started, please check if the MySQL server is installed properly
MySQL is running OK.

I ran cqrlog debug and got the following. I noticed cqrlog also couldn't find mysql.err so I created it but the result from the debug remained the same and mysql.err is empty

Loading libcrypto: /usr/lib/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/libmysqlclient.so
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.500000000000000000E+00
**********************************
Loaded 79027 LoTW users
Loaded 87197 eQSL users
Loaded 47254 SCP calls
IniFile:/root/.config/cqrlog/cqrlog.cfg
LocalIniFile:/root/.config/cqrlog/local.cfg
*
User home directory: /root/
Program home directory: /root/.config/cqrlog/
Data directory: /root/.config/cqrlog/database/
Memebers directory: /usr/share/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.5
*
Trying to connect to database
180102 14:48:55 mysqld_safe Logging to '/root/.config/cqrlog/database//mysql.err'.
180102 14:48:55 mysqld_safe Starting mysqld daemon with databases from /root/.config/cqrlog/database/
/usr/bin/mysqld_safe_helper: Can't create/write to file '/root/.config/cqrlog/database//mysql.err' (Errcode: 13)
Server connect failed.
Trying:1
Trying to connect to database

Trying to connect to database
Server connect failed.
Trying:8
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Closing dData
Closing ini file ...
_________________________________________________
Here is ls -l of mysql.err

root@Spitfire:~# ls -l /root/.config/cqrlog/database//mysql.err
-rw-r--r-- 1 root root 0 Jan 2 14:47 /root/.config/cqrlog/database//mysql.err
__________________________________________________

mysql.cfg is:

[mysqld]

innodb_log_file_size=50331648

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

Im not sure where the problem lies

oh1kh
No mysql No cqrlog.err

Hi !

Two questions:

Why you are running as root?
Why you try to run old and buggy version 1.9.0?

Please:
- create an ordinary user (with sudo privileges) and use that for daily operations.
- Install the latest, or at least 2.1.0, version of cqrlog
and then try again.

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
No mysql No cqrlog.err

I just hadn't got round to creating another user. It may not be good practice but it still works.
Slackbuild is installing that version so I ran with it.

I will upgrade as advised.

m0ddr
No mysql No cqrlog.err

I installed cqrlog 2.2.0 from root using tar xvf as you have detailed elsewhere in the forum and it all went OK, no errors.

I tried to run CQRlog from the Application Launcher search but it never found the file.

I then went into /cqrlog-2.2.0/usr/bin/ and tried to run it from there. I found a setup file but again it just sat and did not open.

I also noticed there in no /.config/ directory under root.

I'm guessing the install is not complete after all.

ok2cqr
ok2cqr's picture
Re: No mysql No cqrlog.err

As far as I know, MySQL won't run under the root account. Run cqrlog with --debug=1 and you'll see more details.

oh1kh
mysql/root

Hi!

Tested just that.
Runs very well when first su +passwd (or sudo su+ passwd) and then cqrlog from console with my Fedora 26.

Difference to basic installation is that my logs are set into mysql server (localhost:3306) and so I can access all logs also as root (or any other user).

But if I try to change this to basic install's default protected mode DB (deleting /root/.config/cqrlog) and allowing cqrlog to set up new log to localhost:64000 ("Save data to local machine" checked) this will not work , as you said!

56 us states loaded
/usr/bin/mysqld_safe --defaults-file=/root/.config/cqrlog/database/mysql.cnf --datadir=/root/.config/cqrlog/database/ --socket=/root/.config/cqrlog/database/sock --port=64000
Trying to connect to database
180111 10:57:02 mysqld_safe Logging to '/root/.config/cqrlog/database//mysql.err'.
180111 10:57:02 mysqld_safe Starting mysqld daemon with databases from /root/.config/cqrlog/database/
/usr/bin/mysqld_safe_helper: Can't create/write to file '/root/.config/cqrlog/database//mysql.err' (Errcode: 13 "Permission denied")
TMySQL56Connection : Server connect failed.
Trying:1
Trying to connect to database
TMySQL56Connection : Server connect failed.
Trying:2
Trying to connect to database
TMySQL56Connection : Server connect failed.

Because of different database setup I have never noticed that before.

So we can say to M0DDR: Please create ordinary user and use all programs, including cqrlog, with that user account. You will get rid of mysterious things like tihis.
For fast root access add this new user to sudoers group and you do not need user root any more for anything.

Thanks Petr !

--
Saku
OH1KH

.

--
Saku
OH1KH

m0ddr
No mysql No cqrlog.err

I deleted the 64bit version and tried the i386.

Again no cqrlog in the Application Launcher but it was in //usr/bin/ and this time it started with the following errors:

Error during connection to database: TMySQL55Connection : Server connect failed

mysql not running But it is!!!

Again there is no /.config directory so no cqrlog.err or cqrlog --debug=1

m0ddr
No mysql No cqrlog.err

I saw a good many references to Mariadbclient so I installed it.

CQRLOG behaved exactly as my last post

No mysql, no cqrlog start icon and no /.config directory.

oh1kh
If you install from tar you

If you install from tar you should download it to /tmp
Then go to /tmp with:
cd /tmp
untar the file with:
tar vzxf cqrlog_2.2.0_amd64.tar.gz
then copy everything to right folders with:
cp -a /tmp/cqrlog-2.2.0/usr /
(this must be done as root)

Then you will have the binary file as /usr/bin/cqrlog and it should start from console with just typing:
cqrlog
Other stuff fill go under /usr/share/cqrlog and some other folders under /usr/share

If you now have, from previous installs, folder /cqrlog-2.2.0 just under the root (/) directory remove it with:
rm -rf /cqrlog-2.2.0

Then everything is in right place.

Check that all needed librariies are installed like the last lines at download page says:

The binaries should work in any distribution. Please don't forget to install MySQL server, MySQL client, Hamlib libraries and if LoTW support is desired, trustedqsl package and libssl-devel must be installed.

Tar install will not create items to start menu or icon to desktop. Those you have to make by your self.

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
No mysql No cqrlog.err

I unpacked the tar file the tried to move it as directed

then copy everything to right folders with:
cp -a /tmp/cqrlog-2.2.0/usr /
(this must be done as root)

Result:

root@Spitfire:/tmp# cp -a /tmp/cqrlog-2.2.0/usr /
cp: cannot overwrite non-directory '/usr/share/man' with directory '/tmp/cqrlog-2.2.0/usr/share/man'

oh1kh
No mysql No cqrlog.err

Ah!
You do not have /usr/share/man directory. Instead you have an ordinary file "man" under /usr/src (I wonder why? An from where it has come to?)

How ever "man" directory is not importatnt for program use.
You can first delete it from /tmp with
rm -rf /tmp/cqrlog-2.2.0/usr/share/man
and then try again to copy all with
cp -a /tmp/cqrlog-2.2.0/usr /

Most important is that binary will go to /usr/bin/cqrlog and directory /usr/share/cqrlog is populated.

You can see the whole structure with comand:
tree /tmp/cqrlog-2.2.0/

On the second line branch "usr" should get located under root (/) directrory to be as /usr.
So with command 'tree' you should see where each file should be if you omit the first 'cqrlog-2.2.0' and think that the 'usr' is placed to the disks root (/) directory.

Because tar file is generated so that it includes cqrlog-2.2.0 directory we can not extract it directly to root (/) that would be the easiest way. (and I think some older version tars have been that kind of)
We have first extract it under /tmp and then strip branch cqrlog-2.2.0 away with cp -a command.

--
Saku
OH1KH

--
Saku
OH1KH

oh1kh
install 2.2.0 from tar.gz

Hi!

I updated my knowledge a bit about all tar functions and whole job can be done with one line. Every day there is something new to learn.
First download cqrlog_2.2.0_amd64.tar.gz to directory /tmp
Then execute tar with parameters:

tar vxfz /tmp/cqrlog_2.2.0_amd64.tar.gz --strip-components=1 -C /

That is all and every file should go right away to correct folder. It even does not complain if there is a ordinary file named with same name as directtory from tar. It just overwrites file with same named directory (be warned). Tested this.

Then just start cqrlog from console with command
cqrlog
or if (for some unknown reason) /usr/bin is not part of your PATH use full name
/usr/bin/cqrlog

Make needed menu and desktop icons manually.

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
Back to square one.

Back to square one.

The ter install seemed to go OK with no errors

When I ran cqrlog the little feather flashed for about 30 seconds then stopped.

root@Spitfire:/# cqrlog --debug=1
-bash: /usr/bin/cqrlog: cannot execute binary file
root@Spitfire:/#

and no /.config directory was created so no log file to read

m0ddr
No mysql No cqrlog.err

It is interesting that the older version cqrlog did at least load and open whereas the latest version will not even install correctly.

m0ddr
Just to confirm cqrlog is

Just to confirm cqrlog is there and in the correct directory

root@Spitfire:/# ls /usr/bin/cqr*
/usr/bin/cqrlog*
root@Spitfire:/#

m0ddr
I don't get the ownership of

I don't get the ownership of this file. Where does 1000 come from?

root@Spitfire:~# ls -l /usr/bin/cqrlog
-rwxr-xr-x 1 1000 1000 15665968 Dec 30 06:45 /usr/bin/cqrlog*
root@Spitfire:~#

oh1kh
I don't get the ownership of

User 1000 comes from tar, I think.

Usually first ordinary user gets ID 1000. But if you are root you should be able to change that (or use sudo chown as oridinary user):
chown root.root /usr/bin/cqrlog

But on the other hand every user has execute rights, so that should be enough for running cqrlog even it is owned by 1000 that seems to be unused ID in your system.
--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
cqrlog still wont start

I changed ownership but cqrlog still wont start.

oh1kh
No.

No.
It can't help as:
root@Spitfire:~# ls -l /usr/bin/cqrlog
-rwxr-xr-x 1 1000 1000 15665968 Dec 30 06:45 /usr/bin/cqrlog*
root@Spitfire:~#.
You see those 3 'x' there. They mean 1st,2nd,3rd owner,group and anyone can execute this file.
So the 3rd = anyone can execute was there already. You just fitted 1st and 2nd 'x' to fit root.root to execute (instead of 1000.1000).
Does not change anything as root was counted to anyone when ownership was 1000.1000

Problem is not there.
What is the output if you type this line in console window: ?

/usr/bin/cqrlog debug=1

There must be some kind of output.

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
What is the output if you

What is the output if you type this line in console window: ?

/usr/bin/cqrlog debug=1

There must be some kind of output.

See message #13

m0ddr
root@Spitfire:/# cqrlog -

root@Spitfire:/# cqrlog --debug=1
-bash: /usr/bin/cqrlog: cannot execute binary file
root@Spitfire:/#

oh1kh
root@Spitfire:/# cqrlog -

Hi!

Could it be that you have i386 CPU and you are trying to use x86_64 CPU's binary?

Did you make last install with this?:
tar vxfz /tmp/cqrlog_2.2.0_amd64.tar.gz --strip-components=1 -C /

It points to 64bit tar. Please download i386 binary and try replace its name to that tar command line.

After that is sure, again check that execute is allowed for all:
chmod a+x /usr/bin/cqrlog

I can't figure out anything else that would prevent executing binary.

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
I uminstalled the 64bit

I uminstalled the 64bit version and installed
tar vxfz /tmp/cqrlog_2.2.0_i386.tar.gz --strip-components=1 -C /

All went OK and CQRLOG started with the following error

Error during connection to database: TMySQL55Connection : Server connect failed.

I ran debug and got the following:

**** DEBUG LEVEL 1 ****

SSL libraries:
/usr/lib/libssl.so.1.0.0
/usr/lib/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib/libmysqlclient.so
**************************
MySQL version: 5.5
**************************
**********************************
MySQL version assigned: 5.5
**********************************
Loaded 79027 LoTW users
Loaded 87197 eQSL users
Loaded 47254 SCP calls
*
User home directory: /root/
Program home directory: /root/.config/cqrlog/
Data directory: /root/.config/cqrlog/database/
Memebers directory: /usr/share/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.5
*
56 us states loaded
/usr/bin/my180116 17:39:07 mysqld_safe Logging to '/root/.config/cqrlog/database//mysql.err'.
180116 17:39:07 mysqld_safe Starting mysqld daemon with databases from /root/.config/cqrlog/database/
sqld_safe --defaults-file=/root/.config/cqrlog/database/mysql.cnf --datadir=/root/.config/cqrlog/database/ --socket=/root/.config/cqrlog/database/sock --port=64000
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:1
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:2
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:3
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:4
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:5
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:6
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:7
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:8
Command line: xdg-open /root/.config/cqrlog/database/mysql.err
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Closing dData

Again there is no /.config directory so no error log.

Looks like I'm back to square 1.

m0ddr
oops I found .config but

oops I found .config but there is no error log there

Here is what I've got there

root@Spitfire:~/.config/cqrlog# ls -l
total 1628
-rw-r--r-- 1 root root 340895 Dec 31 00:43 MASTER.SCP
drwxr-xr-x 2 root root 4096 Dec 31 00:47 call_data/
-rw-r--r-- 1 root root 82 Jan 16 17:39 cqrlog_login.cfg
drwxr-xr-x 2 root root 4096 Jan 7 20:55 ctyfiles/
drwxr-xr-x 2 root root 4096 Jan 16 17:39 database/
drwxr-xr-x 2 root root 4096 Jan 7 20:55 dxcc_data/
drwxr-xr-x 2 root root 4096 Dec 31 00:47 eQSL/
-rw-r--r-- 1 root root 679931 Dec 31 00:43 eqsl.txt
drwxr-xr-x 2 root root 4096 Dec 31 00:47 images/
drwxr-xr-x 2 root root 4096 Dec 31 00:47 lotw/
-rw-r--r-- 1 root root 600942 Dec 31 00:43 lotw1.txt
drwxr-xr-x 2 root root 4096 Dec 31 00:47 voice_keyer/
drwxr-xr-x 2 root root 4096 Dec 31 00:47 xplanet/
root@Spitfire:~/.config/cqrlog#

oh1kh
oops I found .config but

HI!

Now you are almost there!

Read again this chain/reply #4 and #5 (specially the last chapter of #5).
https://www.cqrlog.com/node/1954#comment-6024

and then I think you have running cqrlog. Finally!

--
Saku
OH1KH

--
Saku
OH1KH

m0ddr
I created user M0DDR and

I created user M0DDR and logged as that.

You know what I'm going to say!
..
..
..
IT WORKED!!!!!!

It was a slow train comming*

Thank you so much for your time.

Steve

*Bob Dylan circa 1980

oh1kh
I created user M0DDR and

Hi Steve
Enjoy, sometimes using normal user account makes wonders !
(Slow train coming/side2/the tittle of 1st track)
--
Saku
OH1KH

--
Saku
OH1KH

ok1lrd
CQRLOG Database connection not work

Hallo, my cqrlog not work. What can I do? Tnx, Vaclav, OK1LRD
190620 16:28:56 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
190620 16:28:56 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
190620 16:28:56 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.64-MariaDB-1ubuntu0.14.04.1' socket: '/home/vze/.config/cqrlog/database/sock' port: 64000 (Ubuntu)
190621 1:16:03 [Note] /usr/sbin/mysqld: Normal shutdown
190621 1:16:03 InnoDB: Starting shutdown...
190621 1:16:03 InnoDB: Waiting for 9 pages to be flushed
190621 1:16:05 InnoDB: Shutdown completed; log sequence number 62360239
190621 1:16:05 [Note] /usr/sbin/mysqld: Shutdown complete

File: