[MXS-2372] Core dump failed on crash due to signing issue Created: 2019-03-07  Updated: 2019-03-12  Resolved: 2019-03-12

Status: Closed
Project: MariaDB MaxScale
Component/s: Packaging
Affects Version/s: 2.3.4
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jeffrey Parker Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Centos 7, Percona Mysql backend, PHP front end.


 Description   

MaxScale crashed, but did not leave a core dump, abrt logged that the package is not signed with the proper key.

Mar  7 03:10:29 maxscale-2 systemd: maxscale.service failed.
 
Mar  7 03:10:29 maxscale-2 abrt-server: Package 'maxscale' isn't signed with proper key
 
Mar  7 03:10:29 maxscale-2 abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2019-03-06-21:10:19-15414' exited with 1
 
Mar  7 03:10:29 maxscale-2 abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2019-03-06-21:10:19-15414'



 Comments   
Comment by markus makela [ 2019-03-07 ]

This means that the MaxScale GPG key used to sign the packages isn't added on your system.

For example, this ZenDesk article describes how to either disable GPG key checking or to add a new GPG key to the system. The same applies to all packages that are signed with keys that aren't in the standard repositories.

You can find the MaxScale signing key here: https://downloads.mariadb.com/MaxScale/MariaDB-MaxScale-GPG-KEY

Comment by markus makela [ 2019-03-12 ]

Closing as this seems to be outside of what we control.

Generated at Thu Feb 08 04:13:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.