Skip to main content ↑ ↓
Topic: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv) (Read 635 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Hello, today I updated my system (was away for about two weeks) and got this warning upon boot: https://ibb.co/c1GYgnT

Is here anyone who's also facing this?

Do I have to simply run the command syslog-ng-update-virtualenv?

TIA

P.S. The list of updated packages (syslog-ng is among them): https://pastebin.com/FsGPrTKF

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #2 –
i also had this warning, with syslog-ng refusing to launch
after executing sudo syslog-ng-update-virtualenv, syslog-ng is working again :)

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #3 –
Quote from: Dju – on
i also had this warning, with syslog-ng refusing to launch
after executing sudo syslog-ng-update-virtualenv, syslog-ng is working again :)
Well I wish I had such luck. I also ran the command above and it ran successfully. Upon reboot, however, the output in my tty prior to login still displays the warning message asking me to run the command again. Upon running the command, the output says that the dependencies are already satisfied. I am unsure on how to proceed.

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #4 –
I got the same warning, and find it really annoying. ::)
  • by default I do not need python functionality in my system logger on a desktop client PC
  • <rant> why I have a system python instance if it makes a virtual env for parts of that system? To me it means some developers do not do their work right.
  • we have spent ages to make sure shared libraries are sparing resources, and now we do it backwards installing stuff several times for what exactly? </rant>
To me it seems we need a fix on the configuration of syslog-ng. Making a virtual environment at this level is wasting resources.
****************************************************
* Good decisions come from experience. Experience comes from making bad decisions.
* (Mark Twain)

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #5 –
Quote from: tomio – on
<rant> why I have a system python instance if it makes a virtual env for parts of that system? To me it means some developers do not do their work right.
That's why I use metalog instead, syslog-ng is trying to do more than it's supposed to.

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #6 –
Quote from: nous – on
That's why I use metalog instead

Interesting, thanks. How should I replace it? Simply remove syslog-ng and install metalog and enable the service? Is it enough?

Re: Updated system today: python virtualenv warning (syslog-ng-update-virtualenv)

Reply #7 –
If you use s6, you can also use syslogd-s6 as an alternative.