Rabbitmq keeps dying within 2 minutes of startup, and fails with the error:
ERROR: epmd error for host localhost: timeout (timed out)
The /etc/hosts file shows:
127.0.0.1 localhost []-MacBook-Pro []-MacBook-Pro.local
255.255.255.255 broadcasthost
::1 localhost
([] replaces actual name in file)
I have tried uninstalling and reinstalling Erlang (v20.3.8.3) and Rabbitmq via homebrew, and still no connection. This is also regardless of what wifi I am on, or if I’m disconnected from wifi. Other commands I have tried:
$ echo $HOSTNAME
localhost
$ hostname
localhost
$ ifconfig lo0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
$ lsof -p 15279
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
epmd 15279 user cwd DIR 1,5 960 2 /
epmd 15279 user txt REG 1,5 46756 4852991 /usr/local/Cellar/erlang@20/20.3.8.3/lib/erlang/erts-9.3.3.2/bin/epmd
epmd 15279 user txt REG 1,5 841456 2333502 /usr/lib/dyld
epmd 15279 user txt REG 1,5 1170673664 3866438 /private/var/db/dyld/dyld_shared_cache_x86_64h
epmd 15279 user 0r CHR 3,2 0t0 311 /dev/null
epmd 15279 user 1w CHR 3,2 0t0 311 /dev/null
epmd 15279 user 2w CHR 3,2 0t0 311 /dev/null
epmd 15279 user 3u IPv4 0x91f821cb489372bb 0t0 TCP *:epmd (LISTEN)
epmd 15279 user 4u IPv6 0x91f821cb3ac82ed3 0t0 TCP *:epmd (LISTEN)
epmd 15279 user 5u IPv4 0x91f821cb4a2f057b 0t0 TCP localhost:epmd->localhost:55223 (ESTABLISHED)
epmd 15279 user 6u IPv4 0x91f821cb3a64dc1b 0t0 TCP localhost:epmd->localhost:55470 (ESTABLISHED)
epmd 15279 user 7u IPv4 0x91f821cb4919995b 0t0 TCP localhost:epmd->localhost:55974 (ESTABLISHED)
I’m not sure what else to try here, and am hoping someone has an idea.
Rabbitmq-Server перезапуск начинает ошибку
Узнайте заметки, Оли!
Примечание.
Редактировать/etc/hosts file, добавьте «xxx.xxx.xxx.xxxxix airetalk» в конце файла. Среди них «xxx.xxx.xxx.xxx» может написать IP -адрес сервера
Я здесь редакторwwwПросто обратите внимание на имя за хостом
Это локальный IP -адрес сервера, за которым следует имяПросто иди самостоятельно Я только начал ставить его позади другого
Configuring logger redirection
11:04:29.714 [error]
11:04:29.718 [error] BOOT FAILED
11:04:29.718 [error] ===========
11:04:29.718 [error] ERROR: epmd error for host www: timeout (timed out)
11:04:29.718 [error]
BOOT FAILED
===========
ERROR: epmd error for host www: timeout (timed out)
11:04:30.719 [error] Supervisor rabbit_prelaunch_sup had child prelaunch started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit with reason {epmd_error,"www",timeout} in context start_error
11:04:30.719 [error] CRASH REPORT Process <0.151.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,prelaunch,{epmd_error,"www",timeout}}},{rabbit_prelaunch_app,start,[normal,[]]}} in application_master:init/4 line 138
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{epmd_error,"www",timeout}}},{rabbit_prelaunch_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{epmd_error,"www",timeout}}},{rabbit_prelaunch_app,start,[norm
Crash dump is being written to: erl_crash.dump...done
Rabbitmq-Server перезапуск успешно начинается
Configuring logger redirection
## ## RabbitMQ 3.8.9
## ##
########## Copyright (c) 2007-2020 VMware, Inc. or its affiliates.
###### ##
########## Licensed under the MPL 2.0. Website: https://rabbitmq.com
Doc guides: https://rabbitmq.com/documentation.html
Support: https://rabbitmq.com/contact.html
Tutorials: https://rabbitmq.com/getstarted.html
Monitoring: https://rabbitmq.com/monitoring.html
Logs: /var/log/rabbitmq/rabbit@www.log
/var/log/rabbitmq/rabbit@www_upgrade.log
Config file(s): (none)
Starting broker... completed with 0 plugins.
Rabbitmq -Server -Detached Error Trough
Rabbitmq -Server -Detached Error.
NetStat -lnp | grep 25672 (сообщается в приведенном выше порте) Посмотреть ее соответствующий процесс процесса -9
Запустить снова rabbitmq-server –detached
Или ps -EF | grep rabbitmq (я чувствую, что могу это просмотреть)
Configuring logger redirection
BOOT FAILED
===========
ERROR: distribution port 25672 in use by another node: rabbit@www
14:43:50.407 [error]
14:43:50.410 [error] BOOT FAILED
14:43:50.410 [error] ===========
14:43:50.410 [error] ERROR: distribution port 25672 in use by another node: rabbit@www
14:43:50.410 [error]
14:43:51.411 [error] Supervisor rabbit_prelaunch_sup had child prelaunch started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit with reason {dist_port_already_used,25672,"rabbit","www"} in context start_error
14:43:51.411 [error] CRASH REPORT Process <0.151.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","www"}}},{rabbit_prelaunch_app,start,[normal,[]]}} in application_master:init/4 line 138
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","www"}}},{rabbit_prelaunch_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","www"}}},{rabbit_prelau
Crash dump is being written to: erl_crash.dump...done
tags: Linux
After yum install, start rabbitmq and report an error:
[[email protected] ~]# /etc/init.d/rabbitmq-server start Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err} rabbitmq-server.
View status
[[email protected] ~]# /etc/init.d/rabbitmq-server status Status of node [email protected] ... Error: unable to connect to node [email protected]: nodedown DIAGNOSTICS =========== nodes in question: [[email protected]] hosts, their running nodes and ports: - unable to connect to epmd on www: address (cannot connect to host/port) current node details: - node name: [email protected] - home dir: /var/lib/rabbitmq - cookie hash: xxxxxxxxxx== [[email protected] ~]#
Look at the log:
[[email protected] ~]# tailf /var/log/rabbitmq/startup_log RabbitMQ 3.1.5. Copyright (C) 2007-2013 GoPivotal, Inc. ## ## Licensed under the MPL. See http://www.rabbitmq.com/ ## ## ########## Logs: /var/log/rabbitmq/[email protected] ###### ## /var/log/rabbitmq/[email protected]sasl.log ########## Starting broker... completed with 0 plugins. ERROR: epmd error for host "www": address (cannot connect to host/port) [FAILED]
solution
[[email protected] ~]# vi /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 www 192.168.155 www
Reference: https://gist.github.com/jch/2522701
Intelligent Recommendation
[ ] SSH TIMED OUT Timeout Solution
Transfer from: http://www.cnblogs.com/niutouzdq/p/4091268.html When using Ali Cloud ECS servers, Winsftp is often disconnected by the server, and it is necessary to have no operation for a while, the …
More Recommendation
Created attachment 1080380 [details]
setup log
Description of problem:
When using packstack --answer-file=/root/answerfile.txt
Installation Errors at setting up rabbit
Version-Release number of selected component (if applicable):
How reproducible:
Each time
Steps to Reproduce:
1. Clean Installation of CentOS v7
2. Update CentOS v7
3. install packstack and create /boot/answerfile.txt
3. Use work around for bug #1259354
4. packstack --answer-file=answerfile.txt
Actual results:
192.168.1.100_amqp.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]
ERROR : Error appeared during Puppet run: 192.168.1.100_amqp.pp
Error: Could not start Service[rabbitmq-server]: Execution of '/usr/bin/systemctl start rabbitmq-server' returned 1: Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.
Expected results:
Install to complete
Additional info:
[root@cloud ~]# /sbin/service rabbitmq-server start
Redirecting to /bin/systemctl start rabbitmq-server.service
Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.
Output of journalctl -u rabbitmq-server
[root@cloud ~]# journalctl -u rabbitmq-server
-- Logs begin at Sun 2015-10-04 19:53:13 BST, end at Tue 2015-10-06 20:08:51 BST. --
Oct 04 20:41:04 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6693, but reception only p
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6695, but reception only p
Oct 04 20:41:34 cloud.phillw.net rabbitmq-server[6680]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 20:41:34 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 20:41:35 cloud.phillw.net rabbitmqctl[6805]: Stopping and halting node rabbit@cloud ...
Oct 04 20:41:42 cloud.phillw.net rabbitmqctl[6805]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: DIAGNOSTICS
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: ===========
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: attempted to contact: [rabbit@cloud]
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: rabbit@cloud:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: current node details:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - node name: rabbitmqctl6805@cloud
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - home dir: /var/lib/rabbitmq
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 20:42:12 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 04 23:33:57 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8866, but reception only p
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8868, but reception only p
Oct 04 23:34:27 cloud.phillw.net rabbitmq-server[8853]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 23:34:27 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 23:34:27 cloud.phillw.net rabbitmqctl[8973]: Stopping and halting node rabbit@cloud ...
Oct 04 23:34:34 cloud.phillw.net rabbitmqctl[8973]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: DIAGNOSTICS
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: ===========
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: attempted to contact: [rabbit@cloud]
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: rabbit@cloud:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: current node details:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - node name: rabbitmqctl8973@cloud
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - home dir: /var/lib/rabbitmq
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 23:35:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 06 20:07:43 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13162, but reception only
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13164, but reception only
Oct 06 20:08:14 cloud.phillw.net rabbitmq-server[13149]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 06 20:08:14 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 06 20:08:14 cloud.phillw.net rabbitmqctl[13185]: Stopping and halting node rabbit@cloud ...
Oct 06 20:08:21 cloud.phillw.net rabbitmqctl[13185]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: DIAGNOSTICS
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: ===========
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: attempted to contact: [rabbit@cloud]
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: rabbit@cloud:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: current node details:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - node name: rabbitmqctl13185@cloud
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - home dir: /var/lib/rabbitmq
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 06 20:08:51 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
[root@cloud ~]# journalctl -u rabbitmq-server
-- Logs begin at Sun 2015-10-04 19:53:13 BST, end at Tue 2015-10-06 20:08:51 BST. --
Oct 04 20:41:04 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6693, but reception only permitted for PID 6680
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6695, but reception only permitted for PID 6680
Oct 04 20:41:34 cloud.phillw.net rabbitmq-server[6680]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 20:41:34 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 20:41:35 cloud.phillw.net rabbitmqctl[6805]: Stopping and halting node rabbit@cloud ...
Oct 04 20:41:42 cloud.phillw.net rabbitmqctl[6805]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: DIAGNOSTICS
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: ===========
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: attempted to contact: [rabbit@cloud]
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: rabbit@cloud:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: current node details:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - node name: rabbitmqctl6805@cloud
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - home dir: /var/lib/rabbitmq
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 20:42:12 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 04 23:33:57 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8866, but reception only permitted for PID 8853
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8868, but reception only permitted for PID 8853
Oct 04 23:34:27 cloud.phillw.net rabbitmq-server[8853]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 23:34:27 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 23:34:27 cloud.phillw.net rabbitmqctl[8973]: Stopping and halting node rabbit@cloud ...
Oct 04 23:34:34 cloud.phillw.net rabbitmqctl[8973]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: DIAGNOSTICS
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: ===========
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: attempted to contact: [rabbit@cloud]
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: rabbit@cloud:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: current node details:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - node name: rabbitmqctl8973@cloud
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - home dir: /var/lib/rabbitmq
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 23:35:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 06 20:07:43 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13162, but reception only permitted for PID 13149
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13164, but reception only permitted for PID 13149
Oct 06 20:08:14 cloud.phillw.net rabbitmq-server[13149]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 06 20:08:14 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 06 20:08:14 cloud.phillw.net rabbitmqctl[13185]: Stopping and halting node rabbit@cloud ...
Oct 06 20:08:21 cloud.phillw.net rabbitmqctl[13185]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: DIAGNOSTICS
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: ===========
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: attempted to contact: [rabbit@cloud]
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: rabbit@cloud:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: current node details:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - node name: rabbitmqctl13185@cloud
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - home dir: /var/lib/rabbitmq
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 06 20:08:51 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
------
I have seen such a similar issue at https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Tested with openstack-packstack-2015.1-0.11.dev1616.g5526c38.fc23 CentOS Linux release 7.1.1503 (Core) On this setup the problem does not appear. |