Search results

Any pro/cons on using sysvinit or systemd in LXC container (obviusly with a guest OS that support both and latest proxmox version)? I've seen that: - downloadable template "debian-9.0-standard_9.5-1_amd64.tar.gz" use systemd - while any template build with DAB make use of sysvinit (at least...

Thx.. so just waiting new package rebuild in test source repo. Best Regards

Hi, pve-manager/5.2.9/4b30e8f9 (test source repo) found a mistype in /usr/share/perl5/PVE/JSONSchema.pm line: 490 retturn $res; This prevent CT to start at boot. UPID:pve:00000918:000008AB:5BADE270:startall::root@pam: 5BADE270 Can't call method "retturn" on unblessed reference at...

Hi I experiencede strange behaviour on my single node Proxmox 5.1 Casual effect is can't connect anymore to HOST or CT shell!! Only available option is POWER SWITCH OFF/ON till next time it happens. I suppose an error related to console/login. I discovered that starting Mar 26 @08:57:17...

SOLVED. I monitored error in log... while stopping each LXC. I found the problem was related to a motion daemon working in one container (I think ml2/ml4 process belong to it) Updated "motion" code to last version on git, recompiled... and no more segfault. I was confused about error starting...

well.. proxmox host system shared library is the same: ii libc6:amd64 2.24-11+deb9u1 amd64 GNU C Library: Shared libraries ii libc6-dev:amd64 2.24-11+deb9u1 amd64 GNU C Library: Development Libraries...

Same problem for me. Always HP Proliant G8 (G1610T). Seems related to /boot on ZFS raid-1 and related to a reboot (after having updated kernel ??) Hoping somebody can help to debug/resolve. I'm still working with a reduced RAID-1 ZFS (on 3 disks) due to need of remove one disk to insert a new...

Hi, strange behaviour on my installation: HP Proliant G8 microserver with Proxmox 5.1 (updated to pve-test) Many SEGFAULT error in syslog like: Dec 20 10:24:55 pve kernel: [100995.340203] ml4[62621]: segfault at 10 ip 00007fc3882f6410 sp 00007fc376c6ac80 error 4 in...