[BlueOnyx:22244] Re: Error after update

[Greg Kuhnert]

Hi Dirk.

The symptoms you are seeing have actually been around for a long time on all of my servers, and many other people’s servers. I researched, and provided what I thought would be the fix to Michael. Below is a copy of what I sent to Michael…

In terms of what to do for you. I am guessing that your existing bus socket was some how in /var/run … But the question is, how did it get like that? And equally importantly, what now? Ultimately, you have two symlinks, and no socket. The socket would need to be recreated. Theoretically, it is created by the dbus daemon itself… so theoretically, deleting both of those files and restarting dbus should allow it to be recreated… but the question is, which one will it use for creation? And do we then need to manually sym link it.

But puzzles me - is why is your server different?


=== This is the initial results of my research below ===

> From what I gather, it will be any Centos 7 server… The fix is simple.
> 
> 1. Check if it is already a symlink - and abort if it is
> 2. Stop DBUS
> 3. rm  /var/run/dbus/system_bus_socket
> 4. ln -s /run/dbus/system_bus_socket /var/run/dbus/system_bus_socket
> 5. Restart DBUS
> 
>> On 18 Jun 2018, at 5:19 am, Michael Stauber <mstauber at solarspeed.net> wrote:
>> 
>> Hi Greg,
>> 
>>> Been troubleshooting an issue - I have a solution that should be pushed out
>>> 
>>> https://unix.stackexchange.com/questions/254036/g-io-error-quark-39-error-when-stopping-dbus-service
>>> 
>>> This affects more than just dubs - other stop/starts are coming up with errors, and lots of other app error messages. Not critical, but annoying.
>> 
>> Yeah, it's pretty shitty. Seems to affect OpenVZ VPS's more than ISO
>> installs - if they're affected at all. So the published fix would need
>> to check if this is a VPS or if the problem is present.





> On 13 Jul 2018, at 6:38 am, Dirk Estenfeld <dirk.estenfeld at blackpoint.de> wrote:
> 
> Hello Michael,
> 
> did you find something?
> All of our servers show
> 
> Error getting authority: Error initializing authority: Could not connect: Too many levels of symbolic links (g-io-error-quark, 11)
> 
> while restarting a service (independent what service).
> 
> Best regards,
> Dirk
> 
> ---
> 
> blackpoint GmbH - Friedberger Straße 106b - 61118 Bad Vilbel
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] Im Auftrag von Michael Stauber
> Gesendet: Montag, 9. Juli 2018 23:03
> An: blueonyx at mail.blueonyx.it
> Betreff: [BlueOnyx:22225] Re: Error after update
> 
> Hi Michael,
> 
>> The odd thing is I have never touched that. In any event I tried your
>> suggested fix. Now I get.
>> 
>> # systemctl restart dbus
>> Error getting authority: Error initializing authority: Could not connect: No
>> such file or directory (g-io-error-quark, 1)
> 
> Weird. Could you please send me the login details (via the GUI: "Support
> Request" with "Allow Access" ticked) so that I can take a look?
> 
> -- 
> With best regards
> 
> Michael Stauber
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at mail.blueonyx.it
> http://mail.blueonyx.it/mailman/listinfo/blueonyx