Insecure directory in $ENV{PATH} while running with -T

markusd

Renowned Member
Apr 20, 2015
108
2
83
Dortmund
Hi,
after hardware - failure i restored a node from backup
The system works but some of the web-gui gives me failures:

-Syslog:
command 'journalctl -o short --no-pager --since 2016-04-25 --until '2016-04-28 23:59:59'' failed: Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl/5.20/IPC/Open3.pm line 177. (500)
-Services: (empty)

-ceph-crush:
Fehler command 'crushtool -d /var/tmp/ceph-crush.map.2496 -o /var/tmp/ceph-crush.txt.2496' failed: Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl/5.20/IPC/Open3.pm line 177. (500)

-ceph-disks:
Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl5/PVE/CephTools.pm line 266. (500)

journalctl says:
pveproxy[4744]: got inotify poll request in wrong process - disabling inotify

pvedaemon[17615]: command 'systemctl show pveproxy' failed: Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl/5.20/IPC/Open3.pm line 177.

pvedaemon[8184]: start failed - Insecure directory in $ENV{PATH} while running with -T switch at /usr/share/perl5/PVE/Daemon.pm line 518

$ENV{PATH} seems to be '/sbin:/bin:/usr/sbin:/usr/bin' ...

Where should i look?

I `ve reinstalled the pve-packages..

pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
fence-agents-pve: 4.0.20-1
pve-sheepdog: 0.9.3-1
openvswitch-switch: 2.3.2-3


Thanks for your thoughts

Markus
 
Seems to be solved,
compared filepermissions with a other system, resetting them recursivly -what not really helped direct
After starting pvedaemon --debug by hand all was visible again.
Curios...