Skip to main content ↑ ↓
Topic: syslog-ng and python-virtualenv problem (Read 612 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

syslog-ng and python-virtualenv problem

Hi
I see that during my init syslog-ng complains that my install has no python-virtualenv. I installed it, but it still complains.
Code: [Select]
user@host ~ $ sudo rc-service syslog-ng restart
 * WARNING: you are stopping a boot service
 * Stopping syslog-ng ...                                                                                                               [ ok ]
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
[2023-08-22T16:35:35.503049] python: private virtualenv is not initialized, use the `syslog-ng-update-virtualenv' script to initialize it or make sure all required Python dependencies are available in the system Python installation; path='/var/lib/syslog-ng/python-venv'        [ ok ]
 * Starting syslog-ng ...                                                                                                               [ ok ]
user@host ~ $ pacman -Q python-virtualenv
python-virtualenv 20.24.3-1

When I try to run the script, it tells me that it will use pip for the install. I do not want that, as I do not want to maintain anything with pip.

I have also found talk of in on the gentoo forums: https://bugs.gentoo.org/907550

Re: syslog-ng and python-virtualenv problem

Reply #1 –
look at this post

either run the script (it install the needed package in venv, so no conflict with system packages)
or
use "metalog" instead

Re: syslog-ng and python-virtualenv problem

Reply #2 –
So long as syslog-ng is running and working you don't need to worry to much.
If it is running that would mean your system installed python modules are covering any python dependencies needed by syslog-ng.

It would only become an issue if you uninstalled the python modules it needs.
It's possibly a questionable packaging decision, and actual project decision,  which I imagine Artix has inherited from Arch.
If syslog-ng needs python and certain modules the package should depend on them imho. And in my old fashioned way I'm not keen on system services using python venvs. Not sure why? Just doesn't seem right :)

Maybe there's more to it? It's been discussed on the syslog-ng github issues page.

But I have the warning and just ignore it. It works.
I understand why warnings in the boot messages cause concern though.

Re: syslog-ng and python-virtualenv problem

Reply #3 –
@suren my concern is that when I will install it I will also need to look after it, right?

@gripped I have uninstalled the
Code: [Select]
python-virtualenv
package and it still runs fine from what I can see.
I really do not know whats up with it.

Re: syslog-ng and python-virtualenv problem

Reply #4 –
If you install the package "check-link-consistency" then run "# check-link-consistency -N" it should tell you what libs are missing, and the required version. Some libs are optional and not required for many uses. It could be that syslog-ng was built against a different version of python-virtualenv to the one currently in the repos. In the past I found pip packages worked until there was a major version upgrade for python, typically once a year. After that they stopped functioning, also pip forgot about them and I had to find and uninstall the program files myself. Not sure if that is still the case though. (I use rsyslog from the AUR myself, mainly because I have my own config I like, currently you need to disable imjournal and omjournal in the PKGBUILD though.)

Re: syslog-ng and python-virtualenv problem

Reply #5 –
Quote from: Artt – on
I really do not know whats up with it.
Some discussion on the matter https://github.com/syslog-ng/syslog-ng/issues/4471

A commit that addresses it it seems in master https://github.com/syslog-ng/syslog-ng/pull/4490

Just ignore the warning. It's spurious. I suspect it will go away in due course when syslog-ng gets a new release.