When launching as sidecar with my single-container service, I get the following error in the logs:
time="2021-01-15T20:01:10Z" level=info msg="Starting agent process: /usr/bin/newrelic-infra"
time="2021-01-15T20:01:10Z" level=info msg="Creating service..."
time="2021-01-15T20:01:10Z" level=info msg="runtime configuration" agentUser=root component="New Relic Infrastructure Agent" executablePath= maxProcs=1 pluginDir="[/etc/newrelic-infra/integrations.d /var/db/newrelic-infra/integrations.d]"
time="2021-01-15T20:01:10Z" level=info msg="Checking network connectivity..." component=AgentService service=newrelic-infra
time="2021-01-15T20:01:10Z" level=info msg="service is stopping. waiting for agent process to terminate..."
time="2021-01-15T20:01:10Z" level=info msg=Initializing component=AgentService elapsedTime=470.403006ms service=newrelic-infra version=1.14.2
time="2021-01-15T20:01:13Z" level=info msg="New Relic infrastructure agent is running." component=AgentService elapsedTime=3.47403056s service=newrelic-infra
time="2021-01-15T20:01:13Z" level=info msg="Starting up agent..." component=Agent
time="2021-01-15T20:01:13Z" level=warning msg="failed to connect to DBus. make sure systemd is present." component=NotificationHandler
time="2021-01-15T20:01:13Z" level=warning msg="failed to init shutdown monitor" component=NotificationHandler error="no systemd found"
time="2021-01-15T20:01:13Z" level=info msg="Integration health check finished with success" component=integrations.runner.Runner integration_name=nri-ecs
time="2021-01-15T20:01:20Z" level=warning msg="Service run exit." error="graceful stop time exceeded... forcing stop"
Any idea what is going on?
I followed the instructions here: https://docs.newrelic.com/docs/integrations/elastic-container-service-integration/installation/install-ecs-integration and have the required containers, IAM roles, SSM parameter, Policies etc all in place.
ECS on Fargate v1.4.0
linux
-
Linux
При установке теми появляется ошибка »Внутренняя ошибка DBus».Не могли бы вы мне помоч?
-
Вопрос задан
-
112 просмотров
1
комментарий
-
Нужно больше подробностей, делательно видеозапись действий, которые совершаешь перед ошибкой.
Пригласить эксперта
Ответы на вопрос 1
Такое встречалось при команде timedatectl. Решается apt install dbus
-
А как всё правильно сделать? А то я недавно только установил Линукс
Похожие вопросы
-
Показать ещё
Загружается…
21 сент. 2023, в 22:51
450 руб./за проект
21 сент. 2023, в 22:23
5000 руб./за проект
21 сент. 2023, в 20:54
10000 руб./за проект
Минуточку внимания
0
1
После обновления.
~ >>> thunar
Thunar: Failed to initialize Xfconf: Could not connect: Connection refused
(thunar:12927): GLib-GIO-CRITICAL **: 00:59:34.228: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Error creating proxy: Не удалось подключиться к: Connection refused (g-io-error-quark, 39)
...
(thunar:12927): thunar-CRITICAL **: 00:59:34.435: Имя "org.xfce.FileManager" потеряно в сообщении dbus, выходим.
ThunarThumbnailer: failed to create proxy: Не удалось подключиться к: Connection refused% ~ >>> terminator
Traceback (most recent call last):
File "/usr/bin/terminator", line 107, in <module>
ipc.new_window_cmdline(optionslist)
File "/usr/lib/python2.7/site-packages/terminatorlib/ipc.py", line 190, in _exec
bus = dbus.SessionBus()
File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 211, in __new__
mainloop=mainloop)
File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 122, in __new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-8tQTffCSKw: В соединении отказано
Гугл не помог. Я не представляю, куда копать… Поможете, пожалуйста?
After a long time, I have decided to change my desktop environment to XFCE. While making changes on the tty terminal, I got an error that stated: Failed to execute child process “dbus-launch” (No such file or directory) while x-forwarding.
Because of that, I was not allowed to get the graphic interface, and this error is common when you are accessing the GUI screen using WSL2 with Kex.
In this article, you will see how to fix the above error by installing dbus-x11 on your Debian or Ubuntu-based machine.
A dbus acronym stands for Desktop Bus is interprocess communication, which is used to pass information from one application to another process on Linux and Unix-based systems.
By passing single command can resolve this issue in a swift manner:
$ sudo apt install dbus-x11After a successful installation of dbus-x11, you can try to invoke the command that caused the previous error, and you will find that the error no longer exists on the machine.
That’s all to resolve on Debian based machine “failed to execute child process “dbus-launch” (No such file or directory) while x-forwarding”.
A man with a tech effusive who has explored some of the amazing technology stuff and is exploring more. While moving towards, I had a chance to work on Android development, Linux, AWS, and DevOps with several open-source tools.
Загрузка…