Failed to get properties: Operation not permitted

Issues related to applications and software problems
Post Reply
nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/09 12:09:13

Hello,

Running CentOS Linux release 7.2.1511 (Core) on production server.
Today, I have updated systemd to version systemd-219-57.el7_5.3.x86_64.

After that, I ran command to check the services status and got below error.

[root@abc ~]# systemctl status nginx.service
"Failed to get properties: Operation not permitted"

[root@abc ~]# systemctl list-units
"Failed to list units: Operation not permitted"

Any idea to fix this issue?

tunk
Posts: 412
Joined: 2017/02/22 15:08:17

Re: Failed to get properties: Operation not permitted

Post by tunk » 2018/10/09 12:19:29

Have you tried to reboot it? - that should also boot into the newest kernel.

nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Re: Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/09 12:33:53

Thanks for your quick reply.

I have not rebooted because it is a production server. So I have to plan it accordingly.

Do you think rebooting will solve the issue because when I google the problem I found a few posts where their problem was not resolved by rebooting the server.

nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Re: Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/09 12:35:51

I hope rebooting will not cause any issue otherwise downtime will increase.

tunk
Posts: 412
Joined: 2017/02/22 15:08:17

Re: Failed to get properties: Operation not permitted

Post by tunk » 2018/10/09 12:40:49

I don't know. I'm speculating that there may be some inconsistencies running an old kernel with new packages.

nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Re: Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/10 10:34:37

Any other alternative to fix this issue instead of rebooting.

User avatar
TrevorH
Forum Moderator
Posts: 23647
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Failed to get properties: Operation not permitted

Post by TrevorH » 2018/10/10 14:23:52

Did you just update systemd? Or did you run yum update to get off 7.2 - which is *3 YEARS* old! The current version is 7.5 and you should be running yum update much more regularly than once every 3 years. There have been hundreds if not thousands of security bugs fixed in the last 3 years.

Run yum update then reboot.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Re: Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/12 07:09:35

First, I have updated only systemd but it wont fix the issue so then I updated all the packages with yum update and on reboot I am receiving below error. So it looks like it is not booting. Now I am stuck.
[58754621.145870] systemd-journald[22939]: Received SIGTERM from PID 1 (systemd).
[58754621.146379] systemd-journald[29064]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[58754621.149227] type=1130 audit(1539329580.714:67868172): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[58754621.395551] type=1130 audit(1539329580.960:67868173): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[58754621.395590] type=1131 audit(1539329580.960:67868174): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[58754621.403825] systemd-journald[23014]: Failed to connect to notify socket: Connection refused
Any help is appreciated.

nshah14285
Posts: 7
Joined: 2016/09/12 09:18:52

Re: Failed to get properties: Operation not permitted

Post by nshah14285 » 2018/10/12 09:23:34

Finally, issue got fixed.

I forcefully shutdown the virtual machine using command "virsh destroy domain" then started the virtual machine again and it worked.

@tunk and @TrevorH Thanks for suggesting the solution. It really saved me.

Thank You so much for your help :)

Post Reply