[BlueOnyx:22239] Problem with 5208R after installing newlinq

Hi Michael and Greg, Have installed 5208R on a server, fully yum updated and installed newlinq so I can unlink our all bundles packages off an ailing server to transfer to this one. Went to enter my blueonyx shop account details, ie email and password for the first time on this box and wh

[BlueOnyx:22240] Site's disk usage over 100%

hello I encountered a weird problem: a virtual site uses uses more then the attributed disk space: 115% ! At /:81/disk/serverDiskUsage/, it displays Full Host Name Disk Usage Allowed Disk Space Percentage Used • africa.nelembo.com

[BlueOnyx:22241] Re: Site's disk usage over 100%

Hi Meaulnes, > I encountered a weird problem: a virtual site uses uses more then the > attributed disk space: 115% ! At /:81/disk/serverDiskUsage/, it displays > > Now can anyone tell me where that log file is? A search with find > /home/.sites -type f -size +20k -exec ls -FAl {} \; showed on

[BlueOnyx:22242] Re: Site's disk usage over 100%

yes, that script fixed the disk usage of that site, the group disk usage dropped from 401.71 to 33.35MB, what is about the size of all current log files of that site: # ll /home/sites/africa.nelembo.com/logs drwxrws--- 10 SITE7-logs site1 4096 Apr 6 07:59 2013/ drwxrws--- 14 SITE7-logs sit

[BlueOnyx:22243] Re: Error after update

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 - Fr

[BlueOnyx:22244] Re: Error after update

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 t

[BlueOnyx:22245] Re: Error after update

Dirk wrote: > Hello Michael, > > did you find something? Michael took a look at my server and found the best solution to the problem seems to be to delete /var/run/dbus/system_bus_socket and then to reboot. So simply do: rm /var/run/dbus/system_bus_socket shutdown -r now I did this on 4 server

[BlueOnyx:22246] Re: Error after update

Hi Dirk and Greg, > 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, whi

[BlueOnyx:22247] Re: Error after update

Hello Michael, thank you for the advise. The fix is working. Best regards, Dirk --- -Ursprüngliche Nachricht- Von: Blueonyx [mailto:blueonyx-boun...@mail.blueonyx.it] Im Auftrag von Michael Stauber Gesendet: Donnerstag, 12. Juli 2018 23:24 An: blueonyx@mail.blueonyx.it Betreff: [Bl