Recent content by notter

  1. N

    container is not running.

    do you have anything to suggest?
  2. N

    container is not running.

    root@proxmox:~# pct config 106 arch: amd64 cores: 8 hostname: server.XXXXXX lock: mounted memory: 16000 nameserver: 195.175.39.39 195.175.39.40 net0: name=eth0,bridge=vmbr0,gw=X.X.X.X,hwaddr=56:53:C8:09:3F:E5,ip=X.X.X.X/32,type=veth ostype: centos rootfs...
  3. N

    container is not running.

    I rebooted server after upgrade. kernel upgraded however i have different error message could you help us ? thanks for your interest Hi, root@proxmox:~# pct start 106 __sync_wait: 36 An error occurred in another process (expected sequence number 7) __lxc_start: 1999 Failed to spawn...
  4. N

    container is not running.

    we have different error now. root@proxmox:~# pct start 106 lxc_can_use_pidfd: 1905 Kernel does not support pidfds __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 48(dev) __sync_wait: 36 An error occurred in another process (expected sequence number 7) __lxc_start: 1999...
  5. N

    container is not running.

    root@proxmox:~# cat /tmp/lxc-106.log lxc-start 106 20210604115455.506 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor lxc-start 106 20210604115455.506 INFO seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount # comment this to allow umount -f; not...
  6. N

    container is not running.

    Please check it. root@proxmox:~# lxc-start -n 106 -F -l DEBUG -o /tmp/lxc-106.log lxc-start: 106: cgroups/cgfsng.c: mkdir_eexist_on_last: 1301 File exists - Failed to create directory "/sys/fs/cgroup/systemd//lxc/106" lxc-start: 106: cgroups/cgfsng.c: container_create_path_for_hierarchy...
  7. N

    container is not running.

    Hi , I didn't start container after reboot the server. how we resolve this problem ? thanks root@proxmox:~# pct start 106 Job for pve-container@106.service failed because the control process exited with error code. See "systemctl status pve-container@106.service" and "journalctl -xe" for...
  8. N

    container is not running.

    Hi, I didn't start container after reboot the server. what do you suggest i do? thanks for your interest root@proxmox:~# pct start 106 Job for pve-container@106.service failed because the control process exited with error code. See "systemctl status pve-container@106.service" and "journalctl...
  9. N

    how we mount second disk ?

    thanks udo can you control it ? proxmox:~# dmesg | grep sd sd 8:0:0:1: Attached scsi generic sg1 type 0 sd 7:0:0:0: Attached scsi generic sg2 type 0 sd 7:0:0:0: [sdb] Attached SCSI removable disk sd 8:0:0:1: [sda] Attached SCSI removable disk sd 0:1:0:0: Attached scsi generic sg4 type 0 sd...
  10. N

    how we mount second disk ?

    Our machine has 2 hard drive. RAID 1 is used. "fdisk-l" When I write, I see a hard drive.How do I know that RAID 1?
  11. N

    how we mount second disk ?

    Hello we have two disks in this server. how we mount 2nd disk? proxmox:~# fdisk -l Disk /dev/sdc: 999.6 GB, 999653638144 bytes 255 heads, 63 sectors/track, 121534 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!