Hello,
Today when i restarted datagerry i got message:
Summary
Apr 25 11:21:12 server datagerry[204105]: File “pika/adapters/base_connection.py”, line 464, in _handle_read
Apr 25 11:21:12 server datagerry[204105]: File “pika/connection.py”, line 2021, in _on_data_available
Apr 25 11:21:12 server datagerry[204105]: File “pika/connection.py”, line 2142, in _process_frame
Apr 25 11:21:12 server datagerry[204105]: File “pika/connection.py”, line 2120, in _process_callbacks
Apr 25 11:21:12 server datagerry[204105]: File “pika/callback.py”, line 60, in wrapper
Apr 25 11:21:12 server datagerry[204105]: File “pika/callback.py”, line 92, in wrapper
Apr 25 11:21:12 server datagerry[204105]: File “pika/callback.py”, line 236, in process
Apr 25 11:21:12 server datagerry[204105]: File “pika/adapters/blocking_connection.py”, line 1357, in _on_channel_closed
Apr 25 11:21:12 server datagerry[204105]: pika.exceptions.ChannelClosed: (405, "RESOURCE_LOCKED - cannot obtain exclusive access to locked queue ‘datagerry.eventbus.webapp’ in vhost ‘/’. It could be originally de>
Apr 25 11:21:12 server datagerry[204105]: [2024-04-25 11:21:12][INFO ] — Interfaces started @ http://0.0.0.0:4000 (gunicorn.py)
and second bug when i stop datagerry it still works
root@server:~# systemctl stop datagerry.service
root@server:~# ps aux |grep datagerry
datager+ 1580 0.0 2.0 469300 83852 ? Sl Apr24 0:01 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1594 0.0 1.1 286112 47764 ? Sl Apr24 0:26 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1599 0.0 2.5 430936 101836 ? Sl Apr24 0:25 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1646 0.0 2.4 431192 97368 ? S Apr24 0:12 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1647 0.0 3.0 449700 120684 ? Sl Apr24 0:42 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1648 0.0 4.3 503096 174776 ? Sl Apr24 0:45 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1649 0.0 3.0 452104 123220 ? Sl Apr24 0:44 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1650 0.0 4.3 505180 176168 ? Sl Apr24 0:44 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 1651 0.0 3.0 451840 122776 ? Sl Apr24 0:43 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 204092 0.3 2.0 469292 83888 ? Sl 11:21 0:01 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 204100 0.0 1.1 286112 47908 ? Sl 11:21 0:00 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
datager+ 204105 0.2 2.5 430836 102076 ? Sl 11:21 0:00 /usr/bin/datagerry -c /etc/datagerry/cmdb.conf -s
root 204805 0.0 0.0 6612 2256 pts/1 S+ 11:26 0:00 grep --color=auto datagerry
So stop and restart service datagerry don’t work good