Pydio fails to load as a service in systemclt

mudvane

Member
Jun 4, 2020
5
0
21
50
I am trying to get Pydio Cells to run as a service, my current configuration is using Proxmox and a lxc container running Ubuntu 20.04. I have Pydio installed all is working but when I follow the steps to make it a service here in the documentation but it fails. Below is the command and output I receive.

Code:
pydio@storm:~$ sudo systemctl start cells

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

Job for cells.service failed because the control process exited with error code.

See "systemctl status cells.service" and "journalctl -xe" for details.



pydio@storm:~$ sudo systemctl status cells.service

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

* cells.service - Pydio Cells

     Loaded: loaded (/etc/systemd/system/cells.service; enabled; vendor preset: enabled)

     Active: failed (Result: exit-code) since Thu 2020-06-04 16:25:20 UTC; 17s ago

       Docs: https://pydio.com

    Process: 639 ExecStartPre=/usr/bin/sudo /sbin/setcap cap_net_bind_service=+ep /home/pydio/cells (code=exited, status=200/CHDIR)



Jun 04 16:25:20 storm systemd[1]: cells.service: Scheduled restart job, restart counter is at 5.

Jun 04 16:25:20 storm systemd[1]: Stopped Pydio Cells.

Jun 04 16:25:20 storm systemd[1]: cells.service: Start request repeated too quickly.

Jun 04 16:25:20 storm systemd[1]: cells.service: Failed with result 'exit-code'.

Jun 04 16:25:20 storm systemd[1]: Failed to start Pydio Cells.

pydio@storm:~$

pydio@storm:~$



pydio@storm:~$ sudo journalctl -xe

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

--

-- The unit cells.service has entered the 'failed' state with result 'exit-code'.

Jun 04 16:25:20 storm systemd[1]: Failed to start Pydio Cells.

-- Subject: A start job for unit cells.service has failed

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A start job for unit cells.service has finished with a failure.

--

-- The job identifier is 1802 and the job result is failed.

Jun 04 16:25:20 storm systemd[1]: cells.service: Scheduled restart job, restart counter is at 5.

-- Subject: Automatic restarting of a unit has been scheduled

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- Automatic restarting of the unit cells.service has been scheduled, as the result for

-- the configured Restart= setting for the unit.

Jun 04 16:25:20 storm systemd[1]: Stopped Pydio Cells.

-- Subject: A stop job for unit cells.service has finished

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A stop job for unit cells.service has finished.

--

-- The job identifier is 1853 and the job result is done.

Jun 04 16:25:20 storm systemd[1]: cells.service: Start request repeated too quickly.

Jun 04 16:25:20 storm systemd[1]: cells.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- The unit cells.service has entered the 'failed' state with result 'exit-code'.

Jun 04 16:25:20 storm systemd[1]: Failed to start Pydio Cells.

-- Subject: A start job for unit cells.service has failed

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A start job for unit cells.service has finished with a failure.

--

-- The job identifier is 1853 and the job result is failed.

Jun 04 16:25:37 storm sudo[640]:    pydio : TTY=console ; PWD=/home/pydio ; USER=root ; COMMAND=/bin/systemctl status cells.service

Jun 04 16:25:37 storm sudo[640]: pam_unix(sudo:session): session opened for user root by LOGIN(uid=0)

Jun 04 16:25:37 storm sudo[640]: pam_unix(sudo:session): session closed for user root

Jun 04 16:25:58 storm sudo[644]:    pydio : TTY=console ; PWD=/home/pydio ; USER=root ; COMMAND=/bin/journalctl -xe

Jun 04 16:25:58 storm sudo[644]: pam_unix(sudo:session): session opened for user root by LOGIN(uid=0)

lines 6082-6126/6126 (END)

Thanks in advance.
 
This also seems to be happening for other things like UNSM too. Any discovery of what's causing it yet on Ubuntu 20.04?

Oh I just realized, I think this is trying to use Docker. Are you also trying to use Docker? We have to use other options to make Docker work right with Proxmox it appears.
 
Can you (both) post your used package versions and CTs config please:
Bash:
pveversion -v
pct config VMID

In general, if you run some services in there which do its own isolation you may want to enable the "nesting" Feature under CT → Options in the webinterface.
 
Requested output:
Code:
root@proxVM:~# pct config 101
arch: amd64
cores: 4
features: nesting=1
hostname: storm.praeters.com
memory: 8192
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=E6:71:79:84:D6:9A,ip=192.168.1.221/24,type=veth
ostype: ubuntu
rootfs: local-zfs:subvol-101-disk-0,size=30G
swap: 512
unprivileged: 1
root@proxVM:~#


root@proxVM:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve)
pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754)
pve-kernel-5.4: 6.2-2
pve-kernel-helper: 6.2-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-3
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-7
pve-cluster: 6.1-8
pve-container: 3.1-8
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
root@proxVM:~#

I also set the nesting option but that did not change anything.
 

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!