[opensuse] systemctl and apache2.service
I have a funny quirk going on with apache2.service in openSuSE12.3 x64 and this behavior is different from other services. If I stop the apache2.service - systemctl stop apache2.service then systemctl seems to lose almost all its understanding of the apache2.service. For example, if I issue this command - systemctl --all --type=service to determine the status of my services, the apache2.service is no longer shown in the output listing. Nor does auto complete for the service name work when I try to start it - systemctl start apac(tab) but if I type in the complete command as follows - systemctl start apache2.service that works! AND systemctl --all --type=service shows the apache2.service status AND I can now use auto complete to stop the service - systemctl stop apa(tab) will auto complete this to systemctl stop apache2.service WEIRD!! What gives? Is there something special about apache2.service that is goofing up systemctl? None of the other services behave like this, so far as I can tell.... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/21/2013 12:29 PM, Marc Chamberlin wrote:
I have a funny quirk going on with apache2.service in openSuSE12.3 x64 and this behavior is different from other services.
If I stop the apache2.service -
systemctl stop apache2.service
then systemctl seems to lose almost all its understanding of the apache2.service. For example, if I issue this command -
systemctl --all --type=service
to determine the status of my services, the apache2.service is no longer shown in the output listing. Nor does auto complete for the service name work when I try to start it -
systemctl start apac(tab)
but if I type in the complete command as follows -
systemctl start apache2.service
that works! AND
systemctl --all --type=service
shows the apache2.service status AND I can now use auto complete to stop the service -
systemctl stop apa(tab) will auto complete this to systemctl stop apache2.service
WEIRD!! What gives? Is there something special about apache2.service that is goofing up systemctl? None of the other services behave like this, so far as I can tell....
Marc...
It gets worse... The systemd System Manager doesn't seem to know a thing about apache2.service, no matter what state it is in! Bug? Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 22/04/13 17:48, Marc Chamberlin escribió:
It gets worse... The systemd System Manager doesn't seem to know a thing about apache2.service, no matter what state it is in!
That can't be.. what does systemctl status apache2 returns and exactly what systemd version are you using (rpm -q systemd) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/22/2013 4:41 PM, Cristian Rodríguez wrote:
El 22/04/13 17:48, Marc Chamberlin escribió:
It gets worse... The systemd System Manager doesn't seem to know a thing about apache2.service, no matter what state it is in!
That can't be.. what does systemctl status apache2 returns and exactly what systemd version are you using (rpm -q systemd)
Cristian - The version of systemd i am using is systemd-195-13.18.1.x86_64. And I am going to backup a bit and say you are partially right, but something weird is going on with apache2.service. This behavior I pointed out seems to happen some time, i.e. systemctl seems to forget that it should know about apache2.service. Sometimes when I stop the service, I do not get a status on apache2.service (nor can I auto complete typing it's name) but other times I do... I do not understand why this is happening nor can I reproduce it consistently... But it IS happening some of the time! Go figure! Marc.... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 22/04/13 22:21, Marc Chamberlin escribió:
And I am going to backup a bit and say you are partially right, but something weird is going on with apache2.service. This behavior I pointed out seems to happen some time, i.e. systemctl seems to forget that it should know about apache2.service. Sometimes when I stop the service, I do not get a status on apache2.service
what do you mean exactly ? systemctl status apache2 returns no data ? does it hang for a while? (nor can I auto
complete typing it's name) but other times I do... I do not understand why this is happening nor can I reproduce it consistently... But it IS happening some of the time! Go figure!
bash completion information is usually cached to prevent you having to deal with excruciating slow workflow, the cache invalidation part may be going bad in this case. Also, as you probably already figured out this bash completion thing is generally not particulary reliable. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/22/2013 6:33 PM, Cristian Rodríguez wrote:
El 22/04/13 22:21, Marc Chamberlin escribió:
And I am going to backup a bit and say you are partially right, but something weird is going on with apache2.service. This behavior I pointed out seems to happen some time, i.e. systemctl seems to forget that it should know about apache2.service. Sometimes when I stop the service, I do not get a status on apache2.service
what do you mean exactly ? systemctl status apache2 returns no data ? does it hang for a while? Thanks Cristian for again responding. Uh sorry, guess I am not being too clear. 'systemctl status apache2' seems to work fine. It is when I do
systemctl --all --type=service that I do not always see apache2.system listed in the output. Sometimes I do, sometimes I don't and it seems to be affected more by whether the apache2.system service is stopped and disabled or not... I noted your comments about bash and auto completion of commands... So I won't worry about that particular issue any more and just chalk it up to a bash/cache issue. I have found, what appears to me to be another anomaly about apache2.service, but this is just a long shot guess and I have NO idea whether this affects anything..... The apache2.service file got installed to /lib/systemd/system and it is the ONLY file found at that location. Most of the other .service files seem to get installed at /usr/lib/systemd/system Marc.... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Ping? Is this a bug and should I report it, or is the fact that apache2.service is installed in a unique location OK? Marc.. On 4/23/2013 10:25 AM, Marc Chamberlin wrote:
On 4/22/2013 6:33 PM, Cristian Rodríguez wrote:
El 22/04/13 22:21, Marc Chamberlin escribió:
And I am going to backup a bit and say you are partially right, but something weird is going on with apache2.service. This behavior I pointed out seems to happen some time, i.e. systemctl seems to forget that it should know about apache2.service. Sometimes when I stop the service, I do not get a status on apache2.service
what do you mean exactly ? systemctl status apache2 returns no data ? does it hang for a while? Thanks Cristian for again responding. Uh sorry, guess I am not being too clear. 'systemctl status apache2' seems to work fine. It is when I do
systemctl --all --type=service
that I do not always see apache2.system listed in the output. Sometimes I do, sometimes I don't and it seems to be affected more by whether the apache2.system service is stopped and disabled or not...
I noted your comments about bash and auto completion of commands... So I won't worry about that particular issue any more and just chalk it up to a bash/cache issue.
I have found, what appears to me to be another anomaly about apache2.service, but this is just a long shot guess and I have NO idea whether this affects anything..... The apache2.service file got installed to /lib/systemd/system and it is the ONLY file found at that location. Most of the other .service files seem to get installed at /usr/lib/systemd/system
Marc....
-- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 25/04/13 13:01, Marc Chamberlin escribió:
Ping? Is this a bug and should I report it, or is the fact that apache2.service is installed in a unique location OK?
Systemd still reads units in /lib/systemd/system so in released products this should not be a big deal. This bug was fixed 8 weeks ago in factory, so the next opensuse version will be fine. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Cristian Rodríguez -
Marc Chamberlin