Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mosquitto crashed by segfault on CentOS (v1.4.1~v1.4.2) #38

Closed
ralight opened this issue Mar 15, 2016 · 0 comments
Closed

mosquitto crashed by segfault on CentOS (v1.4.1~v1.4.2) #38

ralight opened this issue Mar 15, 2016 · 0 comments

Comments

@ralight
Copy link
Contributor

ralight commented Mar 15, 2016

migrated from Bugzilla #470534
status CLOSED severity normal in component Mosquitto for 1.4
Reported in version unspecified on platform PC
Assigned to: Roger Light

On 2015-06-18 21:40:59 -0400, Taro Kawazoe wrote:

I installed mosquitto via yum on CentOS 6.5 (yum repository: home_oojah_mqtt).
And I've encountered this issue as below, and looking for a solution.
Any hints please?

mosquitto v1.4.1 crashes from time to time under following segfault:

Jun 8 12:51:54 ****** kernel: mosquitto[27486]: segfault at 0 ip 00007fde8c92382c sp 00007fff79e70438 error 4 in libc-2.12.so[7fde8c7eb000+18a000]
Jun 10 20:57:01 ****** kernel: mosquitto[20195]: segfault at 0 ip 00007f08f49cc82c sp 00007fff9db8e568 error 4 in libc-2.12.so[7f08f4894000+18a000]

By the way, I've also found similar issues in Debian cases:

So I upgraded mosquitto from v1.4.1 to v1.4.2 via yum as well,
however mosquitto crashed again.

Jun 14 10:28:02 ****** kernel: mosquitto[21437]: segfault at 0 ip 00007fe6fedde82c sp 00007fffd9e49ed8 error 4 in libc-2.12.so[7fe6feca6000+18a000]

On 2015-06-21 16:01:20 -0400, Roger Light wrote:

I regret that the segfault information doesn't give any useful information. I'll install CentOS 6.5 in a virtual machine and see if I can reproduce it. Can you give any hints as to what the behaviour of your clients is (i.e. topics, size of payload, qos, clean session or not, anything you can provide).

On 2015-06-23 23:51:44 -0400, Taro Kawazoe wrote:

I have informations that mosquitto output only following application log whenever it crashed:

1433735514: Saving in-memory database to /var/lib/mosquitto/mosquitto.db.
(= Jun 8 12:51:54)
1433937421: Saving in-memory database to /var/lib/mosquitto/mosquitto.db.
(= Jun 10 20:57:01)
1434245282: Saving in-memory database to /var/lib/mosquitto/mosquitto.db.
(= Jun 14 10:28:02)

I don't have any more information because mosquitto have not crashed since Jun 14.
So, I'm sorry that I don't know condition of topic, payload yet.

I don't know whether useful information, but I describe contents of mosquitto.conf.

#mosquitto.conf

retry_interval 60
pid_file /var/run/mosquitto.pid
max_inflight_messages 100
max_queued_messages 100
queue_qos0_messages false
message_size_limit 0
persistent_client_expiration 30d
allow_duplicate_messages true
upgrade_outgoing_qos false
port 1883
max_connections -1
persistence true
persistence_location /var/lib/mosquitto/

log_dest stderr
log_type error
log_type warning
log_type notice
log_type information
log_type debug
connection_messages true

allow_anonymous false
password_file /etc/mosquitto/conf.d/passwd.conf
acl_file /etc/mosquitto/conf.d/acl.conf

Thanks.

On 2015-08-17 16:57:43 -0400, Roger Light wrote:

I'm closing this bug as invalid, because there isn't enough information to work with. If there is more you can add, please reopen the bug.

@ralight ralight closed this as completed Mar 15, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant